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] first part of VFS merges (ro-bind)
Date: Sat, 19 Apr 2008 17:25:42 +0100 [thread overview]
Message-ID: <20080419162542.GJ27459@ZenIV.linux.org.uk> (raw)
The first VFS series of this cycle: ro-bind patches. FWIW,
I'm not particulary happy with the state of commit messages - practically
all changesets ended up with contributions from at least 2-3 people
(usually Dave/me/Christoph) and commit messages have too many [foo: fixed
bug in bar() noticed by baz] in them. OTOH, it's bisectable and hopefully
each changeset makes sense, which is one hell of a good reason to fold
fixes into affected changesets, IMO...
Anyway, please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs-2.6.git/ ro-bind.b6
Shortlog:
Christoph Hellwig (1):
merge open_namei() and do_filp_open()
Dave Hansen (23):
do namei_flags calculation inside open_namei()
r/o bind mounts: stub functions
r/o bind mounts: create helper to drop file write access
r/o bind mounts: drop write during emergency remount
r/o bind mounts: elevate write count for rmdir and unlink.
r/o bind mounts: get callers of vfs_mknod/create/mkdir()
r/o bind mounts: write counts for link/symlink
r/o bind mounts: get write access for vfs_rename() callers
r/o bind mounts: elevate write count for xattr_permission() callers
r/o bind mounts: elevate write count for ncp_ioctl()
r/o bind mounts: write counts for touch_atime()
r/o bind mounts: elevate write count for do_utimes()
r/o bind mounts: write count for file_update_time()
r/o bind mounts: elevate write count for ioctls()
r/o bind mounts: elevate write count for open()s
r/o bind mounts: elevate write count for chmod/chown callers
r/o bind mounts: write counts for truncate()
r/o bind mounts: make access() use new r/o helper
r/o bind mounts: elevate count for xfs timestamp updates
r/o bind mounts: check mnt instead of superblock directly
r/o bind mounts: track numbers of writers to mounts
r/o bind mounts: honor mount writer counts at remount
r/o bind mounts: debugging for missed calls
Diffstat:
fs/ext2/ioctl.c | 57 +++++---
fs/ext3/ioctl.c | 103 +++++++++-----
fs/ext4/ioctl.c | 86 +++++++-----
fs/fat/file.c | 12 +-
fs/file_table.c | 42 ++++++-
fs/hfsplus/ioctl.c | 38 +++--
fs/inode.c | 51 ++++----
fs/jfs/ioctl.c | 33 +++--
fs/namei.c | 275 ++++++++++++++++++++++++++++---------
fs/namespace.c | 316 +++++++++++++++++++++++++++++++++++++++++-
fs/ncpfs/ioctl.c | 54 +++++++-
fs/nfs/dir.c | 3 +-
fs/nfsd/nfs4proc.c | 7 +-
fs/nfsd/nfs4recover.c | 16 ++-
fs/nfsd/nfs4state.c | 3 +-
fs/nfsd/vfs.c | 72 ++++++++--
fs/ocfs2/ioctl.c | 11 +-
fs/open.c | 149 ++++++++++++--------
fs/reiserfs/ioctl.c | 63 ++++++---
fs/super.c | 24 +++-
fs/utimes.c | 18 ++-
fs/xattr.c | 40 +++++-
fs/xfs/linux-2.6/xfs_ioctl.c | 15 ++-
fs/xfs/linux-2.6/xfs_iops.c | 7 -
fs/xfs/linux-2.6/xfs_lrw.c | 9 +-
include/linux/file.h | 1 +
include/linux/fs.h | 52 +++++++-
include/linux/mount.h | 11 ++
ipc/mqueue.c | 25 +++-
lib/Kconfig.debug | 10 ++
net/unix/af_unix.c | 4 +
31 files changed, 1256 insertions(+), 351 deletions(-)
reply other threads:[~2008-04-19 16:25 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=20080419162542.GJ27459@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;
as well as URLs for NNTP newsgroup(s).