From: Christian Brauner <christian.brauner@ubuntu.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] idmapped updates
Date: Tue, 31 Aug 2021 12:02:52 +0200 [thread overview]
Message-ID: <20210831100252.2298022-1-christian.brauner@ubuntu.com> (raw)
Hi Linus,
/* Summary */
The bulk of the idmapped work this cycle is adding support for idmapped mounts
to btrfs. While this required the addition of a (simple) new vfs helper all the
work is going through David Sterba's btrfs tree. It was way simpler to do it
this way rather then forcing David to coordinate between his btrfs and my tree.
Plus I don't care who merges it as long as I feel I can trust the maintainer
and the btrfs folks were really fast and helpful in reviewing this work.
As always, associated with the btrfs port for idmapped mounts is a new fstests
extension specifically concerned with btrfs ioctls (e.g. subvolume creation,
deletion etc.) on idmapped mounts which can be found in the fstests repo as
5f8179ce8b00 ("btrfs: introduce btrfs specific idmapped mounts tests").
Consequently, this PR should hopefully be boring. It only contains
documentation updates, specifically about how idmappings and idmapped mounts
work.
(In case any question come up I'll be on vacation next week so responding might
take a while.)
/* Testing */
All patches are based on v5.14-rc3 and have been sitting in linux-next. No
build failures or warnings were observed. All old and new tests are passing.
/* Conflicts */
At the time of creating this PR no merge conflicts were reported from
linux-next and no merge conflicts showed up doing a test-merge with current
mainline.
The following changes since commit ff1176468d368232b684f75e82563369208bc371:
Linux 5.14-rc3 (2021-07-25 15:35:14 -0700)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/brauner/linux tags/fs.idmapped.v5.15
for you to fetch changes up to ad19607a90b29eef044660aba92a2a2d63b1e977:
doc: give a more thorough id handling explanation (2021-08-11 15:28:32 +0200)
Please consider pulling these changes from the signed fs.idmapped.v5.15 tag.
Thanks!
Christian
----------------------------------------------------------------
fs.idmapped.v5.15
----------------------------------------------------------------
Christian Brauner (1):
doc: give a more thorough id handling explanation
Documentation/filesystems/idmappings.rst | 1026 ++++++++++++++++++++++++++++++
Documentation/filesystems/index.rst | 1 +
2 files changed, 1027 insertions(+)
create mode 100644 Documentation/filesystems/idmappings.rst
next reply other threads:[~2021-08-31 10:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-31 10:02 Christian Brauner [this message]
2021-08-31 19:52 ` pr-tracker-bot
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=20210831100252.2298022-1-christian.brauner@ubuntu.com \
--to=christian.brauner@ubuntu.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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
all inboxes | Powered by JetHome®