From: Miklos Szeredi <mszeredi@redhat.com>
To: Christian Brauner <christian@brauner.io>
Cc: 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: [PATCH 0/4] listmount changes
Date: Tue, 28 Nov 2023 17:03:31 +0100 [thread overview]
Message-ID: <20231128160337.29094-1-mszeredi@redhat.com> (raw)
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
commit 229dc17d71b0 ("listmount: guard against speculation")
Miklos Szeredi (4):
listmount: rip out flags
listmount: list mounts in ID order
listmount: small changes in semantics
listmount: allow continuing
fs/namespace.c | 93 +++++++++++++++-----------------------
include/uapi/linux/mount.h | 13 ++++--
2 files changed, 45 insertions(+), 61 deletions(-)
--
2.41.0
next reply other threads:[~2023-11-28 16:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-28 16:03 Miklos Szeredi [this message]
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
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=20231128160337.29094-1-mszeredi@redhat.com \
--to=mszeredi@redhat.com \
--cc=christian@brauner.io \
--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=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 read-only IMAP folder(s) and NNTP newsgroup(s).