From: Steven Whitehouse <swhiteho@redhat.com>
To: Christoph Hellwig <hch@infradead.org>,
Andreas Gruenbacher <andreas.gruenbacher@gmail.com>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
cluster-devel@redhat.com, David Quigley <dpquigl@davequigley.com>,
Eric Paris <eparis@redhat.com>,
linux-security-module@vger.kernel.org,
Alexander Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Subject: Re: [Cluster-devel] [RFC 07/11] 9p: Stop using the generic xattr_handler infrastructure
Date: Fri, 21 Aug 2015 09:35:56 +0100 [thread overview]
Message-ID: <55D6E2EC.6030306@redhat.com> (raw)
In-Reply-To: <20150821064645.GA24276@infradead.org>
Hi,
On 21/08/15 07:46, Christoph Hellwig wrote:
> On Thu, Aug 20, 2015 at 08:19:54PM +0200, Andreas Gruenbacher wrote:
>> Of all the file systems that use the generic xattr handler infrastructure, 9p
>> is the only one that needs dentries inside the xattr file system code. Open
>> code the xattr handling code in 9p so that we can then convert the generic code
>> to pass down inodes instead of dentries; this actually takes only little
>> additional code.
> NAK. The rest of the series looks somewhat sensible but this is wrong.
>
> We need want to converge to one interface, probably more similar to the
> handlers, so we need to decided if we want to pass dentries or inodes to
> both of them.
>
> Personally I'm in favor of inodes, and that's how it used to be, but
> that makes life more complicated for path based file systems like cifs
> or 9p.
>
We did look at this in detail some time ago, and Al came to the
conclusion that 9p and CIFS both required the dentries and that it would
not be possible to pass just an inode. In the SELinux refresh case, the
dentry is not always available, and I don't think we have any choice
about that.
I know it is a bit of a mess, so if there is a better way to do it, then
that would be good. At the moment though, it is not clear quite how we
could get around this issue,
Steve.
next prev parent reply other threads:[~2015-08-21 8:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-20 18:19 [RFC 00/11] Inode security label invalidation Andreas Gruenbacher
2015-08-20 18:19 ` [RFC 01/11] ubifs: Remove unused "security.*" xattr handler Andreas Gruenbacher
2015-08-20 18:19 ` [RFC 02/11] hfsplus: Remove unused xattr handler list operations Andreas Gruenbacher
2015-08-20 18:19 ` [RFC 03/11] 9p: Simplify the xattr handlers Andreas Gruenbacher
2015-08-20 18:19 ` [RFC 04/11] xattr handlers: Pass handler to operations instead of flags Andreas Gruenbacher
2015-08-20 18:19 ` [RFC 05/11] xattr handlers: Some simplifications Andreas Gruenbacher
2015-08-20 18:19 ` [RFC 06/11] lib: Move strcmp_prefix into string.c Andreas Gruenbacher
2015-08-20 18:19 ` [RFC 07/11] 9p: Stop using the generic xattr_handler infrastructure Andreas Gruenbacher
2015-08-21 6:46 ` Christoph Hellwig
2015-08-21 8:35 ` Steven Whitehouse [this message]
2015-08-20 18:19 ` [RFC 08/11] xattr: Pass inodes to xattr handlers instead of dentries Andreas Gruenbacher
2015-08-20 18:19 ` [RFC 09/11] vfs: Add igetxattr inode operation Andreas Gruenbacher
2015-08-21 6:48 ` Christoph Hellwig
2015-08-20 18:19 ` [RFC 10/11] selinux: Allow to invalidate an inode's security label Andreas Gruenbacher
2015-08-20 18:19 ` [RFC 11/11] gfs2: Invalide security labels of inodes that go invalid Andreas Gruenbacher
2015-08-21 6:49 ` Christoph Hellwig
2015-08-21 9:25 ` [Cluster-devel] " Andreas Gruenbacher
2015-08-24 17:42 ` [RFC 00/11] Inode security label invalidation Stephen Smalley
2015-08-24 19:13 ` Andreas Grünbacher
2015-08-24 20:47 ` Eric Paris
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55D6E2EC.6030306@redhat.com \
--to=swhiteho@redhat.com \
--cc=andreas.gruenbacher@gmail.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=bfields@fieldses.org \
--cc=cluster-devel@redhat.com \
--cc=dpquigl@davequigley.com \
--cc=eparis@redhat.com \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).