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] work.sane_pwd
Date: Fri, 12 May 2017 02:14:47 +0100 [thread overview]
Message-ID: <20170512011445.GN390@ZenIV.linux.org.uk> (raw)
Making sure that something like a referral point won't end up
as pwd or root. The main part is the last commit (fixing mntns_install());
that one fixes a hard-to-hit race. fchdir() one is making fchdir(2)
a bit more robust - it should be impossible to get opened files (even
O_PATH ones) for referral points in the first place, so the existing
checks are OK, but checking the same thing as in chdir(2) is just as
cheap. path_init() commit removes a redundant check that shouldn't
have been there in the first place.
The following changes since commit 85128b2be6738fe36c224995c5ee80fe80fbb1b5:
fix nfs O_DIRECT advancing iov_iter too much (2017-04-17 14:23:20 -0400)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.sane_pwd
for you to fetch changes up to 4f757f3cbf54edef7b75c68d6d6d2f1a0ca08d2e:
make sure that mntns_install() doesn't end up with referral for root (2017-04-21 14:05:36 -0400)
----------------------------------------------------------------
Al Viro (3):
make sure that fchdir() won't accept referral points, etc.
path_init(): don't bother with checking MAY_EXEC for LOOKUP_ROOT
make sure that mntns_install() doesn't end up with referral for root
fs/namei.c | 48 ++++++++++++++++++++++++++++++++++++++++--------
fs/namespace.c | 18 +++++++++++-------
fs/open.c | 9 +++------
include/linux/namei.h | 1 +
4 files changed, 55 insertions(+), 21 deletions(-)
reply other threads:[~2017-05-12 1:14 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=20170512011445.GN390@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).