From: Al Viro <viro@zeniv.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Christian Brauner <brauner@kernel.org>,
Allison Karlitskaya <lis@redhat.com>,
linux-fsdevel@vger.kernel.org
Subject: [git pull] regression fix for mount propagation in detached trees
Date: Fri, 30 May 2025 20:04:47 +0100 [thread overview]
Message-ID: <20250530190447.GA3574388@ZenIV> (raw)
6.15 allowed mount propagation to destinations in detached trees;
unfortunately, that breaks existing userland, so the old behaviour
needs to be restored.
It's not exactly a revert - original behaviour had a bug, where existence
of detached tree might disrupt propagation between locations not in
detached trees. Thankfully, userland did not upon that bug, so we
want to keep the fix.
The following changes since commit d1ddc6f1d9f0cf887834eb54a5a68bbfeec1bb77:
fix IS_MNT_PROPAGATING uses (2025-05-09 18:06:27 -0400)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git tags/pull-fixes
for you to fetch changes up to 3b5260d12b1fe76b566fe182de8abc586b827ed0:
Don't propagate mounts into detached trees (2025-05-26 17:35:32 -0400)
----------------------------------------------------------------
6.15 behaviour wrt mount propagation into detached trees breaks userland.
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
----------------------------------------------------------------
Al Viro (1):
Don't propagate mounts into detached trees
fs/mount.h | 5 -----
fs/namespace.c | 15 ++-------------
fs/pnode.c | 4 ++--
3 files changed, 4 insertions(+), 20 deletions(-)
next reply other threads:[~2025-05-30 19:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-30 19:04 Al Viro [this message]
2025-05-30 23:17 ` [git pull] regression fix for mount propagation in detached trees 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=20250530190447.GA3574388@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=brauner@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lis@redhat.com \
--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 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.