diff options
| author | Chao Shi <coshi036@gmail.com> | 2026-08-06 12:58:33 -0400 |
|---|---|---|
| committer | Christian Brauner <brauner@kernel.org> | 2026-09-10 09:27:24 +0200 |
| commit | 5089db0f2dd38a64921eb44e55eb78dfd0b242fc (patch) | |
| tree | 64335fbee9f8dff1695318942fd27de2703de110 /tools/lib/python/kdoc/python_version.py | |
| parent | 5c49ba63bead84b0584a57095a703147cca6c811 (diff) | |
| download | linux-next-5089db0f2dd38a64921eb44e55eb78dfd0b242fc.tar.gz linux-next-5089db0f2dd38a64921eb44e55eb78dfd0b242fc.zip | |
omfs: check for an inode write error with buffer_write_io_error()
__omfs_write_inode() spots a failed synchronous write, on both the primary
block and each mirror, by testing BH_Req together with !BH_Uptodate. 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.
BH_Write_EIO says exactly what this code wants to know, and it implies
BH_Req, so each pair collapses into one test.
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/b33ccb12c29ae743ccfa48cdf1e9140fbf2dabcc.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