From: sashiko-bot@kernel.org
To: "Christian Brauner" <brauner@kernel.org>, "Jan Kara" <jack@suse.com>
Cc: "Al Viro" <viro@zeniv.linux.org.uk>,
linux-ext4@vger.kernel.org, linux-mm@kvack.org,
linux-efi@vger.kernel.org, linux-mtd@lists.infradead.org,
dsterba@suse.cz, tytso@mit.edu, "Mark Fasheh" <mark@fasheh.com>,
"Joel Becker" <jlbec@evilplan.org>,
"Joseph Qi" <joseph.qi@linux.alibaba.com>
Subject: Re: [PATCH v3 12/33] exfat: use the generic emergency read-only state
Date: Sat, 14 Nov 2026 12:03:31 +0000 [thread overview]
Message-ID: <sashiko-outbox-214463@kernel.org> (raw)
In-Reply-To: <20261113-work-fs-sb_rdonly-v3-12-0be92bb73709@kernel.org>
Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [Medium] exfat: race with emergency read-only transition in
exfat_force_shutdown()
--
commit 55555fc2a6a36c47e1e61fcbe8c22b69f7d5a5f8
Author: Christian Brauner <brauner@kernel.org>
exfat: use the generic emergency read-only state
This commit replaces EXFAT_FLAGS_EMERGENCY_RO with the VFS generic
SB_STATE_EMERGENCY_RO state and skips freezing in exfat_force_shutdown()
when the superblock is already in the emergency read-only state.
> diff --git a/fs/exfat/super.c b/fs/exfat/super.c
> index feeda41a80741..e3587ed270245 100644
> --- a/fs/exfat/super.c
> +++ b/fs/exfat/super.c
[ ... ]
> @@ -176,6 +176,11 @@ int exfat_force_shutdown(struct super_block *sb, u32 flags)
> if (exfat_forced_shutdown(sb))
> return 0;
>
> + /* After an error there is nothing to sync and freezing fails. */
> + if ((flags == EXFAT_GOING_DOWN_DEFAULT ||
> + flags == EXFAT_GOING_DOWN_FULLSYNC) && sb_emergency_ro(sb))
> + flags = EXFAT_GOING_DOWN_NOSYNC;
> +
> switch (flags) {
> case EXFAT_GOING_DOWN_DEFAULT:
> case EXFAT_GOING_DOWN_FULLSYNC:
[Severity: Medium]
Can exfat_force_shutdown() abort without setting EXFAT_FLAGS_SHUTDOWN if a
filesystem error sets SB_STATE_EMERGENCY_RO while bdev_freeze() is running?
CPU0 CPU1
exfat_force_shutdown()
sb_emergency_ro(sb) -> false
bdev_freeze(sb->s_bdev)
...
freeze_super(sb, ...)
sb_wait_write(sb, ...) /
sync_filesystem(sb)
__exfat_fs_error(sb, ...)
sb_set_emergency_ro(sb)
if (!ret && sb_emergency_ro(sb))
ret = -EROFS;
if (ret)
return ret; <-- aborts without shutting down
Because freeze_super() checks sb_emergency_ro(sb) both on entry and after
sync_filesystem(sb), an in-flight writer or writeback error during the
freeze makes bdev_freeze() return -EROFS. exfat_force_shutdown() then
returns -EROFS without setting EXFAT_FLAGS_SHUTDOWN or clearing
opts->discard. Ignoring -EROFS from bdev_freeze() when sb_emergency_ro(sb)
is set would still complete the shutdown.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261113-work-fs-sb_rdonly-v3-0-0be92bb73709@kernel.org?part=12
WARNING: multiple messages have this Message-ID (diff)
From: sashiko-bot@kernel.org
To: "Christian Brauner" <brauner@kernel.org>, "Jan Kara" <jack@suse.com>
Cc: "Al Viro" <viro@zeniv.linux.org.uk>,
linux-ext4@vger.kernel.org, linux-mm@kvack.org,
linux-efi@vger.kernel.org, linux-mtd@lists.infradead.org,
dsterba@suse.cz, tytso@mit.edu, "Mark Fasheh" <mark@fasheh.com>,
"Joel Becker" <jlbec@evilplan.org>,
"Joseph Qi" <joseph.qi@linux.alibaba.com>
Subject: Re: [PATCH v3 12/33] exfat: use the generic emergency read-only state
Date: Sat, 14 Nov 2026 12:03:31 +0000 [thread overview]
Message-ID: <sashiko-outbox-214463@kernel.org> (raw)
In-Reply-To: <20261113-work-fs-sb_rdonly-v3-12-0be92bb73709@kernel.org>
Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [Medium] exfat: race with emergency read-only transition in
exfat_force_shutdown()
--
commit 55555fc2a6a36c47e1e61fcbe8c22b69f7d5a5f8
Author: Christian Brauner <brauner@kernel.org>
exfat: use the generic emergency read-only state
This commit replaces EXFAT_FLAGS_EMERGENCY_RO with the VFS generic
SB_STATE_EMERGENCY_RO state and skips freezing in exfat_force_shutdown()
when the superblock is already in the emergency read-only state.
> diff --git a/fs/exfat/super.c b/fs/exfat/super.c
> index feeda41a80741..e3587ed270245 100644
> --- a/fs/exfat/super.c
> +++ b/fs/exfat/super.c
[ ... ]
> @@ -176,6 +176,11 @@ int exfat_force_shutdown(struct super_block *sb, u32 flags)
> if (exfat_forced_shutdown(sb))
> return 0;
>
> + /* After an error there is nothing to sync and freezing fails. */
> + if ((flags == EXFAT_GOING_DOWN_DEFAULT ||
> + flags == EXFAT_GOING_DOWN_FULLSYNC) && sb_emergency_ro(sb))
> + flags = EXFAT_GOING_DOWN_NOSYNC;
> +
> switch (flags) {
> case EXFAT_GOING_DOWN_DEFAULT:
> case EXFAT_GOING_DOWN_FULLSYNC:
[Severity: Medium]
Can exfat_force_shutdown() abort without setting EXFAT_FLAGS_SHUTDOWN if a
filesystem error sets SB_STATE_EMERGENCY_RO while bdev_freeze() is running?
CPU0 CPU1
exfat_force_shutdown()
sb_emergency_ro(sb) -> false
bdev_freeze(sb->s_bdev)
...
freeze_super(sb, ...)
sb_wait_write(sb, ...) /
sync_filesystem(sb)
__exfat_fs_error(sb, ...)
sb_set_emergency_ro(sb)
if (!ret && sb_emergency_ro(sb))
ret = -EROFS;
if (ret)
return ret; <-- aborts without shutting down
Because freeze_super() checks sb_emergency_ro(sb) both on entry and after
sync_filesystem(sb), an in-flight writer or writeback error during the
freeze makes bdev_freeze() return -EROFS. exfat_force_shutdown() then
returns -EROFS without setting EXFAT_FLAGS_SHUTDOWN or clearing
opts->discard. Ignoring -EROFS from bdev_freeze() when sb_emergency_ro(sb)
is set would still complete the shutdown.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261113-work-fs-sb_rdonly-v3-0-0be92bb73709@kernel.org?part=12
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2026-11-14 12:03 UTC|newest]
Thread overview: 118+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 11:58 [PATCH v3 00/33] fs: don't set SB_RDONLY after filesystem errors Christian Brauner
2026-11-13 11:58 ` Christian Brauner
2026-11-13 11:58 ` [PATCH v3 01/33] jfs: free uncommitted anonymous tlocks when evicting an inode Christian Brauner
2026-11-13 11:58 ` Christian Brauner
2026-11-14 12:03 ` sashiko-bot
2026-11-14 12:03 ` sashiko-bot
2026-11-13 11:58 ` [PATCH v3 02/33] jfs: use jfs_symlink_inode_operations in jfs_iget() Christian Brauner
2026-11-13 11:58 ` Christian Brauner
2026-11-14 12:03 ` sashiko-bot
2026-11-13 11:58 ` [PATCH v3 03/33] ecryptfs: don't leak the inode when a lookup can't open the lower file Christian Brauner
2026-11-13 11:58 ` Christian Brauner
2026-11-14 12:03 ` sashiko-bot
2026-11-13 11:59 ` [PATCH v3 04/33] ecryptfs: fall back to a read-only " Christian Brauner
2026-11-13 11:59 ` Christian Brauner
2026-11-14 12:03 ` sashiko-bot
2026-11-13 11:59 ` [PATCH v3 05/33] fs: add a generic emergency read-only state Christian Brauner
2026-11-13 11:59 ` Christian Brauner
2026-11-13 14:53 ` Jan Kara
2026-11-13 14:53 ` Jan Kara
2026-11-14 12:03 ` sashiko-bot
2026-11-14 12:03 ` sashiko-bot
2026-11-13 11:59 ` [PATCH v3 06/33] ext2: don't set SB_RDONLY after filesystem errors Christian Brauner
2026-11-13 11:59 ` Christian Brauner
2026-11-13 14:54 ` Jan Kara
2026-11-13 14:54 ` Jan Kara
2026-11-14 12:03 ` sashiko-bot
2026-11-13 11:59 ` [PATCH v3 07/33] jfs: " Christian Brauner
2026-11-13 11:59 ` Christian Brauner
2026-11-14 12:03 ` sashiko-bot
2026-11-13 11:59 ` [PATCH v3 08/33] nilfs2: " Christian Brauner
2026-11-13 11:59 ` Christian Brauner
2026-11-14 12:03 ` sashiko-bot
2026-11-13 11:59 ` [PATCH v3 09/33] fat: " Christian Brauner
2026-11-13 11:59 ` Christian Brauner
2026-11-14 12:03 ` sashiko-bot
2026-11-14 12:03 ` sashiko-bot
2026-11-13 11:59 ` [PATCH v3 10/33] exfat: keep the current mount options on remount Christian Brauner
2026-11-13 11:59 ` Christian Brauner
2026-11-14 12:03 ` sashiko-bot
2026-11-13 11:59 ` [PATCH v3 11/33] exfat: don't set SB_RDONLY after filesystem errors Christian Brauner
2026-11-13 11:59 ` Christian Brauner
2026-11-14 12:03 ` sashiko-bot
2026-11-14 12:03 ` sashiko-bot
2026-11-13 11:59 ` [PATCH v3 12/33] exfat: use the generic emergency read-only state Christian Brauner
2026-11-13 11:59 ` Christian Brauner
2026-11-14 12:03 ` sashiko-bot [this message]
2026-11-14 12:03 ` sashiko-bot
2026-11-13 11:59 ` [PATCH v3 13/33] hfs: don't set SB_RDONLY after MDB write errors Christian Brauner
2026-11-13 11:59 ` Christian Brauner
2026-11-14 12:03 ` sashiko-bot
2026-11-14 12:03 ` sashiko-bot
2026-11-13 11:59 ` [PATCH v3 14/33] hfs: use the generic emergency read-only state Christian Brauner
2026-11-13 11:59 ` Christian Brauner
2026-11-14 12:03 ` sashiko-bot
2026-11-13 11:59 ` [PATCH v3 15/33] hfsplus: don't set SB_RDONLY when creating the attributes tree Christian Brauner
2026-11-13 11:59 ` Christian Brauner
2026-11-14 12:03 ` sashiko-bot
2026-11-13 11:59 ` [PATCH v3 16/33] affs: don't set SB_RDONLY after filesystem errors Christian Brauner
2026-11-13 11:59 ` Christian Brauner
2026-11-14 12:03 ` sashiko-bot
2026-11-13 11:59 ` [PATCH v3 17/33] ufs: " Christian Brauner
2026-11-13 11:59 ` Christian Brauner
2026-11-14 12:03 ` sashiko-bot
2026-11-14 12:03 ` sashiko-bot
2026-11-13 11:59 ` [PATCH v3 18/33] hpfs: " Christian Brauner
2026-11-13 11:59 ` Christian Brauner
2026-11-14 12:03 ` sashiko-bot
2026-11-13 11:59 ` [PATCH v3 19/33] ntfs: " Christian Brauner
2026-11-13 11:59 ` Christian Brauner
2026-11-14 12:03 ` sashiko-bot
2026-11-14 12:03 ` sashiko-bot
2026-11-13 11:59 ` [PATCH v3 20/33] ntfs: use the generic emergency read-only state Christian Brauner
2026-11-13 11:59 ` Christian Brauner
2026-11-14 12:03 ` sashiko-bot
2026-11-13 11:59 ` [PATCH v3 21/33] ocfs2: keep the current mount options on remount Christian Brauner
2026-11-13 11:59 ` Christian Brauner
2026-11-14 12:03 ` sashiko-bot
2026-11-13 11:59 ` [PATCH v3 22/33] ocfs2: don't set SB_RDONLY after filesystem errors Christian Brauner
2026-11-13 11:59 ` Christian Brauner
2026-11-14 12:03 ` sashiko-bot
2026-11-13 11:59 ` [PATCH v3 23/33] zonefs: don't set SB_RDONLY after I/O errors Christian Brauner
2026-11-13 11:59 ` Christian Brauner
2026-11-14 12:03 ` sashiko-bot
2026-11-13 11:59 ` [PATCH v3 24/33] zonefs: use the generic emergency read-only state Christian Brauner
2026-11-13 11:59 ` Christian Brauner
2026-11-14 12:03 ` sashiko-bot
2026-11-13 11:59 ` [PATCH v3 25/33] btrfs: check BTRFS_FS_STATE_RO instead of SB_RDONLY at runtime Christian Brauner
2026-11-13 11:59 ` Christian Brauner
2026-11-14 12:03 ` sashiko-bot
2026-11-13 11:59 ` [PATCH v3 26/33] btrfs: don't set SB_RDONLY after filesystem errors Christian Brauner
2026-11-13 11:59 ` Christian Brauner
2026-11-14 12:03 ` sashiko-bot
2026-11-14 12:03 ` sashiko-bot
2026-11-13 11:59 ` [PATCH v3 27/33] gfs2: wait for a pending withdraw before remounting read-only Christian Brauner
2026-11-13 11:59 ` Christian Brauner
2026-11-14 12:03 ` sashiko-bot
2026-11-14 12:03 ` sashiko-bot
2026-11-13 11:59 ` [PATCH v3 28/33] gfs2: don't set SB_RDONLY on withdraw Christian Brauner
2026-11-13 11:59 ` Christian Brauner
2026-11-14 12:03 ` sashiko-bot
2026-11-13 11:59 ` [PATCH v3 29/33] efivarfs: stop using SB_RDONLY for read-only efivar ops Christian Brauner
2026-11-13 11:59 ` Christian Brauner
2026-11-14 12:03 ` sashiko-bot
2026-11-13 11:59 ` [PATCH v3 30/33] ubifs: don't set SB_RDONLY after errors Christian Brauner
2026-11-13 11:59 ` Christian Brauner
2026-11-14 2:17 ` Zhihao Cheng
2026-11-14 2:17 ` Zhihao Cheng
2026-11-14 12:03 ` sashiko-bot
2026-11-14 12:03 ` sashiko-bot
2026-11-13 11:59 ` [PATCH v3 31/33] ext4: allow remounting read-only in the emergency state Christian Brauner
2026-11-13 11:59 ` Christian Brauner
2026-11-14 12:03 ` sashiko-bot
2026-11-13 11:59 ` [PATCH v3 32/33] ext4: use the generic emergency read-only state Christian Brauner
2026-11-13 11:59 ` Christian Brauner
2026-11-14 12:03 ` sashiko-bot
2026-11-13 11:59 ` [PATCH v3 33/33] xfs: allow remounting read-only after a shutdown Christian Brauner
2026-11-13 11:59 ` Christian Brauner
2026-11-14 12:03 ` sashiko-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=sashiko-outbox-214463@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=brauner@kernel.org \
--cc=dsterba@suse.cz \
--cc=jack@suse.com \
--cc=jlbec@evilplan.org \
--cc=joseph.qi@linux.alibaba.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-mtd@lists.infradead.org \
--cc=mark@fasheh.com \
--cc=sashiko-reviews@lists.linux.dev \
--cc=tytso@mit.edu \
--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.