From: Christian Brauner <christian.brauner@ubuntu.com>
To: David Sterba <dsterba@suse.com>
Cc: Christoph Hellwig <hch@lst.de>, Chris Mason <clm@fb.com>,
Josef Bacik <josef@toxicpanda.com>,
Al Viro <viro@zeniv.linux.org.uk>,
linux-btrfs@vger.kernel.org,
Christian Brauner <brauner@kernel.org>
Subject: Re: [PATCH v4 00/21] btrfs: support idmapped mounts
Date: Mon, 2 Aug 2021 14:28:27 +0200 [thread overview]
Message-ID: <20210802122827.aomsh5i3rljgm2r3@wittgenstein> (raw)
In-Reply-To: <20210727104900.829215-1-brauner@kernel.org>
On Tue, Jul 27, 2021 at 12:48:39PM +0200, Christian Brauner wrote:
> From: Christian Brauner <christian.brauner@ubuntu.com>
>
> Hey everyone,
>
> /* v4 */
> Rename new helper to lookup_one() and add new Reviewed-bys.
>
> This series enables the creation of idmapped mounts on btrfs. On the list of
> filesystems btrfs was pretty high-up and requested quite often from userspace
> (cf. [1]). This series requires just a few changes to the vfs for specific
> lookup helpers that btrfs relies on to perform permission checking when looking
> up an inode. The changes are required to port some other filesystem as well.
>
> The conversion of the necessary btrfs internals was fairly straightforward. No
> invasive changes were needed. I've decided to split up the patchset into very
> small individual patches. This hopefully makes the series more readable and
> fairly easy to review. The overall changeset is quite small.
>
> All non-filesystem wide ioctls that peform permission checking based on inodes
> can be supported on idmapped mounts. There are really just a few restrictions.
> This should really only affect the deletion of subvolumes by subvolume id which
> can be used to delete any subvolume in the filesystem even though the caller
> might not even be able to see the subvolume under their mount. Other than that
> behavior on idmapped and non-idmapped mounts is identical for all enabled
> ioctls. People interested in idmappings on idmapped mounts should read [2].
>
> The changeset has an associated new testsuite specific to btrfs. The
> core vfs operations that btrfs implements are covered by the generic
> idmapped mount testsuite. For the ioctls a new testsuite was added. It
> is sent alongside this patchset for ease of review but will very likely
> be merged independent of it.
>
> All patches are based on v5.14-rc3.
>
> The series can be pulled from:
> https://git.kernel.org/brauner/h/fs.idmapped.btrfs
> https://github.com/brauner/linux/tree/fs.idmapped.btrfs
>
> The xfstests can be pulled from:
> https://git.kernel.org/brauner/xfstests-dev/h/fs.idmapped.btrfs
> https://github.com/brauner/xfstests/tree/fs.idmapped.btrfs
>
> Note, the new btrfs xfstests patch is on top of a branch of mine
> containing a few more preliminary patches. So if you want to run the
> tests, please simply pull the branch and build from there.
>
> The series has been tested with xfstests including the newly added btrfs
> specific test. All tests pass.
> There were three unrelated failures that I observed: btrfs/219,
> btrfs/2020 and btrfs/235. All three also fail on earlier kernels
> without the patch series applied.
Hey David,
Sorry to ping, could I answer the outstanding questions you had and are
you okay with this series?
Christian
next prev parent reply other threads:[~2021-08-02 12:28 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-27 10:48 [PATCH v4 00/21] btrfs: support idmapped mounts Christian Brauner
2021-07-27 10:48 ` [PATCH v4 01/21] namei: add mapping aware lookup helper Christian Brauner
2021-08-02 12:24 ` Christian Brauner
2021-08-10 13:42 ` Christoph Hellwig
2021-07-27 10:48 ` [PATCH v4 02/21] btrfs/inode: handle idmaps in btrfs_new_inode() Christian Brauner
2021-07-27 10:48 ` [PATCH v4 03/21] btrfs/inode: allow idmapped rename iop Christian Brauner
2021-07-27 10:48 ` [PATCH v4 04/21] btrfs/inode: allow idmapped getattr iop Christian Brauner
2021-07-27 10:48 ` [PATCH v4 05/21] btrfs/inode: allow idmapped mknod iop Christian Brauner
2021-07-27 10:48 ` [PATCH v4 06/21] btrfs/inode: allow idmapped create iop Christian Brauner
2021-07-27 10:48 ` [PATCH v4 07/21] btrfs/inode: allow idmapped mkdir iop Christian Brauner
2021-07-27 10:48 ` [PATCH v4 08/21] btrfs/inode: allow idmapped symlink iop Christian Brauner
2021-07-27 10:48 ` [PATCH v4 09/21] btrfs/inode: allow idmapped tmpfile iop Christian Brauner
2021-07-27 10:48 ` [PATCH v4 10/21] btrfs/inode: allow idmapped setattr iop Christian Brauner
2021-07-27 10:48 ` [PATCH v4 11/21] btrfs/inode: allow idmapped permission iop Christian Brauner
2021-07-27 10:48 ` [PATCH v4 12/21] btrfs/ioctl: check whether fs{g,u}id are mapped during subvolume creation Christian Brauner
2021-07-27 10:48 ` [PATCH v4 13/21] btrfs/inode: allow idmapped BTRFS_IOC_{SNAP,SUBVOL}_CREATE{_V2} ioctl Christian Brauner
2021-07-27 10:48 ` [PATCH v4 14/21] btrfs/ioctl: allow idmapped BTRFS_IOC_SNAP_DESTROY{_V2} ioctl Christian Brauner
2021-07-27 10:48 ` [PATCH v4 15/21] btrfs/ioctl: relax restrictions for BTRFS_IOC_SNAP_DESTROY_V2 with subvolids Christian Brauner
2021-07-27 10:48 ` [PATCH v4 16/21] btrfs/ioctl: allow idmapped BTRFS_IOC_SET_RECEIVED_SUBVOL{_32} ioctl Christian Brauner
2021-07-27 10:48 ` [PATCH v4 17/21] btrfs/ioctl: allow idmapped BTRFS_IOC_SUBVOL_SETFLAGS ioctl Christian Brauner
2021-07-27 10:48 ` [PATCH v4 18/21] btrfs/ioctl: allow idmapped BTRFS_IOC_INO_LOOKUP_USER ioctl Christian Brauner
2021-07-27 10:48 ` [PATCH v4 19/21] btrfs/acl: handle idmapped mounts Christian Brauner
2021-07-27 10:48 ` [PATCH v4 20/21] btrfs/super: allow idmapped btrfs Christian Brauner
2021-07-27 10:49 ` [PATCH v4 21/21] btrfs/242: introduce btrfs specific idmapped mounts tests Christian Brauner
2021-08-02 12:28 ` Christian Brauner [this message]
2021-08-09 10:12 ` [PATCH v4 00/21] btrfs: support idmapped mounts Christian Brauner
2021-08-09 14:44 ` David Sterba
2021-08-09 15:20 ` Christian Brauner
2021-08-11 10:12 ` David Sterba
2021-08-11 10:43 ` Christian Brauner
2021-08-11 10:52 ` David Sterba
2021-08-11 13:29 ` 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=20210802122827.aomsh5i3rljgm2r3@wittgenstein \
--to=christian.brauner@ubuntu.com \
--cc=brauner@kernel.org \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=hch@lst.de \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@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).