linux-kernel - Re: [RFD 1/4] Pass no useless nameidata to the create, lookup, and permission IOPs

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: <20070630091452.GB21784@infradead.org>
Date:	Sat, 30 Jun 2007 10:14:52 +0100
From:	Christoph Hellwig <hch@...radead.org>
To:	Erez Zadok <ezk@...sunysb.edu>
Cc:	jjohansen@...e.de, linux-kernel@...r.kernel.org,
	linux-security-module@...r.kernel.org,
	linux-fsdevel@...r.kernel.org, Andreas Gruenbacher <agruen@...e.de>
Subject: Re: [RFD 1/4] Pass no useless nameidata to the create, lookup, and permission IOPs

On Tue, Jun 26, 2007 at 08:11:41PM -0400, Erez Zadok wrote:
> Perhaps it is also time to put the dentry + mnt into a single struct path?
> It's a small change, but it emphasizes that the two items here, dentry+mnt,
> really define a single path to be passed around:

No.  The vfsmount will go away completely medium-term once we get right
of the atomic open nfs hack that paases a file back in the open intent.
A normal filesystem has not business looking at the vfsmount instance at
all, and the raw open/create we need to replace the atomic open hack
will need the full nameidata per definition, also to allow things like
a multi-component lookup that various cluster/network filesystems really
want.

-
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/