Re: kern___getcwd() returns ENOTDIR
From: David Schultz (das_at_FreeBSD.ORG)
Date: 06/27/04
- Previous message: Kentucky Mandeloid Mo.: "kern___getcwd() returns ENOTDIR"
- In reply to: Kentucky Mandeloid Mo.: "kern___getcwd() returns ENOTDIR"
- Next in thread: Pawel Jakub Dawidek: "Re: kern___getcwd() returns ENOTDIR"
- Reply: Pawel Jakub Dawidek: "Re: kern___getcwd() returns ENOTDIR"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sun, 27 Jun 2004 11:12:20 -0700 To: "Kentucky Mandeloid Mo." <ky@df.ru>
On Sun, Jun 27, 2004, Kentucky Mandeloid Mo. wrote:
> I'm writng a smal kernel module that catches file access syscalls.
> At every syscall I need a full name of file is being passed to a syscall.
> I'm getting it with a path passed to syscall and if path is not starting
> with / I get current working directory of process using kern___getcwd().
> In every syscall all works just fine except rmdir & unlink.
> Sometimes in unlink and everytime in rmdir it returns "not a directory" error.
> I know already that kern___getcwd() works through vnode cache and this method
> is not a reliable way to get file names.
> So is there any other way get cwd of a proccess?
linux_getcwd() works in more cases than kern___getcwd(), but it
has other problems.
_______________________________________________
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"
- Previous message: Kentucky Mandeloid Mo.: "kern___getcwd() returns ENOTDIR"
- In reply to: Kentucky Mandeloid Mo.: "kern___getcwd() returns ENOTDIR"
- Next in thread: Pawel Jakub Dawidek: "Re: kern___getcwd() returns ENOTDIR"
- Reply: Pawel Jakub Dawidek: "Re: kern___getcwd() returns ENOTDIR"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]