summaryrefslogtreecommitdiff
path: root/scripts/const_structs.checkpatch
diff options
context:
space:
mode:
authorDaeho Jeong <daehojeong@google.com>2026-08-24 18:53:03 -0700
committerJaegeuk Kim <jaegeuk@kernel.org>2026-08-25 15:32:48 +0000
commit8c963d1738fdca400082ff5f9d99e083de4f4e70 (patch)
tree20f1e507eaea74346250a6993585e38198ee048d /scripts/const_structs.checkpatch
parentce366bfa821ec81dd45bde547ee31e659306cc61 (diff)
downloadlinux-8c963d1738fdca400082ff5f9d99e083de4f4e70.tar.gz
linux-8c963d1738fdca400082ff5f9d99e083de4f4e70.zip
f2fs: accurately adjust free_sections during free_segment_range
In free_segment_range(), MAIN_SECS(sbi) is temporarily reduced by `secs` to restrict block allocation to the safe remaining main area while valid blocks in the truncated range are evacuated by GC. However, FREE_I(sbi)->free_sections tracks the total number of free sections across the whole filesystem. If any sections within the truncated range were already free upon entering free_segment_range(), failing to deduct them from free_sections causes the filesystem to overestimate available free sections in the active, reduced main area. This leads to inconsistent free section accounting during GC data migration and can trigger unexpected allocation failures or assertion errors when space is tight. Fix this by calculating the number of already-free sections in the truncated range, deducting them from free_sections upon entering free_segment_range(), and restoring them on exit. Fixes: b4b10061ef98 ("f2fs: refactor resize_fs to avoid meta updates in progress") Cc: stable@vger.kernel.org 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