linux-kernel - Re: [RFC PATCH -v4 00/14] fsnotify, dnotify, and inotify

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20081225203302.GS28946@ZenIV.linux.org.uk>
Date:	Thu, 25 Dec 2008 20:33:02 +0000
From:	Al Viro <viro@...IV.linux.org.uk>
To:	"C. Scott Ananian" <cscott@...top.org>
Cc:	Christoph Hellwig <hch@...radead.org>,
	Eric Paris <eparis@...hat.com>, linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH -v4 00/14] fsnotify, dnotify, and inotify

On Thu, Dec 25, 2008 at 01:17:28PM -0500, C. Scott Ananian wrote:
> getcwd doesn't actually hold a file descriptor to the working
> directory.  If you reread my message, you'll find that I was explicit
> about where the information was stored.

Indeed - explicit, persistent and wrong.  For current directory of a process
we store vfsmount and dentry.  And use those in getcwd() rather than playing
hopeless games with inodes.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/