From: Christian Brauner <christian.brauner@ubuntu.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Christian Brauner <brauner@kernel.org>,
Seth Forshee <sforshee@digitalocean.com>,
Amir Goldstein <amir73il@gmail.com>,
Al Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v3 00/10] Extend and tweak mapping support
Date: Mon, 6 Dec 2021 15:27:52 +0100 [thread overview]
Message-ID: <20211206142752.54cigi5hhdudw4x2@wittgenstein> (raw)
In-Reply-To: <20211206141042.GA5488@lst.de>
On Mon, Dec 06, 2021 at 03:10:42PM +0100, Christoph Hellwig wrote:
> I think without the actual file system consumer this is a little pointless.
> Can you please post this with an actual user in a single series?
The series cleans up the semantics and naming of the low-level mapping
helpers something we started earlier this year. This just finishes that
work and generalizes the infrastructure. So I think this really should
stand on its own.
I really want to do this incrementally with the generic changes first so
we have time to watch for regressions. The series is also at its core a
semantic cleanup.
No matter if I send this in one or in two series I'd like this to be a
two-stage process where we first extend the generic infra and port
existing filesystems as we do here. Next cycle we then port overlayfs as
the first idmapped filesystem.
prev parent reply other threads:[~2021-12-06 14:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-03 11:16 [PATCH v3 00/10] Extend and tweak mapping support Christian Brauner
2021-12-03 11:16 ` [PATCH v3 01/10] fs: add is_idmapped_mnt() helper Christian Brauner
2021-12-03 11:16 ` [PATCH v3 02/10] fs: move mapping helpers Christian Brauner
2021-12-03 11:17 ` [PATCH v3 03/10] fs: tweak fsuidgid_has_mapping() Christian Brauner
2021-12-03 11:17 ` [PATCH v3 04/10] fs: account for filesystem mappings Christian Brauner
2021-12-03 11:17 ` [PATCH v3 05/10] docs: update mapping documentation Christian Brauner
2021-12-03 11:17 ` [PATCH v3 06/10] fs: use low-level mapping helpers Christian Brauner
2021-12-03 11:17 ` [PATCH v3 07/10] fs: remove unused " Christian Brauner
2021-12-03 11:17 ` [PATCH v3 08/10] fs: port higher-level " Christian Brauner
2021-12-03 11:17 ` [PATCH v3 09/10] fs: add i_user_ns() helper Christian Brauner
2021-12-03 11:17 ` [PATCH v3 10/10] fs: support mapped mounts of mapped filesystems Christian Brauner
2021-12-04 15:41 ` Seth Forshee
2021-12-06 14:10 ` [PATCH v3 00/10] Extend and tweak mapping support Christoph Hellwig
2021-12-06 14:27 ` Christian Brauner [this message]
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=20211206142752.54cigi5hhdudw4x2@wittgenstein \
--to=christian.brauner@ubuntu.com \
--cc=amir73il@gmail.com \
--cc=brauner@kernel.org \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=sforshee@digitalocean.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.