Re: kernel space getcwd()? (using current() to find out cwd)

• Next message: Hen, Shmulik: "change_mtu boundary checking error"
• Previous message: Andreas Ferber: "Re: Mylex DAC vs RAM disk in 2.4.2 devfs"
• In reply to: Michael L. Welles: "kernel space getcwd()? (using current() to find out cwd)"
• Next in thread: Brian J. Watson: "Re: kernel space getcwd()? (using current() to find out cwd)"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

In article <15067.30060.436790.458922@bangstate.com> you wrote:
> So, a little ignorance being a dangerous thing, I thought I'd be clever
> and manually reconstruct the full path by walking up
> current->fs->pwd->d_parent and padding d_name to the filename until it
> hits root.
>
> Unfortunatly, this approach causes kernel panics. e.g., the attached
> code snippet will inevitably bring down the machine if I call it
> during in my replacement open, mkdir, rmdir, unlink routines -- and
> tehy all work fine without itq.

Use d_path. NOTE: the buffer in which the pathname is returned is
the return value of the function and _not_ the buffer you gave to it.

        Christoph

-- 
Of course it doesn't work. We've performed a software upgrade.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

• Next message: Hen, Shmulik: "change_mtu boundary checking error"
• Previous message: Andreas Ferber: "Re: Mylex DAC vs RAM disk in 2.4.2 devfs"
• In reply to: Michael L. Welles: "kernel space getcwd()? (using current() to find out cwd)"
• Next in thread: Brian J. Watson: "Re: kernel space getcwd()? (using current() to find out cwd)"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Mon Apr 23 2001 - 21:00:22 EST