diff options
| author | Chao Shi <coshi036@gmail.com> | 2026-08-06 12:58:41 -0400 |
|---|---|---|
| committer | Christian Brauner <brauner@kernel.org> | 2026-09-10 09:27:26 +0200 |
| commit | b1c88ae0b554322fa29b4b490ce0b09c2c84ec52 (patch) | |
| tree | e5c0e6f90589420d83273f897ce8dafc86bfb14b /tools/lib/python/kdoc/python_version.py | |
| parent | a05d5c40af1bbf32a3fe78a1e25defcf0503f7bf (diff) | |
| download | linux-next-b1c88ae0b554322fa29b4b490ce0b09c2c84ec52.tar.gz linux-next-b1c88ae0b554322fa29b4b490ce0b09c2c84ec52.zip | |
jbd2: say what jbd2_freeze_jh_data()'s assertion is actually checking
The assertion that the buffer about to be copied out is up to date is
correct and stays, but its message - "Possible IO failure" - describes what
a buffer that is not up to date used to mean rather than what is being
checked.
Once this series stops clearing BH_Uptodate on write error, that reading is
wrong twice over. A failed write no longer makes a buffer not up to date,
and a buffer that does carry BH_Write_EIO is fine here: it still holds
valid data and the journal will write it again. What the assertion is
really guarding is that there is something valid to copy at all.
Say that instead.
Suggested-by: Jan Kara <jack@suse.cz>
Acked-by: Weidong Zhu <weizhu@fiu.edu>
Signed-off-by: Chao Shi <coshi036@gmail.com>
Link: https://patch.msgid.link/713ffb9c0cdfe55499b3cdd2c06a59a2c152c46c.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