From: Miklos Szeredi <miklos@szeredi.hu>
To: Christian Brauner <brauner@kernel.org>
Cc: Miklos Szeredi <mszeredi@redhat.com>,
linux-api@vger.kernel.org, linux-man@vger.kernel.org,
linux-security-module@vger.kernel.org,
Karel Zak <kzak@redhat.com>,
linux-fsdevel@vger.kernel.org, Ian Kent <raven@themaw.net>,
David Howells <dhowells@redhat.com>,
Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: [PATCH 0/4] listmount changes
Date: Wed, 29 Nov 2023 11:22:03 +0100 [thread overview]
Message-ID: <CAJfpegsTGq0TW0oFDnYiTeM+z66M73k1jXXjFE6GwebPQYSgGA@mail.gmail.com> (raw)
In-Reply-To: <20231129-rinnen-gekapert-c3875be7c9da@brauner>
On Wed, 29 Nov 2023 at 10:53, Christian Brauner <brauner@kernel.org> wrote:
>
> On Tue, 28 Nov 2023 17:03:31 +0100, Miklos Szeredi wrote:
> > This came out from me thinking about the best libc API. It contains a few
> > changes that simplify and (I think) improve the interface.
> >
> > Tree:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git#vfs.mount
> >
> > [...]
>
> Afaict, all changes as discussed. Thanks. I folded the fixes into the
> main commit. Links to the patches that were folded are in the commit
> message and explained in there as well. The final commit is now rather
> small and easy to read.
Looks good, thanks for folding the patches.
> * Remove explicit LISTMOUNT_UNREACHABLE flag (cf. [1]). That
> functionality can simply be made available by checking for required
> privileges. If the caller is sufficiently privileged then list mounts
> that can't be reached from the current root. If the caller isn't skip
> mounts that can't be reached from the current root. This also makes
> permission checking consistent with statmount() (cf. [3]).
Skipping mounts based on privileges was what the initial version did.
That inconsistency was the reason for introducing
LISTMOUNT_UNREACHABLE. The final version doesn't skip mounts based on
privileges, either all submounts are listed or the request is rejected
with -EPERM.
For the case when some submounts are inside root and some are outside
useing LSMT_ROOT should be sufficient. LSMT_ROOT won't fail due to
insufficient privileges, since by definition it lists only mounts that
are below root.
Thanks,
Miklos
next prev parent reply other threads:[~2023-11-29 10:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-28 16:03 [PATCH 0/4] listmount changes Miklos Szeredi
2023-11-28 16:03 ` [PATCH 1/4] listmount: rip out flags Miklos Szeredi
2023-11-28 16:03 ` [PATCH 2/4] listmount: list mounts in ID order Miklos Szeredi
2023-11-28 16:03 ` [PATCH 3/4] listmount: small changes in semantics Miklos Szeredi
2023-12-06 19:58 ` Serge E. Hallyn
2023-12-06 20:24 ` Miklos Szeredi
2023-12-08 13:07 ` Christian Brauner
2023-11-28 16:03 ` [PATCH 4/4] listmount: allow continuing Miklos Szeredi
2023-11-29 9:52 ` [PATCH 0/4] listmount changes Christian Brauner
2023-11-29 10:22 ` Miklos Szeredi [this message]
2023-11-29 10:40 ` Christian Brauner
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=CAJfpegsTGq0TW0oFDnYiTeM+z66M73k1jXXjFE6GwebPQYSgGA@mail.gmail.com \
--to=miklos@szeredi.hu \
--cc=brauner@kernel.org \
--cc=dhowells@redhat.com \
--cc=kzak@redhat.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mszeredi@redhat.com \
--cc=raven@themaw.net \
--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).