aboutsummaryrefslogtreecommitdiff
path: root/lib/mpi/mpih-mul.c
diff options
context:
space:
mode:
authorChao Yu <[email protected]>2018-07-05 19:37:00 +0800
committerJaegeuk Kim <[email protected]>2018-08-01 11:52:36 -0700
commit82902c06bd17dbf6e8184299842ca5c68880970f (patch)
tree04e2898228e4515fb710b9ed23eecffbd18349cc /lib/mpi/mpih-mul.c
parentc9b60788fc760d136211853f10ce73dc152d1f4a (diff)
f2fs: fix to detect looped node chain correctly
Below dmesg was printed when testing generic/388 of fstest: F2FS-fs (zram1): find_fsync_dnodes: detect looped node chain, blkaddr:526615, next:526616 F2FS-fs (zram1): Cannot recover all fsync data errno=-22 F2FS-fs (zram1): Mounted with checkpoint version = 22300d0e F2FS-fs (zram1): find_fsync_dnodes: detect looped node chain, blkaddr:526615, next:526616 F2FS-fs (zram1): Cannot recover all fsync data errno=-22 The reason is that we initialize free_blocks with free blocks of filesystem, so if filesystem is full, free_blocks can be zero, below condition will be true, so that, it will fail recovery. if (++loop_cnt >= free_blocks || blkaddr == next_blkaddr_of_node(page)) To fix this issue, initialize free_blocks with correct value which includes over-privision blocks. Signed-off-by: Chao Yu <[email protected]> Signed-off-by: Jaegeuk Kim <[email protected]>
Diffstat (limited to 'lib/mpi/mpih-mul.c')
0 files changed, 0 insertions, 0 deletions