From: Rui Xiang <rui.xiang@huawei.com>
To: <linux-fsdevel@vger.kernel.org>, <viro@zeniv.linux.org.uk>
Cc: <linux-kernel@vger.kernel.org>, <linux-ia64@vger.kernel.org>,
<linuxppc-dev@lists.ozlabs.org>, <linux-s390@vger.kernel.org>,
<linux-rdma@vger.kernel.org>, <linux-usb@vger.kernel.org>,
<v9fs-developer@lists.sourceforge.net>, <linux-mm@kvack.org>,
<cgroups@vger.kernel.org>, <netdev@vger.kernel.org>,
Rui Xiang <rui.xiang@huawei.com>
Subject: [PATCH 0/2] fs: supply inode uid/gid setting interface
Date: Fri, 23 Aug 2013 10:48:36 +0800 [thread overview]
Message-ID: <1377226118-43756-1-git-send-email-rui.xiang@huawei.com> (raw)
This patchset implements an accessor functions to set uid/gid
in inode struct. Just finish code clean up.
Rui Xiang (2):
fs: implement inode uid/gid setting function
fs: use inode_set_user to set uid/gid of inode
arch/ia64/kernel/perfmon.c | 3 +--
arch/powerpc/platforms/cell/spufs/inode.c | 3 +--
arch/s390/hypfs/inode.c | 3 +--
drivers/infiniband/hw/qib/qib_fs.c | 3 +--
drivers/usb/gadget/f_fs.c | 3 +--
drivers/usb/gadget/inode.c | 5 +++--
fs/9p/vfs_inode.c | 6 ++----
fs/adfs/inode.c | 3 +--
fs/affs/inode.c | 6 ++----
fs/afs/inode.c | 6 ++----
fs/anon_inodes.c | 3 +--
fs/autofs4/inode.c | 4 ++--
fs/befs/linuxvfs.c | 8 ++++----
fs/ceph/caps.c | 5 +++--
fs/ceph/inode.c | 8 ++++----
fs/cifs/inode.c | 6 ++----
fs/configfs/inode.c | 3 +--
fs/debugfs/inode.c | 3 +--
fs/devpts/inode.c | 7 +++----
fs/ext2/ialloc.c | 3 +--
fs/ext3/ialloc.c | 3 +--
fs/ext4/ialloc.c | 3 +--
fs/fat/inode.c | 6 ++----
fs/fuse/control.c | 3 +--
fs/fuse/inode.c | 4 ++--
fs/hfs/inode.c | 6 ++----
fs/hfsplus/inode.c | 3 +--
fs/hpfs/inode.c | 3 +--
fs/hpfs/namei.c | 12 ++++--------
fs/hugetlbfs/inode.c | 3 +--
fs/inode.c | 7 +++++++
fs/isofs/inode.c | 3 +--
fs/isofs/rock.c | 3 +--
fs/ncpfs/inode.c | 3 +--
fs/nfs/inode.c | 4 ++--
fs/ntfs/inode.c | 12 ++++--------
fs/ntfs/mft.c | 3 +--
fs/ntfs/super.c | 3 +--
fs/ocfs2/refcounttree.c | 3 +--
fs/omfs/inode.c | 3 +--
fs/pipe.c | 3 +--
fs/proc/base.c | 15 +++++----------
fs/proc/fd.c | 8 ++++----
fs/proc/inode.c | 3 +--
fs/proc/self.c | 3 +--
fs/stack.c | 3 +--
fs/sysfs/inode.c | 3 +--
fs/xfs/xfs_iops.c | 4 ++--
include/linux/fs.h | 1 +
ipc/mqueue.c | 3 +--
kernel/cgroup.c | 3 +--
mm/shmem.c | 3 +--
net/socket.c | 3 +--
53 files changed, 94 insertions(+), 142 deletions(-)
--
1.8.2.2
next reply other threads:[~2013-08-23 2:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-23 2:48 Rui Xiang [this message]
2013-08-23 2:48 ` [PATCH 1/2] fs: implement inode uid/gid setting function Rui Xiang
2013-08-23 2:48 ` [PATCH 2/2] fs: use inode_set_user to set uid/gid of inode Rui Xiang
2013-08-23 5:21 ` David Miller
2013-08-23 4:10 ` [PATCH 0/2] fs: supply inode uid/gid setting interface Greg KH
2013-08-23 7:32 ` Rui Xiang
2013-08-27 9:20 ` David Laight
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=1377226118-43756-1-git-send-email-rui.xiang@huawei.com \
--to=rui.xiang@huawei.com \
--cc=cgroups@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=v9fs-developer@lists.sourceforge.net \
--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).