diff options
| author | Daeho Jeong <daehojeong@google.com> | 2026-08-20 09:43:40 -0700 |
|---|---|---|
| committer | Jaegeuk Kim <jaegeuk@kernel.org> | 2026-08-21 01:00:38 +0000 |
| commit | 258c95150c26a30db1896eacd3bdef26314f2ca1 (patch) | |
| tree | b62e629284ef27bcd17d0d77d60ff2331102e91f /scripts/const_structs.checkpatch | |
| parent | 0a1703eba23707e3b2edfa2a2329352e7abc0ffa (diff) | |
| download | linux-258c95150c26a30db1896eacd3bdef26314f2ca1.tar.gz linux-258c95150c26a30db1896eacd3bdef26314f2ca1.zip | |
f2fs: avoid setting SBI_NEED_FSCK on transient resize failure
When free_segment_range() fails in f2fs_resize_fs(), no on-disk
superblock or filesystem metadata has been modified yet, and
free_segment_range() safely restores all in-memory counters before
returning.
However, the current error recovery path unconditionally sets the
SBI_NEED_FSCK flag and prints a scary error message on any error,
forcing an unnecessary and time-consuming fsck.f2fs repair on the
subsequent mount/reboot.
Fix this by separating the error recovery path with a dedicated
recover_user_blocks label to bypass setting SBI_NEED_FSCK on
free_segment_range() failures.
Signed-off-by: Daeho Jeong <daehojeong@google.com>
Signed-off-by: Sunmin Jeong <s_min.jeong@samsung.com>
Reviewed-by: Chao Yu <chao@kernel.org>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
Diffstat (limited to 'scripts/const_structs.checkpatch')
0 files changed, 0 insertions, 0 deletions