From: Alexey Gladkov <gladkov.alexey@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>,
Linux FS Devel <linux-fsdevel@vger.kernel.org>,
"Eric W . Biederman" <ebiederm@xmission.com>
Cc: Alexey Gladkov <legion@kernel.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Kees Cook <keescook@chromium.org>
Subject: [PATCH v4 0/3] proc: Relax check of mount visibility
Date: Fri, 6 Nov 2020 16:15:09 +0100 [thread overview]
Message-ID: <cover.1604675649.git.gladkov.alexey@gmail.com> (raw)
If only the dynamic part of procfs is mounted (subset=pid), then there is no
need to check if procfs is fully visible to the user in the new user namespace.
Changelog
---------
v4:
* Set SB_I_DYNAMIC only if pidonly is set.
* Add an error message if subset=pid is canceled during remount.
v3:
* Add 'const' to struct cred *mounter_cred (fix kernel test robot warning).
v2:
* cache the mounters credentials and make access to the net directories
contingent of the permissions of the mounter of procfs.
--
Alexey Gladkov (3):
proc: Relax check of mount visibility
proc: Show /proc/self/net only for CAP_NET_ADMIN
proc: Disable cancellation of subset=pid option
fs/namespace.c | 27 ++++++++++++++++-----------
fs/proc/proc_net.c | 8 ++++++++
fs/proc/root.c | 29 ++++++++++++++++++++++-------
include/linux/fs.h | 1 +
include/linux/proc_fs.h | 1 +
5 files changed, 48 insertions(+), 18 deletions(-)
--
2.25.4
next reply other threads:[~2020-11-06 15:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-06 15:15 Alexey Gladkov [this message]
2020-11-06 15:15 ` [PATCH v4 1/3] proc: Relax check of mount visibility Alexey Gladkov
2020-11-06 15:15 ` [PATCH v4 2/3] proc: Show /proc/self/net only for CAP_NET_ADMIN Alexey Gladkov
2020-11-06 15:15 ` [PATCH v4 3/3] proc: Disable cancellation of subset=pid option Alexey Gladkov
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=cover.1604675649.git.gladkov.alexey@gmail.com \
--to=gladkov.alexey@gmail.com \
--cc=ebiederm@xmission.com \
--cc=keescook@chromium.org \
--cc=legion@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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).