From: Al Viro <viro@zeniv.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org,
Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>
Subject: [git pull] several mount fixes
Date: Sat, 10 May 2025 07:02:48 +0100 [thread overview]
Message-ID: <20250510060248.GX2023217@ZenIV> (raw)
More stuff caught in mount code audit. There's more, but those'll have to
wait for several days...
A couple of races around legalize_mnt vs. umount (both fairly old and hard to
hit) plus two bugs in move_mount(2) - both around "move detached subtree in
place" logics.
The following changes since commit 92a09c47464d040866cf2b4cd052bc60555185fb:
Linux 6.15-rc5 (2025-05-04 13:55:04 -0700)
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 d1ddc6f1d9f0cf887834eb54a5a68bbfeec1bb77:
fix IS_MNT_PROPAGATING uses (2025-05-09 18:06:27 -0400)
----------------------------------------------------------------
assorted namespace fixes
----------------------------------------------------------------
Al Viro (4):
__legitimize_mnt(): check for MNT_SYNC_UMOUNT should be under mount_lock
do_umount(): add missing barrier before refcount checks in sync case
do_move_mount(): don't leak MNTNS_PROPAGATING on failures
fix IS_MNT_PROPAGATING uses
fs/namespace.c | 17 +++++++----------
fs/pnode.c | 17 +++++++++--------
fs/pnode.h | 2 +-
3 files changed, 17 insertions(+), 19 deletions(-)
next reply other threads:[~2025-05-10 6:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-10 6:02 Al Viro [this message]
2025-05-10 16:29 ` [git pull] several mount fixes 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=20250510060248.GX2023217@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--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.