containers.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Alexey Gladkov <gladkov.alexey@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>,
	"Eric W . Biederman" <ebiederm@xmission.com>
Cc: Linux FS Devel <linux-fsdevel@vger.kernel.org>,
	Linux Containers <containers@lists.linux-foundation.org>,
	Alexey Gladkov <legion@kernel.org>,
	Alexander Viro <viro@zeniv.linux.org.uk>,
	Kees Cook <keescook@chromium.org>
Subject: [PATCH v5 0/5] proc: Relax check of mount visibility
Date: Wed, 10 Mar 2021 19:19:55 +0100	[thread overview]
Message-ID: <cover.1615400395.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 (5):
  docs: proc: add documentation about mount restrictions
  proc: Show /proc/self/net only for CAP_NET_ADMIN
  proc: Disable cancellation of subset=pid option
  proc: Relax check of mount visibility
  docs: proc: add documentation about relaxing visibility restrictions

 Documentation/filesystems/proc.rst | 18 ++++++++++++++++++
 fs/namespace.c                     | 27 ++++++++++++++++-----------
 fs/proc/proc_net.c                 |  8 ++++++++
 fs/proc/root.c                     | 25 +++++++++++++++++++------
 include/linux/fs.h                 |  1 +
 include/linux/proc_fs.h            |  1 +
 6 files changed, 63 insertions(+), 17 deletions(-)

-- 
2.29.2

_______________________________________________
Containers mailing list
Containers@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/containers

             reply	other threads:[~2021-03-10 18:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-10 18:19 Alexey Gladkov [this message]
2021-03-10 18:19 ` [PATCH v5 1/5] docs: proc: add documentation about mount restrictions Alexey Gladkov
2021-03-10 18:19 ` [PATCH v5 2/5] proc: Show /proc/self/net only for CAP_NET_ADMIN Alexey Gladkov
2021-03-10 18:19 ` [PATCH v5 3/5] proc: Disable cancellation of subset=pid option Alexey Gladkov
2021-03-10 18:19 ` [PATCH v5 4/5] proc: Relax check of mount visibility Alexey Gladkov
2021-03-10 19:42   ` kernel test robot
2021-03-10 18:20 ` [PATCH v5 5/5] docs: proc: add documentation about relaxing visibility restrictions Alexey Gladkov
2021-03-10 20:07 ` [PATCH v5 0/5] proc: Relax check of mount visibility 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.1615400395.git.gladkov.alexey@gmail.com \
    --to=gladkov.alexey@gmail.com \
    --cc=containers@lists.linux-foundation.org \
    --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).