From: David Quigley <merlin@countercultured.net>
To: Eric Paris <eparis@redhat.com>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
Josef Bacik <josef@redhat.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
sds@tycho.nsa.gov, selinux@tycho.nsa.gov,
linux-security-module@vger.kernel.org
Subject: Re: [PATCH] fs: call security_d_instantiate in d_obtain_alias
Date: Fri, 19 Nov 2010 00:28:09 -0500 [thread overview]
Message-ID: <4CE60AE9.2070101@countercultured.net> (raw)
In-Reply-To: <1290031941.14282.101.camel@localhost.localdomain>
[snip]
> If you have persistent xattr support we need the dentry since the xattr
> code requires a dentry. I have no idea why but that's what
> inode->i_op->getxattr() requires.
>
The original reason that the xattr operations take dentries is because
of p9fs and CIFS. CIFS uses the name of the file to grab the extended
attributes and so does p9fs. I had tried to remove this a while ago but
couldn't find a way around that. When trying to find a solution I also
got push back from Miklos (FUSE) as he views a filesystem being able to
make xattr decisions based on the path name being a valid use-case.
Dave
next prev parent reply other threads:[~2010-11-19 5:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-17 17:51 [PATCH] fs: call security_d_instantiate in d_obtain_alias Josef Bacik
2010-11-17 18:54 ` Eric Paris
2010-11-17 19:18 ` J. Bruce Fields
2010-11-17 19:28 ` Josef Bacik
2010-11-17 20:26 ` J. Bruce Fields
2010-11-17 22:12 ` Eric Paris
2010-11-18 1:43 ` Josef Bacik
2010-11-19 5:28 ` David Quigley [this message]
2010-11-19 16:42 ` J. Bruce Fields
2010-11-20 16:38 ` Dave Quigley
2010-11-29 20:23 ` J. Bruce Fields
2010-11-17 20:27 ` Josef Bacik
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=4CE60AE9.2070101@countercultured.net \
--to=merlin@countercultured.net \
--cc=bfields@fieldses.org \
--cc=eparis@redhat.com \
--cc=josef@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
/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