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] more vfs bits
Date: Sun, 3 Mar 2013 16:04:30 +0000 [thread overview]
Message-ID: <20130303160430.GL4503@ZenIV.linux.org.uk> (raw)
Unfortunately, it looks like xattr series will have to wait until
the next cycle ;-/ This pile contains 9p cleanups and fixes (races in
v9fs_fid_add(), etc.), fixup for nommu breakage in shmem.c, several cleanups
and a bit more file_inode() work. Please, pull from
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git for-linus
Shortlog:
Al Viro (13):
selinux: opened file can't have NULL or negative ->f_path.dentry
more file_inode() open-coded instances
9p: don't bother with private lock in ->d_fsdata; dentry->d_lock will do just fine
9p: turn fid->dlist into hlist
v9fs: get rid of v9fs_dentry
9p: v9fs_fid_add() can't fail now
9p: double iput() in ->lookup() if d_materialise_unique() fails
9p: untangle ->lookup() a bit
9p: make sure ->lookup() adds fid to the right dentry
9p: if v9fs_fid_lookup() gets to asking server, it'd better have hashed dentry
cache the value of file_inode() in struct file
fix nommu breakage in shmem.c
constify path_get/path_put and fs_struct.c stuff
Diffstat:
arch/s390/hypfs/inode.c | 6 +--
arch/x86/kernel/msr.c | 9 ++---
drivers/staging/comedi/comedi_fops.c | 14 ++++----
drivers/tty/tty_io.c | 16 ++++------
fs/9p/fid.c | 55 ++++++++++++++++------------------
fs/9p/fid.h | 22 +-------------
fs/9p/vfs_dentry.c | 17 ++--------
fs/9p/vfs_inode.c | 40 ++++++++----------------
fs/9p/vfs_inode_dotl.c | 19 ++++-------
fs/ext4/indirect.c | 2 +-
fs/f2fs/file.c | 6 ++--
fs/file_table.c | 2 +
fs/fs_struct.c | 6 ++--
fs/fuse/dev.c | 2 +-
fs/fuse/file.c | 24 +++++++-------
fs/internal.h | 2 +-
fs/namei.c | 4 +-
fs/open.c | 3 +-
fs/seq_file.c | 2 +-
include/linux/fs.h | 3 +-
include/linux/fs_struct.h | 4 +-
include/linux/path.h | 4 +-
include/net/9p/client.h | 2 +-
kernel/futex.c | 2 +-
mm/shmem.c | 5 +--
security/selinux/hooks.c | 9 -----
26 files changed, 109 insertions(+), 171 deletions(-)
next reply other threads:[~2013-03-03 16:04 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-03 16:04 Al Viro [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-02-21 3:34 [git pull] more vfs bits Al Viro
2015-02-21 22:45 ` Linus Torvalds
2015-02-21 22:48 ` Linus Torvalds
2015-02-22 0:23 ` David Howells
2015-02-22 0:59 ` Al Viro
2015-02-22 0:51 ` Al Viro
2015-02-22 1:34 ` Linus Torvalds
2015-02-22 2:02 ` Al Viro
2015-02-22 2:11 ` Al Viro
2015-02-22 2:19 ` Linus Torvalds
2015-02-22 2:51 ` Al Viro
2015-02-22 3:16 ` Linus Torvalds
2015-02-22 8:51 ` Al Viro
2015-02-22 9:32 ` Sedat Dilek
2015-02-22 9:37 ` Al Viro
2015-02-22 10:36 ` Sedat Dilek
2015-02-22 15:05 ` Sedat Dilek
2015-02-22 15:12 ` Sedat Dilek
2015-02-22 13:22 ` Sedat Dilek
2015-02-22 13:23 ` Sedat Dilek
2015-02-22 12:54 ` David Howells
2015-02-22 12:44 ` David Howells
2015-02-22 12:39 ` David Howells
2015-02-22 12:30 ` David Howells
2015-02-22 0:18 ` David Howells
2015-02-22 1:14 ` Linus Torvalds
2015-02-22 1:32 ` Al Viro
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=20130303160430.GL4503@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).