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.git, pile 2
Date: Fri, 12 Oct 2012 02:19:57 +0100 [thread overview]
Message-ID: <20121012011957.GH2616@ZenIV.linux.org.uk> (raw)
Stuff in this one - assorted fixes, lglock tidy-up, death to
lock_super(). There'll be a VFS pile tomorrow (with patches from Jeff Layton,
sanitizing getname() and related parts of audit and preparing for ESTALE
fixes), but I'd rather push the stuff in this one ASAP - some of the bugs
closed here are quite unpleasant. Please, pull from the usual place -
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git for-linus
Shortlog:
Al Viro (2):
MAX_LFS_FILESIZE definition for 64bit needs LL...
consitify do_mount() arguments
Arnd Bergmann (1):
vfs: bogus warnings in fs/namei.c
Hugh Dickins (1):
tmpfs,ceph,gfs2,isofs,reiserfs,xfs: fix fh_len checking
Lai Jiangshan (3):
lglock: remove unused DEFINE_LGLOCK_LOCKDEP()
lglock: make the per_cpu locks static
lglock: add DEFINE_STATIC_LGLOCK()
Marco Stornelli (7):
exofs: drop lock/unlock super
ext3: drop lock/unlock super
fat: drop lock/unlock super
hpfs: drop lock/unlock super
sysv: drop lock/unlock super
ufs: drop lock/unlock super
vfs: drop lock/unlock super
Richard W.M. Jones (1):
dup3: Return an error when oldfd == newfd.
Sasha Levin (2):
fs: prevent use after free in auditing when symlink following was denied
fs: handle failed audit_log_start properly
Diffstat:
fs/ceph/export.c | 18 ++++++++++++++----
fs/exofs/super.c | 4 ----
fs/ext3/super.c | 6 ------
fs/fat/dir.c | 4 ++--
fs/fat/fat.h | 5 +++--
fs/fat/inode.c | 5 +++--
fs/fat/namei_msdos.c | 26 +++++++++++++-------------
fs/fat/namei_vfat.c | 30 +++++++++++++++---------------
fs/file.c | 3 +++
fs/file_table.c | 2 +-
fs/gfs2/export.c | 4 ++++
fs/hpfs/super.c | 3 ---
fs/isofs/export.c | 2 +-
fs/namei.c | 3 ++-
fs/namespace.c | 12 ++++++------
fs/reiserfs/inode.c | 6 +++++-
fs/super.c | 23 -----------------------
fs/sysv/balloc.c | 18 +++++++++---------
fs/sysv/ialloc.c | 14 +++++++-------
fs/sysv/inode.c | 4 ++--
fs/sysv/super.c | 1 +
fs/sysv/sysv.h | 1 +
fs/ufs/balloc.c | 30 +++++++++++++++---------------
fs/ufs/ialloc.c | 16 ++++++++--------
fs/ufs/super.c | 21 +++++++++++----------
fs/ufs/ufs.h | 1 +
fs/xfs/xfs_export.c | 3 +++
include/linux/fs.h | 5 ++---
include/linux/lglock.h | 19 ++++++++-----------
include/linux/security.h | 12 ++++++------
kernel/audit.c | 2 ++
mm/shmem.c | 6 ++++--
security/capability.c | 4 ++--
security/security.c | 4 ++--
security/selinux/hooks.c | 4 ++--
security/smack/smack_lsm.c | 4 ++--
security/tomoyo/common.h | 2 +-
security/tomoyo/mount.c | 5 +++--
security/tomoyo/tomoyo.c | 4 ++--
39 files changed, 166 insertions(+), 170 deletions(-)
next reply other threads:[~2012-10-12 1:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-12 1:19 Al Viro [this message]
2013-05-04 20:23 [git pull] vfs.git pile 2 Al Viro
2014-12-15 23:51 Al Viro
2014-12-16 13:33 ` Al Viro
2014-12-16 18:06 ` Al Viro
2016-12-16 22:12 Al Viro
2016-12-18 2:49 ` Linus Torvalds
2016-12-18 3:26 ` Al Viro
2016-12-18 3:34 ` Linus Torvalds
2016-12-18 4:06 ` Al Viro
2016-12-18 23:40 ` Darrick J. Wong
2017-03-02 12:38 [git pull] vfs.git, " 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=20121012011957.GH2616@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).