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 fixes for -final
Date: Sat, 14 May 2016 19:44:47 +0100 [thread overview]
Message-ID: <20160514184447.GC14480@ZenIV.linux.org.uk> (raw)
Overlayfs fixes from Miklos, assorted fixes from me. -stable fodder of
varying severity, all sat in -next for a while.
The following changes since commit 44549e8f5eea4e0a41b487b63e616cb089922b99:
Linux 4.6-rc7 (2016-05-08 14:38:32 -0700)
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 e4d35be584be88a3db3fa5635a97c62a2ec5aafe:
Merge branch 'ovl-fixes' into for-linus (2016-05-11 00:00:29 -0400)
----------------------------------------------------------------
Al Viro (6):
do_splice_to(): cap the size before passing to ->splice_read()
fix the copy vs. map logics in blk_rq_map_user_iov()
atomic_open(): fix the handling of create_error
ecryptfs: fix handling of directory opening
get_rock_ridge_filename(): handle malformed NM entries
Merge branch 'ovl-fixes' into for-linus
Miklos Szeredi (4):
vfs: add vfs_select_inode() helper
vfs: rename: check backing inode being equal
vfs: add lookup_hash() helper
ovl: ignore permissions on underlying lookup
block/blk-map.c | 47 ++++++---------------------------
fs/ecryptfs/file.c | 71 ++++++++++++++++++++++++++++++++++++++------------
fs/isofs/rock.c | 13 ++++++---
fs/namei.c | 59 +++++++++++++++++++++++++----------------
fs/open.c | 12 +++------
fs/overlayfs/super.c | 4 +--
fs/splice.c | 3 +++
include/linux/dcache.h | 12 +++++++++
include/linux/namei.h | 2 ++
include/linux/uio.h | 1 +
lib/iov_iter.c | 19 ++++++++++++++
11 files changed, 152 insertions(+), 91 deletions(-)
reply other threads:[~2016-05-14 18:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20160514184447.GC14480@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).