From: Christian Brauner <brauner@kernel.org>
To: linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
exfat@lists.linux.dev, linux-kernel@vger.kernel.org,
Chi Zhiling <chizhiling@163.com>
Cc: Namjae Jeon <linkinjeon@kernel.org>,
Sungjong Seo <sj1557.seo@samsung.com>,
Yuezhang Mo <yuezhang.mo@sony.com>,
"Darrick J. Wong" <djwong@kernel.org>,
Chi Zhiling <chizhiling@kylinos.cn>
Subject: Re: (subset) [PATCH v4 0/5] exfat: fix valid_size update races
Date: Tue, 17 Nov 2026 18:16:45 +0100 [thread overview]
Message-ID: <20261117-heilbad-seile-oberdeck-5bf79ca6d840@brauner> (raw)
In-Reply-To: <20261116085752.3908082-1-chizhiling@163.com>
On Mon, 16 Nov 2026 16:57:47 +0800, Chi Zhiling wrote:
> From: Chi Zhiling <chizhiling@kylinos.cn>
>
> exFAT uses valid_size (ValidDataLength) as the on-disk boundary of
> initialised data, but the current code advances it too late and without
> proper serialisation. Buffered writes can silently lose data reclaimed
> before valid_size covers it, file expansion and page faults can
> initialise the same range concurrently, and a failed or short direct
> write can still grow the file on disk.
>
> [...]
Applied to the vfs-7.5.iomap branch of the vfs/vfs.git tree.
Patches in the vfs-7.5.iomap branch should appear in linux-next soon.
Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.
It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.
Note that commit hashes shown below are subject to change due to rebase,
trailer updates or similar. If in doubt, please check the listed branch.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs-7.5.iomap
[1/5] iomap: export iomap_bio_read_folio_range_sync()
https://git.kernel.org/vfs/vfs/c/4c7bbc7f82ff
prev parent reply other threads:[~2026-11-17 17:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-16 8:57 Chi Zhiling
2026-11-16 8:57 ` [PATCH v4 1/5] iomap: export iomap_bio_read_folio_range_sync() Chi Zhiling
2026-11-17 11:15 ` Namjae Jeon
2026-11-16 8:57 ` [PATCH v4 2/5] exfat: increase VDL before unlocking initialized folios Chi Zhiling
2026-11-16 8:57 ` [PATCH v4 3/5] exfat: zero invalid VDL tails in buffered and direct reads Chi Zhiling
2026-11-16 8:57 ` [PATCH v4 4/5] exfat: serialize file expansion with mmap write faults Chi Zhiling
2026-11-16 8:57 ` [PATCH v4 5/5] exfat: coordinate direct writes with mmap faults Chi Zhiling
2026-11-17 17:16 ` Christian Brauner [this message]
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=20261117-heilbad-seile-oberdeck-5bf79ca6d840@brauner \
--to=brauner@kernel.org \
--cc=chizhiling@163.com \
--cc=chizhiling@kylinos.cn \
--cc=djwong@kernel.org \
--cc=exfat@lists.linux.dev \
--cc=linkinjeon@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=sj1557.seo@samsung.com \
--cc=yuezhang.mo@sony.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®