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/fs fixes
Date: Wed, 27 Jul 2011 02:10:26 +0100 [thread overview]
Message-ID: <20110727011026.GA31146@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20110726185440.GK22133@ZenIV.linux.org.uk>
On Tue, Jul 26, 2011 at 07:54:40PM +0100, Al Viro wrote:
> The next commit in there turns it into umode_t ;-) I can put it (or both,
> for that matter) into today's pull - I'm waiting for s-o-b'ed version of
> XFS fix right now...
Grr... Looks like that will have to wait until tomorrow when the guy
wakes up. In the meanwhile, here's what I've got in queue at the moment,
if you prefer to pull it now rather than wait for tomorrow:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs-2.6.git/ for-linus
Shortlog:
Al Viro (10):
v9fs_iop_get_acl: get rid of unused variable
snd_msnd ->mode is fmode_t, not mode_t
jffs2: S_ISLNK(mode & S_IFMT) is pointless
pci-label.c: size_t misspelled as mode_t
ima: fmode_t misspelled as mode_t...
btrfs: S_ISREG(mode) is not mode & S_IFREG...
omfs: fix (mode & S_IFDIR) abuse
xfs: get rid of open-coded S_ISREG(), etc.
xfs: fix misspelled S_IS...()
merge fchmod() and fchmodat() guts, kill ancient broken kludge
Dan Carpenter (1):
fs: add missing unlock in default_llseek()
Eric Dumazet (1):
vfs: dont chain pipe/anon/socket on superblock s_inodes list
Jeff Layton (1):
vfs: document locking requirements for d_move, __d_move and d_materialise_unique
Phillip Lougher (1):
Documentation: Exporting: update description of d_splice_alias
Diffstat:
Documentation/filesystems/nfs/Exporting | 9 +++-
drivers/pci/pci-label.c | 2 +-
fs/9p/acl.c | 1 -
fs/anon_inodes.c | 2 +-
fs/btrfs/inode.c | 4 +-
fs/dcache.c | 11 +++--
fs/inode.c | 39 ++++++++++++----
fs/jffs2/fs.c | 2 +-
fs/omfs/dir.c | 2 +-
fs/open.c | 78 +++++++++++--------------------
fs/pipe.c | 2 +-
fs/read_write.c | 12 +++--
fs/xfs/linux-2.6/xfs_ioctl.c | 6 +-
fs/xfs/xfs_bmap.c | 7 +--
fs/xfs/xfs_dir2.c | 16 +++---
fs/xfs/xfs_filestream.c | 14 +++---
fs/xfs/xfs_inode.c | 16 +++---
fs/xfs/xfs_inode.h | 2 +-
fs/xfs/xfs_log_recover.c | 4 +-
fs/xfs/xfs_mount.c | 2 +-
fs/xfs/xfs_rename.c | 4 +-
fs/xfs/xfs_vnodeops.c | 10 ++--
include/linux/fs.h | 3 +-
net/socket.c | 2 +-
security/integrity/ima/ima_main.c | 2 +-
sound/isa/msnd/msnd.h | 2 +-
26 files changed, 133 insertions(+), 121 deletions(-)
next parent reply other threads:[~2011-07-27 1:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110724232409.GM24703@ZenIV.linux.org.uk>
[not found] ` <CA+55aFwkEaxyxaHWjQLRQx1Oq2mkJC4w_Jmx1w4XoUAzoscBrQ@mail.gmail.com>
[not found] ` <20110725184748.GT24703@ZenIV.linux.org.uk>
[not found] ` <CA+55aFwihZNDhDD4dXX3fKTECqf4puUOJmJc6Scebs1f4UFwGA@mail.gmail.com>
[not found] ` <20110725200303.GB22133@ZenIV.linux.org.uk>
[not found] ` <CA+55aFyNfkex19B3TERTohm6SMAJkwn3z=c+0KgFk_p1a=22BA@mail.gmail.com>
[not found] ` <20110725205832.GC22133@ZenIV.linux.org.uk>
[not found] ` <20110726183421.GA15641@ZenIV.linux.org.uk>
[not found] ` <CA+55aFxDQK5Tu0d6PqxvoRqvs1zZM5f8fVEKbJEQ1P3fm7PbHQ@mail.gmail.com>
[not found] ` <20110726185440.GK22133@ZenIV.linux.org.uk>
2011-07-27 1:10 ` Al Viro [this message]
2011-07-27 6:33 ` [git pull] vfs/fs fixes Markus Trippelsdorf
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=20110727011026.GA31146@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