[PATCH linux-next] exfat: check the emergency state in exfat_writeback_range()

From: Sasha Levin

Date: Thu Nov 19 2026 - 19:35:18 EST


The vfs.all merge in next-20261119 takes the exfat side in
exfat_writepages(), where b900c61a3f21 ("exfat: drain dirty pages after
forced shutdown") moved the shutdown check into exfat_writeback_range(),
but leaves exfat_writeback_range() with exfat_forced_shutdown(). So the
exfat_emergency_state() check that 788f21d1f192 ("exfat: don't set
SB_RDONLY after filesystem errors") adds to writeback is lost, and after
an error with errors=remount-ro writeback keeps writing dirty data.

next-20261118 had exfat_emergency_state() in exfat_writeback_range().
Put it back.

Fixes: 026bdab726d8 ("Merge branch 'vfs.all' of https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git";)
Link: https://lore.kernel.org/all/av2mOPyANz3H59F5@xxxxxxxxxxxxx/
Signed-off-by: Sasha Levin <sashal@xxxxxxxxxx>
---
This is for folding into the vfs.all merge in fs-next. Built fs/exfat on
x86_64 (defconfig plus EXFAT_FS=m, W=1).

fs/exfat/iomap.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/fs/exfat/iomap.c b/fs/exfat/iomap.c
index d0bcf523f48b5..a846fbc450b82 100644
--- a/fs/exfat/iomap.c
+++ b/fs/exfat/iomap.c
@@ -374,14 +374,14 @@ static ssize_t exfat_writeback_range(struct iomap_writepage_ctx *wpc,
struct folio *folio, u64 offset, unsigned int len, u64 end_pos)
{
struct inode *inode = wpc->inode;
+ int error;

- if (exfat_forced_shutdown(inode->i_sb))
- return -EIO;
+ error = exfat_emergency_state(inode->i_sb);
+ if (error)
+ return error;

if (offset < wpc->iomap.offset ||
offset >= wpc->iomap.offset + wpc->iomap.length) {
- int error;
-
error = __exfat_iomap_begin(inode, offset, len,
0, &wpc->iomap, false,
exfat_get_valid_size(EXFAT_I(inode)));

base-commit: adcad7f4e6332cff3d6d7165f41584899f598534
--
2.53.0