From: Al Viro <viro@ZenIV.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: [git pull] vfs.git, xattr stuff
Date: Mon, 10 Oct 2016 23:01:39 +0100 [thread overview]
Message-ID: <20161010220139.GB19539@ZenIV.linux.org.uk> (raw)
xattr stuff from Andreas; aka. completing the switch to xattr_handler
->get()/->set() from ->getxattr/->setxattr/->removexattr
The following changes since commit 703c73629f93464ce210f5ad92d0c1fb95bfbadf:
fuse: Use generic xattr ops (2016-10-01 07:32:32 +0200)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.xattr
for you to fetch changes up to fd50ecaddf8372a1d96e0daeaac0f93cf04e4d42:
vfs: Remove {get,set,remove}xattr inode operations (2016-10-07 21:48:36 -0400)
----------------------------------------------------------------
Al Viro (2):
Merge commit '2c563880ea' into work.xattr
Merge remote-tracking branch 'fuse/xattr' into work.xattr
Andreas Gruenbacher (15):
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
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 +++--
drivers/staging/lustre/lustre/llite/file.c | 3 -
drivers/staging/lustre/lustre/llite/namei.c | 6 -
drivers/staging/lustre/lustre/llite/symlink.c | 3 -
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 | 9 -
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 | 6 -
fs/overlayfs/super.c | 4 +-
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.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 | 61 +++----
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 +-
80 files changed, 471 insertions(+), 687 deletions(-)
reply other threads:[~2016-10-10 22:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20161010220139.GB19539@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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
all inboxes | Powered by JetHome®