Linux filesystem development
 help / color / mirror / Atom feed
From: Christian Brauner <brauner@kernel.org>
To: Al Viro <viro@zeniv.linux.org.uk>,
	Seth Forshee <sforshee@kernel.org>,
	Christian Brauner <brauner@kernel.org>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v4 0/4] fs: allow to mount beneath top mount
Date: Fri, 19 May 2023 12:52:00 +0200	[thread overview]
Message-ID: <20230519-aromen-zeugnis-5554bbb56ec1@brauner> (raw)
In-Reply-To: <20230202-fs-move-mount-replace-v4-0-98f3d80d7eaa@kernel.org>

On Wed, 03 May 2023 13:18:38 +0200, Christian Brauner wrote:
> Changes in v4:
> * Refuse MOVE_MOUNT_BENEATH in more cases.
> * Fix documentation of __lookup_mnt().
> * The sample program to test all of this got reworked:
>   https://github.com/brauner/move-mount-beneath
> 
> Various distributions are adding or are in the process of adding support
> for system extensions and in the future configuration extensions through
> various tools. A more detailed explanation on system and configuration
> extensions can be found on the manpage which is listed below at [1].
> 
> [...]

I'd like to see v4 get some -next exposure since this has been sitting
on the list for a while.

Applied to the v6.5/vfs.mount branch of the vfs/vfs.git tree.
Patches in the v6.5/vfs.mount 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.

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: v6.5/vfs.mount

[1/4] fs: add path_mounted()
      https://git.kernel.org/vfs/vfs/c/78aa08a8cab6
[2/4] fs: properly document __lookup_mnt()
      https://git.kernel.org/vfs/vfs/c/104026c2e49f
[3/4] fs: use a for loop when locking a mount
      https://git.kernel.org/vfs/vfs/c/64f44b27ae91
[4/4] fs: allow to mount beneath top mount
      https://git.kernel.org/vfs/vfs/c/6ac392815628

      parent reply	other threads:[~2023-05-19 10:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-03 11:18 [PATCH v4 0/4] fs: allow to mount beneath top mount Christian Brauner
2023-05-03 11:18 ` [PATCH v4 1/4] fs: add path_mounted() Christian Brauner
2023-05-03 11:18 ` [PATCH v4 2/4] fs: properly document __lookup_mnt() Christian Brauner
2023-05-03 11:18 ` [PATCH v4 3/4] fs: use a for loop when locking a mount Christian Brauner
2023-05-03 11:18 ` [PATCH v4 4/4] fs: allow to mount beneath top mount Christian Brauner
2023-05-11 14:19   ` Seth Forshee
2023-05-11 14:17 ` [PATCH v4 0/4] " Seth Forshee
2023-05-19 10: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=20230519-aromen-zeugnis-5554bbb56ec1@brauner \
    --to=brauner@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=sforshee@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