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: Thu, 2 Mar 2017 12:38:36 +0000 [thread overview]
Message-ID: <20170302123836.GZ29622@ZenIV.linux.org.uk> (raw)
orangefs fix + series of fs/namei.c cleanups from
me + VFS stuff coming from overlayfs tree.
The following changes since commit f1ef09fde17f9b77ca1435a5b53a28b203afb81c:
Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace (2017-02-23 20:33:51 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git for-linus
for you to fetch changes up to 653a7746fa2f5369985f5368ffc162b6510db6c8:
Merge remote-tracking branch 'ovl/for-viro' into for-linus (2017-03-02 06:41:22 -0500)
----------------------------------------------------------------
Al Viro (6):
namei: fold unlazy_link() into its sole caller
lookup_fast(): clean up the logics around the fallback to non-rcu mode
namei.c: fold the check for DCACHE_OP_REVALIDATE into d_revalidate()
namei.c: split unlazy_walk()
Merge branch 'work.namei' into for-linus
Merge remote-tracking branch 'ovl/for-viro' into for-linus
Amir Goldstein (4):
vfs: create vfs helper vfs_tmpfile()
vfs: deny fallocate() on directory
vfs: deny copy_file_range() for non regular files
vfs: wrap write f_ops with file_{start,end}_write()
Miklos Szeredi (5):
vfs: extract common parts of {compat_,}do_readv_writev()
vfs: pass type instead of fn to do_{loop,iter}_readv_writev()
vfs: use helpers for calling f_op->{read,write}_iter()
mm: use helper for calling f_op->mmap()
vfs: use helper for calling f_op->fsync()
Peter Zijlstra (1):
orangefs: Use RCU for destroy_inode
drivers/block/loop.c | 4 +-
drivers/gpu/drm/i915/i915_gem_dmabuf.c | 2 +-
drivers/gpu/drm/vgem/vgem_drv.c | 2 +-
fs/aio.c | 4 +-
fs/coda/file.c | 2 +-
fs/namei.c | 251 ++++++++++++++++++---------------
fs/open.c | 14 +-
fs/orangefs/super.c | 9 +-
fs/read_write.c | 130 ++++++++---------
fs/splice.c | 2 +-
fs/sync.c | 2 +-
include/linux/fs.h | 52 +++++--
ipc/shm.c | 4 +-
mm/mmap.c | 2 +-
mm/nommu.c | 4 +-
15 files changed, 261 insertions(+), 223 deletions(-)
next reply other threads:[~2017-03-02 12:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-02 12:38 Al Viro [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-12-16 22:12 [git pull] vfs.git pile 2 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
2014-12-15 23:51 Al Viro
2014-12-16 13:33 ` Al Viro
2014-12-16 18:06 ` Al Viro
2013-05-04 20:23 Al Viro
2012-10-12 1:19 [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=20170302123836.GZ29622@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