linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Brauner <brauner@kernel.org>
To: linux-fsdevel@vger.kernel.org, Seth Forshee <sforshee@kernel.org>,
	Christian Brauner <brauner@kernel.org>
Subject: Re: [PATCH 0/4] mnt_idmapping: decouple from namespaces
Date: Fri, 24 Nov 2023 08:52:15 +0100	[thread overview]
Message-ID: <20231124-lachen-anorak-4bd3f6a766e2@brauner> (raw)
In-Reply-To: <20231122-vfs-mnt_idmap-v1-0-dae4abdde5bd@kernel.org>

On Wed, 22 Nov 2023 13:44:36 +0100, Christian Brauner wrote:
> Hey,
> 
> This is a tiny series to fully decouple idmapped mounts from namespaces.
> We already have a dedicated type and nothing matters from a namespace
> apart from it's permissions. So just get rid of it. Also means we could
> extend this to allow changing of idmapping completely independent of
> namespaces in the future. There's no need to tie them that close
> together.
> 
> [...]

Applied to the vfs.misc branch of the vfs/vfs.git tree.
Patches in the vfs.misc branch should appear in linux-next soon.

Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.

It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.

Note that commit hashes shown below are subject to change due to rebase,
trailer updates or similar. If in doubt, please check the listed branch.

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs.misc

[1/4] mnt_idmapping: remove check_fsmapping()
      https://git.kernel.org/vfs/vfs/c/a4fd34a68d61
[2/4] mnt_idmapping: remove nop check
      https://git.kernel.org/vfs/vfs/c/b77a69e35261
[3/4] mnt_idmapping: decouple from namespaces
      https://git.kernel.org/vfs/vfs/c/cc8ac0ea8188
[4/4] fs: reformat idmapped mounts entry
      https://git.kernel.org/vfs/vfs/c/5c7b656ebb3b

      parent reply	other threads:[~2023-11-24  7:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-22 12:44 [PATCH 0/4] mnt_idmapping: decouple from namespaces Christian Brauner
2023-11-22 12:44 ` [PATCH 1/4] mnt_idmapping: remove check_fsmapping() Christian Brauner
2023-11-22 12:44 ` [PATCH 2/4] mnt_idmapping: remove nop check Christian Brauner
2023-11-22 12:44 ` [PATCH 3/4] mnt_idmapping: decouple from namespaces Christian Brauner
2023-11-22 14:26   ` Josef Bacik
2023-11-22 14:34     ` Christian Brauner
2023-11-22 15:14       ` Josef Bacik
2023-11-22 12:44 ` [PATCH 4/4] fs: reformat idmapped mounts entry Christian Brauner
2023-11-24  7:52 ` 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=20231124-lachen-anorak-4bd3f6a766e2@brauner \
    --to=brauner@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=sforshee@kernel.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;
as well as URLs for NNTP newsgroup(s).