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 work.misc
Date: Fri, 17 Nov 2017 03:04:21 +0000 [thread overview]
Message-ID: <20171117030420.GM21978@ZenIV.linux.org.uk> (raw)
Assorted stuff, really no common topic here.
The following changes since commit 2bd6bf03f4c1c59381d62c61d03f6cc3fe71f66e:
Linux 4.14-rc1 (2017-09-16 15:47:51 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.misc
for you to fetch changes up to c02b1a9b41c2e728289f96850580a3651e0a8b5f:
vfs: grab the lock instead of blocking in __fd_install during resizing (2017-11-05 18:58:07 -0500)
----------------------------------------------------------------
Al Viro (6):
acct.h: get rid of detritus
new helper: destroy_unused_super()
fold destroy_super() into __put_super()
do_handle_open() should be static
make vfs_ustat() static
stubs for mount_bdev() and kill_block_super() in !CONFIG_BLOCK case
Arnd Bergmann (1):
elf_fdpic: fix unused variable warning
Hirofumi Nakagawa (2):
vfs: remove unneeded unlikely()
pstore: remove unneeded unlikely()
Jan Harkes (1):
coda: fix 'kernel memory exposure attempt' in fsync
Josef Bacik (1):
fs: make fiemap work from compat_ioctl
Linus Torvalds (1):
fix address space warnings in ipc/
Mateusz Guzik (2):
vfs: stop clearing close on exec when closing a fd
vfs: grab the lock instead of blocking in __fd_install during resizing
Mike Rapoport (1):
include/linux/fs.h: fix comment about struct address_space
Documentation/filesystems/porting | 4 ----
fs/binfmt_elf_fdpic.c | 2 ++
fs/coda/upcall.c | 3 +--
fs/compat_ioctl.c | 1 +
fs/fhandle.c | 4 ++--
fs/file.c | 12 +++++-----
fs/namei.c | 2 +-
fs/pstore/platform.c | 2 +-
fs/statfs.c | 2 +-
fs/super.c | 46 ++++++++++++++++++---------------------
include/linux/acct.h | 3 ---
include/linux/fs.h | 19 ++++++++++++++--
ipc/msg.c | 4 ++--
ipc/sem.c | 4 ++--
ipc/shm.c | 4 ++--
ipc/syscall.c | 2 +-
16 files changed, 61 insertions(+), 53 deletions(-)
next reply other threads:[~2017-11-17 3:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-17 3:04 Al Viro [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-08-14 0:23 [git pull] vfs.git #work.misc Al Viro
2022-08-14 0:39 ` Linus Torvalds
2022-08-14 0:39 ` pr-tracker-bot
2016-05-18 18:40 [git pull] vfs.git#work.misc 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=20171117030420.GM21978@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