From: Al Viro <viro@ZenIV.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: [git pull] vfs patches, part 2
Date: Wed, 17 Jun 2009 08:07:31 +0100 [thread overview]
Message-ID: <20090617070731.GH8633@ZenIV.linux.org.uk> (raw)
Mostlty BKL removal in VFS and filesystems. Please, pull from
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs-2.6.git for-linus
Al Viro (8):
No instance of ->bmap() needs BKL
fuse doesn't need BKL in ->umount_begin()
9P doesn't need BKL in ->umount_begin()
Cleanup of adfs headers
befs ->pust_super() doesn't need BKL
get rid of BKL in fs/efs
get rid of BKL in fs/minix
get rid of BKL in fs/sysv
J. R. Okajima (1):
remove unlock_kernel() left accidentally
Linus Torvalds (1):
ext3: avoid unnecessary spinlock in critical POSIX ACL path
Theodore Ts'o (1):
ext4: avoid unnecessary spinlock in critical POSIX ACL path
Documentation/filesystems/Locking | 2 +-
fs/9p/vfs_super.c | 3 --
fs/adfs/adfs.h | 55 +++++++++++++++++++++++++++++++++++++
fs/adfs/dir.c | 8 -----
fs/adfs/dir_f.c | 8 -----
fs/adfs/dir_fplus.c | 8 -----
fs/adfs/file.c | 4 ---
fs/adfs/inode.c | 10 -------
fs/adfs/map.c | 6 ----
fs/adfs/super.c | 17 +----------
fs/befs/linuxvfs.c | 4 ---
fs/efs/dir.c | 5 +---
fs/efs/namei.c | 9 +-----
fs/efs/symlink.c | 7 +----
fs/ext3/acl.c | 13 +++++---
fs/ext4/acl.c | 15 ++++++----
fs/fuse/inode.c | 3 --
fs/ioctl.c | 2 -
fs/minix/bitmap.c | 25 +++++++++--------
fs/minix/dir.c | 5 +---
fs/minix/inode.c | 4 ---
fs/super.c | 12 ++------
fs/sysv/dir.c | 5 +---
fs/sysv/inode.c | 11 -------
include/linux/adfs_fs.h | 13 ---------
include/linux/adfs_fs_i.h | 24 ----------------
include/linux/adfs_fs_sb.h | 38 -------------------------
27 files changed, 96 insertions(+), 220 deletions(-)
delete mode 100644 include/linux/adfs_fs_i.h
delete mode 100644 include/linux/adfs_fs_sb.h
reply other threads:[~2009-06-17 7:07 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=20090617070731.GH8633@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.