From: Chi Zhiling <chizhiling@163.com>
To: exfat@lists.linux.dev, linux-kernel@vger.kernel.org
Cc: Yuezhang.Mo@sony.com, dxdt@dev.snart.me, linkinjeon@kernel.org,
sj1557.seo@samsung.com, Chi Zhiling <chizhiling@kylinos.cn>
Subject: [PATCH v2 3/7] exfat: validate cached iomaps during buffered writes
Date: Tue, 13 Oct 2026 11:38:33 +0800 [thread overview]
Message-ID: <20261013033837.2748258-4-chizhiling@163.com> (raw)
In-Reply-To: <20261013033837.2748258-1-chizhiling@163.com>
From: Chi Zhiling <chizhiling@kylinos.cn>
The next patch, "exfat: drop i_rwsem from exfat_page_mkwrite()", allows a
fault to advance valid_size under the folio lock without serializing
against an in-flight buffered write. As a result, valid_size may advance
into a folio covered by a cached iomap. Reusing that iomap would cause
__iomap_write_begin() to zero the wrong part of the block.
Add an ->iomap_valid callback that compares ->validity_cookie against the
current valid_size and forces a remap if valid_size has advanced into the
locked folio, whose pointer is stored in ->private by ->get_folio.
Signed-off-by: Chi Zhiling <chizhiling@kylinos.cn>
---
fs/exfat/iomap.c | 38 +++++++++++++++++++++++++++++++++++++-
1 file changed, 37 insertions(+), 1 deletion(-)
diff --git a/fs/exfat/iomap.c b/fs/exfat/iomap.c
index f3816509c6e5..26d216ef9c44 100644
--- a/fs/exfat/iomap.c
+++ b/fs/exfat/iomap.c
@@ -57,6 +57,7 @@ static int __exfat_iomap_begin(struct inode *inode, loff_t offset, loff_t length
iomap->addr = IOMAP_NULL_ADDR;
iomap->offset = offset;
iomap->length = length;
+ iomap->validity_cookie = valid_size;
return 0;
}
@@ -145,7 +146,7 @@ static int __exfat_iomap_begin(struct inode *inode, loff_t offset, loff_t length
}
}
- iomap->flags |= IOMAP_F_MERGED;
+ iomap->validity_cookie = valid_size;
out:
mutex_unlock(&sbi->s_lock);
return err;
@@ -252,6 +253,17 @@ const struct iomap_ops exfat_write_iomap_ops = {
.iomap_next = exfat_write_iomap_next,
};
+static struct folio *exfat_iomap_get_folio(struct iomap_iter *iter, loff_t pos,
+ unsigned int len)
+{
+ struct folio *folio = iomap_get_folio(iter, pos, len);
+
+ if (!IS_ERR(folio))
+ iter->iomap.private = folio;
+
+ return folio;
+}
+
static void exfat_iomap_put_folio(struct inode *inode, loff_t pos,
unsigned int copied, struct folio *folio)
{
@@ -264,8 +276,32 @@ static void exfat_iomap_put_folio(struct inode *inode, loff_t pos,
folio_put(folio);
}
+static bool exfat_iomap_valid(struct inode *inode, const struct iomap *iomap)
+{
+ struct folio *folio = iomap->private;
+ loff_t old_valid_size = iomap->validity_cookie;
+ loff_t valid_size = exfat_get_valid_size(EXFAT_I(inode));
+
+ if (valid_size == old_valid_size)
+ return true;
+
+ if (!folio)
+ return false;
+
+ /* Still valid for this folio. */
+ if (old_valid_size >= folio_next_pos(folio))
+ return true;
+
+ if (valid_size <= folio_pos(folio))
+ return true;
+
+ return false;
+}
+
const struct iomap_write_ops exfat_iomap_write_ops = {
+ .get_folio = exfat_iomap_get_folio,
.put_folio = exfat_iomap_put_folio,
+ .iomap_valid = exfat_iomap_valid,
};
/*
--
2.53.0
next prev parent reply other threads:[~2026-10-13 3:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 3:38 [PATCH v2 0/7] exfat: fix valid_size update races Chi Zhiling
2026-10-13 3:38 ` [PATCH v2 1/7] exfat: advance valid_size under the folio lock for buffered writes Chi Zhiling
2026-10-13 3:38 ` [PATCH v2 2/7] exfat: advance valid_size while zeroing new ranges Chi Zhiling
2026-10-13 3:38 ` Chi Zhiling [this message]
2026-10-13 3:38 ` [PATCH v2 4/7] exfat: drop i_rwsem from exfat_page_mkwrite Chi Zhiling
2026-10-13 3:38 ` [PATCH v2 5/7] exfat: do not re-zero the valid range in exfat_page_mkwrite Chi Zhiling
2026-10-13 3:38 ` [PATCH v2 6/7] exfat: complete direct writes synchronously when they update metadata Chi Zhiling
2026-10-13 3:38 ` [PATCH v2 7/7] exfat: publish i_size and valid_size on direct I/O completion Chi Zhiling
2026-10-13 4:04 ` [PATCH v2 0/7] exfat: fix valid_size update races Namjae Jeon
2026-10-13 6:02 ` Chi Zhiling
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=20261013033837.2748258-4-chizhiling@163.com \
--to=chizhiling@163.com \
--cc=Yuezhang.Mo@sony.com \
--cc=chizhiling@kylinos.cn \
--cc=dxdt@dev.snart.me \
--cc=exfat@lists.linux.dev \
--cc=linkinjeon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sj1557.seo@samsung.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®