All of lore.kernel.org
 help / color / mirror / Atom feed
From: Seth Forshee <sforshee@kernel.org>
To: Christian Brauner <brauner@kernel.org>
Cc: Al Viro <viro@zeniv.linux.org.uk>, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v4 0/4] fs: allow to mount beneath top mount
Date: Thu, 11 May 2023 07:17:58 -0700	[thread overview]
Message-ID: <ZFz5Fm7kVVFUc3FY@do-x1extreme> (raw)
In-Reply-To: <20230202-fs-move-mount-replace-v4-0-98f3d80d7eaa@kernel.org>

On Wed, May 03, 2023 at 01:18:38PM +0200, Christian Brauner wrote:
> Changes in v4:
> - Tweak the logic and helper that's used to prevent mounting beneath a
>   mount if the propagation relationship between the source mount, parent
>   mount, and top mount would lead to nonsensical mount trees.
> - Link to v3: https://lore.kernel.org/r/20230202-fs-move-mount-replace-v3-0-377893f74bc8@kernel.org
> 
> Changes in v3:
> - Refuse to mount source trees whose root has been overmounted after
>   path resolution of the source path has finished but before we grabbed
>   the namespace semaphore. This avoids the creation of shadow mounts.
> - Refuse to mount if the mount we're mounting beneath has been moved to
>   a different mountpoint before we grabbed the namespace semaphore.
> - Refuse to mount if the mount we're mounting beneath has been unmounted
>   before we grabbed the namespace semaphore.
> - Link to v2: https://lore.kernel.org/r/20230202-fs-move-mount-replace-v2-0-f53cd31d6392@kernel.org
> 
> Changes in v2:
> - s/MOVE_MOUNT_TUCK/MOVE_MOUNT_BENEATH/ which is a much clearer name.
> - Improve commit message.
> - Link to v1: https://lore.kernel.org/r/20230202-fs-move-mount-replace-v1-0-9b73026d5f10@kernel.org

Reviewed the changes since my last review. I'll send one
follow up about some wording in a comment, but other than that LGTM.

Reviewed-by: Seth Forshee (DigitalOcean) <sforshee@kernel.org>

  parent reply	other threads:[~2023-05-11 14:18 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 ` Seth Forshee [this message]
2023-05-19 10:52 ` [PATCH v4 0/4] " 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=ZFz5Fm7kVVFUc3FY@do-x1extreme \
    --to=sforshee@kernel.org \
    --cc=brauner@kernel.org \
    --cc=linux-fsdevel@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 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.