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, Miklos Szeredi <miklos@szeredi.hu>,
linux-unionfs@vger.kernel.org,
David Howells <dhowells@redhat.com>,
Serge Hallyn <serge.hallyn@canonical.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 v4 00/20] Xattr inode operation removal
Date: Mon, 22 Aug 2016 23:21:48 +0200 [thread overview]
Message-ID: <1471900928-21588-1-git-send-email-agruenba@redhat.com> (raw)
This is version 4 of the xattr inode operation removal patch series. The
patches are available in git form at:
https://git.kernel.org/cgit/linux/kernel/git/agruen/linux.git/log/?h=work.xattr
Previous posting: http://www.spinics.net/lists/ecryptfs/msg00791.html
The purpose of this series is to remove unnecessary differences between the
xattr implementations on different filesystems and to simplify things. With
the exception of redirectors like fuse, overlayfs, and ecryptfs, all
filesystems perform some de-multiplexing based on the xattr name, so it makes
sense to make that the default; filesystems that don't do any de-multiplexing
can easily use a catch-all xattr handler.
The patch series is structured as follows:
* The first four patches fix a few things and convert overlayfs to use xattr
handlers; they have been posted to Miklos and linux-unionfs@vger.kernel.org
already because they are partially relevant for the 4.8 kernel.
* The following patches convert the remaining filesystems over to use xattr
handlers.
* Next, a new IOP_XATTR inode operations flag is introduced: the flag is set
when an inode supports xattrs. On most filesystems, the IOP_XATTR flag is
automatically initialized correctly when the inode is allocated based on
whether or not the s_xattr field in the inode's superblock is defined.
Filesystems that support xattrs on some but not all inodes can clear the
IOP_XATTR flag appropriately.
* The IOP_XATTR flag is then used to get rid of the two remaining places where
xattr inode operations other than the generic ones are used: bad inodes and
libfs empty directories.
* After that, we get rid of the remaining direct accesses to xattr inode
operations.
* Finally, we stop calling the xattr inode operations and remove them.
Note that these patches only remove the getxattr, setxattr, and removexattr
inode operations. The listxattr inode operation does not do any attribute name
de-multiplexing, and remains unchanged except for checking the new IOP_XATTR
flag as well now.
Thanks,
Andreas
Andreas Gruenbacher (20):
ovl: Fix OVL_XATTR_PREFIX
ovl: Get rid of ovl_xattr_noacl_handlers array
ovl: Switch to generic_removexattr
ovl: Switch to generic_getxattr
xattr: Remove unnecessary NULL attribute name check
jffs2: Remove jffs2_{get,set,remove}xattr macros
hfs: Switch to generic xattr handlers
kernfs: Switch to generic xattr handlers
sockfs: getxattr: Fail with -EOPNOTSUPP for invalid attribute names
sockfs: Get rid of getxattr iop
ecryptfs: Switch to generic xattr handlers
fuse: Switch to generic xattr handlers
vfs: Move xattr_resolve_name to the front of fs/xattr.c
vfs: Add IOP_XATTR inode operations flag
vfs: Use IOP_XATTR flag for bad-inode handling
libfs: Use IOP_XATTR flag for empty directory handling
xattr: Add __vfs_{get,set,remove}xattr helpers
vfs: Check for the IOP_XATTR flag in listxattr
xattr: Stop calling {get,set,remove}xattr inode operations
vfs: Remove {get,set,remove}xattr inode operations
Documentation/filesystems/Locking | 24 +++-
Documentation/filesystems/vfs.txt | 45 ++++--
fs/9p/vfs_inode_dotl.c | 9 --
fs/bad_inode.c | 21 +--
fs/btrfs/inode.c | 12 --
fs/cachefiles/bind.c | 4 +-
fs/cachefiles/namei.c | 4 +-
fs/ceph/dir.c | 3 -
fs/ceph/inode.c | 6 -
fs/cifs/cifsfs.c | 9 --
fs/ecryptfs/ecryptfs_kernel.h | 2 +
fs/ecryptfs/inode.c | 67 ++++++---
fs/ecryptfs/main.c | 1 +
fs/ecryptfs/mmap.c | 13 +-
fs/ext2/file.c | 3 -
fs/ext2/namei.c | 6 -
fs/ext2/symlink.c | 6 -
fs/ext4/file.c | 3 -
fs/ext4/namei.c | 6 -
fs/ext4/symlink.c | 9 --
fs/f2fs/file.c | 3 -
fs/f2fs/namei.c | 12 --
fs/fuse/dir.c | 49 +++++--
fs/fuse/fuse_i.h | 2 +
fs/fuse/inode.c | 1 +
fs/gfs2/inode.c | 9 --
fs/hfs/attr.c | 83 +++++++----
fs/hfs/hfs_fs.h | 6 +-
fs/hfs/inode.c | 5 +-
fs/hfs/super.c | 1 +
fs/hfsplus/dir.c | 3 -
fs/hfsplus/inode.c | 3 -
fs/inode.c | 2 +
fs/jffs2/dir.c | 3 -
fs/jffs2/file.c | 3 -
fs/jffs2/symlink.c | 3 -
fs/jffs2/xattr.h | 6 -
fs/jfs/file.c | 3 -
fs/jfs/namei.c | 3 -
fs/jfs/symlink.c | 6 -
fs/kernfs/dir.c | 3 -
fs/kernfs/inode.c | 155 +++++++++++----------
fs/kernfs/kernfs-internal.h | 7 +-
fs/kernfs/mount.c | 1 +
fs/kernfs/symlink.c | 3 -
fs/libfs.c | 29 +---
fs/nfs/nfs3proc.c | 6 -
fs/nfs/nfs4proc.c | 6 -
fs/ocfs2/file.c | 3 -
fs/ocfs2/namei.c | 3 -
fs/ocfs2/symlink.c | 3 -
fs/orangefs/inode.c | 3 -
fs/orangefs/namei.c | 3 -
fs/orangefs/symlink.c | 1 -
fs/orangefs/xattr.c | 3 +
fs/overlayfs/copy_up.c | 4 +-
fs/overlayfs/dir.c | 3 -
fs/overlayfs/inode.c | 88 +++---------
fs/overlayfs/overlayfs.h | 12 +-
fs/overlayfs/super.c | 69 ++++++----
fs/reiserfs/file.c | 3 -
fs/reiserfs/namei.c | 9 --
fs/squashfs/inode.c | 1 -
fs/squashfs/namei.c | 1 -
fs/squashfs/symlink.c | 1 -
fs/squashfs/xattr.c | 19 ++-
fs/squashfs/xattr.h | 1 -
fs/ubifs/dir.c | 3 -
fs/ubifs/file.c | 6 -
fs/xattr.c | 250 ++++++++++++++++------------------
fs/xfs/xfs_iops.c | 15 --
include/linux/fs.h | 23 ++--
include/linux/xattr.h | 7 +-
mm/shmem.c | 15 --
net/socket.c | 70 +++++-----
security/commoncap.c | 25 ++--
security/integrity/evm/evm_crypto.c | 7 +-
security/integrity/evm/evm_main.c | 4 +-
security/integrity/ima/ima_appraise.c | 21 ++-
security/selinux/hooks.c | 19 +--
security/smack/smack_lsm.c | 12 +-
81 files changed, 602 insertions(+), 774 deletions(-)
--
2.7.4
next reply other threads:[~2016-08-22 21:22 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-22 21:21 Andreas Gruenbacher [this message]
2016-08-22 21:21 ` [PATCH v4 01/20] ovl: Fix OVL_XATTR_PREFIX Andreas Gruenbacher
2016-08-22 21:21 ` [PATCH v4 02/20] ovl: Get rid of ovl_xattr_noacl_handlers array Andreas Gruenbacher
2016-08-22 21:21 ` [PATCH v4 03/20] ovl: Switch to generic_removexattr Andreas Gruenbacher
2016-08-22 21:21 ` [PATCH v4 04/20] ovl: Switch to generic_getxattr Andreas Gruenbacher
2016-08-22 21:21 ` [PATCH v4 05/20] xattr: Remove unnecessary NULL attribute name check Andreas Gruenbacher
2016-08-22 21:21 ` [PATCH v4 06/20] jffs2: Remove jffs2_{get,set,remove}xattr macros Andreas Gruenbacher
2016-08-22 21:21 ` [PATCH v4 07/20] hfs: Switch to generic xattr handlers Andreas Gruenbacher
2016-08-22 21:21 ` [PATCH v4 08/20] kernfs: " Andreas Gruenbacher
2016-08-22 21:21 ` [PATCH v4 09/20] sockfs: getxattr: Fail with -EOPNOTSUPP for invalid attribute names Andreas Gruenbacher
2016-08-22 21:21 ` [PATCH v4 10/20] sockfs: Get rid of getxattr iop Andreas Gruenbacher
2016-08-22 21:21 ` [PATCH v4 11/20] ecryptfs: Switch to generic xattr handlers Andreas Gruenbacher
2016-08-22 21:22 ` [PATCH v4 12/20] fuse: " Andreas Gruenbacher
2016-08-22 21:22 ` [PATCH v4 13/20] vfs: Move xattr_resolve_name to the front of fs/xattr.c Andreas Gruenbacher
2016-08-22 21:22 ` [PATCH v4 14/20] vfs: Add IOP_XATTR inode operations flag Andreas Gruenbacher
2016-08-22 21:22 ` [PATCH v4 15/20] vfs: Use IOP_XATTR flag for bad-inode handling Andreas Gruenbacher
2016-08-22 21:22 ` [PATCH v4 16/20] libfs: Use IOP_XATTR flag for empty directory handling Andreas Gruenbacher
2016-08-22 21:22 ` [PATCH v4 17/20] xattr: Add __vfs_{get,set,remove}xattr helpers Andreas Gruenbacher
2016-08-22 21:22 ` [PATCH v4 18/20] vfs: Check for the IOP_XATTR flag in listxattr Andreas Gruenbacher
2016-08-22 21:22 ` [PATCH v4 19/20] xattr: Stop calling {get,set,remove}xattr inode operations Andreas Gruenbacher
2016-08-22 21:22 ` [PATCH v4 20/20] vfs: Remove " Andreas Gruenbacher
2016-08-23 0:34 ` kbuild test robot
2016-08-23 9:57 ` [PATCH] lustre: Switch to generic xattr handlers 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=1471900928-21588-1-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=miklos@szeredi.hu \
--cc=oleg.drokin@intel.com \
--cc=paul@paul-moore.com \
--cc=sds@tycho.nsa.gov \
--cc=serge.hallyn@canonical.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).