From: Andreas Gruenbacher <agruenba@redhat.com>
To: Alexander Viro <viro@zeniv.linux.org.uk>
Cc: Andreas Gruenbacher <agruenba@redhat.com>,
linux-fsdevel@vger.kernel.org,
Tyler Hicks <tyhicks@canonical.com>,
ecryptfs@vger.kernel.org, linux-unionfs@vger.kernel.org,
David Howells <dhowells@redhat.com>,
Serge Hallyn <serge@hallyn.com>,
Dmitry Kasatkin <dmitry.kasatkin@gmail.com>,
linux-ima-devel@lists.sourceforge.net,
Paul Moore <paul@paul-moore.com>,
Stephen Smalley <sds@tycho.nsa.gov>,
Eric Paris <eparis@parisplace.org>,
Casey Schaufler <casey@schaufler-ca.com>,
Oleg Drokin <oleg.drokin@intel.com>,
Andreas Dilger <andreas.dilger@intel.com>
Subject: [PATCH v5 15/17] vfs: Check for the IOP_XATTR flag in listxattr
Date: Wed, 28 Sep 2016 16:58:01 +0200 [thread overview]
Message-ID: <1475074683-26971-16-git-send-email-agruenba@redhat.com> (raw)
In-Reply-To: <1475074683-26971-1-git-send-email-agruenba@redhat.com>
When an inode doesn't support xattrs, turn listxattr off as well.
(When xattrs are "turned off", the VFS still passes security xattr
operations through to security modules, which can still expose inode
security labels that way.)
Signed-off-by: Andreas Gruenbacher <agruenba@redhat.com>
---
fs/xattr.c | 13 +++++++------
1 file changed, 7 insertions(+), 6 deletions(-)
diff --git a/fs/xattr.c b/fs/xattr.c
index 54a4115..e1ccf2b 100644
--- a/fs/xattr.c
+++ b/fs/xattr.c
@@ -326,18 +326,19 @@ nolsm:
EXPORT_SYMBOL_GPL(vfs_getxattr);
ssize_t
-vfs_listxattr(struct dentry *d, char *list, size_t size)
+vfs_listxattr(struct dentry *dentry, char *list, size_t size)
{
+ struct inode *inode = d_inode(dentry);
ssize_t error;
- error = security_inode_listxattr(d);
+ error = security_inode_listxattr(dentry);
if (error)
return error;
- error = -EOPNOTSUPP;
- if (d->d_inode->i_op->listxattr) {
- error = d->d_inode->i_op->listxattr(d, list, size);
+ if (inode->i_op->listxattr && (inode->i_opflags & IOP_XATTR)) {
+ error = -EOPNOTSUPP;
+ error = inode->i_op->listxattr(dentry, list, size);
} else {
- error = security_inode_listsecurity(d->d_inode, list, size);
+ error = security_inode_listsecurity(inode, list, size);
if (size && error > size)
error = -ERANGE;
}
--
2.7.4
next prev parent reply other threads:[~2016-09-28 14:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-28 14:57 [PATCH v5 00/17] Xattr inode operation removal Andreas Gruenbacher
2016-09-28 14:57 ` [PATCH v5 01/17] xattr: Remove unnecessary NULL attribute name check Andreas Gruenbacher
2016-09-28 14:57 ` [PATCH v5 02/17] jffs2: Remove jffs2_{get,set,remove}xattr macros Andreas Gruenbacher
2016-09-28 14:57 ` [PATCH v5 03/17] hfs: Switch to generic xattr handlers Andreas Gruenbacher
2016-09-28 14:57 ` [PATCH v5 04/17] kernfs: " Andreas Gruenbacher
2016-09-28 14:57 ` [PATCH v5 05/17] sockfs: getxattr: Fail with -EOPNOTSUPP for invalid attribute names Andreas Gruenbacher
2016-09-28 14:57 ` [PATCH v5 06/17] sockfs: Get rid of getxattr iop Andreas Gruenbacher
2016-09-28 14:57 ` [PATCH v5 07/17] ecryptfs: Switch to generic xattr handlers Andreas Gruenbacher
2016-09-28 14:57 ` [PATCH v5 08/17] fuse: " Andreas Gruenbacher
2016-09-29 12:27 ` Miklos Szeredi
2016-09-28 14:57 ` [PATCH v5 09/17] lustre: " Andreas Gruenbacher
2016-09-28 22:40 ` Dilger, Andreas
2016-09-28 14:57 ` [PATCH v5 10/17] vfs: Move xattr_resolve_name to the front of fs/xattr.c Andreas Gruenbacher
2016-09-28 14:57 ` [PATCH v5 11/17] vfs: Add IOP_XATTR inode operations flag Andreas Gruenbacher
2016-09-28 14:57 ` [PATCH v5 12/17] vfs: Use IOP_XATTR flag for bad-inode handling Andreas Gruenbacher
2016-09-28 14:57 ` [PATCH v5 13/17] libfs: Use IOP_XATTR flag for empty directory handling Andreas Gruenbacher
2016-09-28 14:58 ` [PATCH v5 14/17] xattr: Add __vfs_{get,set,remove}xattr helpers Andreas Gruenbacher
2016-09-28 14:58 ` Andreas Gruenbacher [this message]
2016-09-28 14:58 ` [PATCH v5 16/17] xattr: Stop calling {get,set,remove}xattr inode operations Andreas Gruenbacher
2016-09-28 14:58 ` [PATCH v5 17/17] vfs: Remove " Andreas Gruenbacher
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=1475074683-26971-16-git-send-email-agruenba@redhat.com \
--to=agruenba@redhat.com \
--cc=andreas.dilger@intel.com \
--cc=casey@schaufler-ca.com \
--cc=dhowells@redhat.com \
--cc=dmitry.kasatkin@gmail.com \
--cc=ecryptfs@vger.kernel.org \
--cc=eparis@parisplace.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-ima-devel@lists.sourceforge.net \
--cc=linux-unionfs@vger.kernel.org \
--cc=oleg.drokin@intel.com \
--cc=paul@paul-moore.com \
--cc=sds@tycho.nsa.gov \
--cc=serge@hallyn.com \
--cc=tyhicks@canonical.com \
--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).