diff options
| author | Chao Shi <coshi036@gmail.com> | 2026-08-06 12:58:35 -0400 |
|---|---|---|
| committer | Christian Brauner <brauner@kernel.org> | 2026-09-10 09:27:25 +0200 |
| commit | 8417ab622ffc140960818420cf72d42ecd3a12fe (patch) | |
| tree | 971ef6ff87e132ab6e8b08b1ea69f26c66e8fcd7 /tools/lib/python/kdoc/python_version.py | |
| parent | 0015b215eb6270d3e6bb5437b5198f5c38f4d2cd (diff) | |
| download | linux-next-8417ab622ffc140960818420cf72d42ecd3a12fe.tar.gz linux-next-8417ab622ffc140960818420cf72d42ecd3a12fe.zip | |
fat: check for a metadata write error with buffer_write_io_error()
fat_sync_bhs() waits for the writes it issued and then tests
!buffer_uptodate() to find the ones that failed. That relies on the write
completion handler clearing BH_Uptodate on error, which this series
removes: a buffer whose write failed still holds the data the filesystem
asked to be written, so declaring it not up to date is wrong and makes
callers re-read it.
Test BH_Write_EIO, which is what the completion handler sets and what this
code actually wants to know.
No behaviour change today - a failed write sets BH_Write_EIO and clears
BH_Uptodate together. It stops being a no-op at the end of the series,
where the new test is the one that still works.
Acked-by: Weidong Zhu <weizhu@fiu.edu>
Signed-off-by: Chao Shi <coshi036@gmail.com>
Link: https://patch.msgid.link/4b6019b5a48b83c8235918b084248983a57692e1.1785951556.git.coshi036@gmail.com
Reviewed-by: Jan Kara <jack@suse.cz>
Signed-off-by: Christian Brauner (Amutable) <brauner@kernel.org>
Diffstat (limited to 'tools/lib/python/kdoc/python_version.py')
0 files changed, 0 insertions, 0 deletions