Revert "f2fs: clean up w/ sbi->log_sectors_per_block"
Subsystems (2)
Jaegeuk Kim
maintainerPATCH 1/1 Revert "f2fs: clean up w/ sbi->log_sectors_per_block"
This reverts commit bfd476623999118d9c509cb0fa9380f2912bc225.
Shinichiro Kawasaki reported:
When I ran workloads on f2fs using v6.5-rcX with fixes [1][2] and a zoned block devices with 4kb logical block size, I observe mount failure as follows. When I revert this commit, the failure goes away.
[ 167.781975][ T1555] F2FS-fs (dm-0): IO Block Size: 4 KB [ 167.890728][ T1555] F2FS-fs (dm-0): Found nat_bits in checkpoint [ 171.482588][ T1555] F2FS-fs (dm-0): Zone without valid block has non-zero write pointer. Reset the write pointer: wp[0x1300,0x8] [ 171.496000][ T1555] F2FS-fs (dm-0): (0) : Unaligned zone reset attempted (block 280000 + 80000) [ 171.505037][ T1555] F2FS-fs (dm-0): Discard zone failed: (errno=-5)
The patch replaced "sbi->log_blocksize - SECTOR_SHIFT" with "sbi->log_sectors_per_block". However, I think these two are not equal when the device has 4k logical block size. The former uses Linux kernel sector size 512 byte. The latter use 512b sector size or 4kb sector size depending on the device. mkfs.f2fs obtains logical block size via BLKSSZGET ioctl from the device and reflects it to the value sbi->log_sector_size_per_block. This causes unexpected write pointer calculations in check_zone_write_pointer(). This resulted in unexpected zone reset and the mount failure.
[1] https://lkml.kernel.org/linux-f2fs-devel/[email protected]/
[2] https://lore.kernel.org/linux-f2fs-devel/[email protected]/
--- fs/f2fs/segment.c | 23 ++++++++++++----------- 1 file changed, 12 insertions(+), 11 deletions(-)
fs/f2fs/segment.c +12 -11
@@ -4846,17 +4846,17 @@ static int check_zone_write_pointer(struct f2fs_sb_info *sbi, {unsigned int wp_segno, wp_blkoff, zone_secno, zone_segno, segno;block_t zone_block, wp_block, last_valid_block; +unsigned int log_sectors_per_block = sbi->log_blocksize -SECTOR_SHIFT ;int i, s, b, ret;struct seg_entry *se;if (zone->type !=BLK_ZONE_TYPE_SEQWRITE_REQ )return 0 ; - wp_block = fdev->start_blk + (zone->wp >> sbi->log_sectors_per_block); + wp_block = fdev->start_blk + (zone->wp >> log_sectors_per_block); wp_segno =GET_SEGNO (sbi, wp_block); wp_blkoff = wp_block -START_BLOCK (sbi, wp_segno); - zone_block = fdev->start_blk + (zone->start >> - sbi->log_sectors_per_block); + zone_block = fdev->start_blk + (zone->start >> log_sectors_per_block); zone_segno =GET_SEGNO (sbi, zone_block); zone_secno =GET_SEC_FROM_SEG (sbi, zone_segno);
@@ -4906,7 +4906,7 @@ static int check_zone_write_pointer(struct f2fs_sb_info *sbi,"pointer. Reset the write pointer: wp[0x%x,0x%x]" , wp_segno, wp_blkoff); ret =__f2fs_issue_discard_zone (sbi, fdev->bdev, zone_block, - zone->len >> sbi->log_sectors_per_block); + zone->len >> log_sectors_per_block);if (ret)f2fs_err (sbi,"Discard zone failed: %s (errno=%d)" , fdev->path, ret);
@@ -4967,6 +4967,7 @@ static int fix_curseg_write_pointer(struct f2fs_sb_info *sbi, int type)struct blk_zone zone;unsigned int cs_section, wp_segno, wp_blkoff, wp_sector_off;block_t cs_zone_block, wp_block; +unsigned int log_sectors_per_block = sbi->log_blocksize -SECTOR_SHIFT ;sector_t zone_sector;int err;
@@ -4978,8 +4979,8 @@ static int fix_curseg_write_pointer(struct f2fs_sb_info *sbi, int type)return 0 ;/* report zone for the sector the curseg points to */ - zone_sector = (sector_t)(cs_zone_block - zbd->start_blk) << - sbi->log_sectors_per_block; + zone_sector = (sector_t)(cs_zone_block - zbd->start_blk) + << log_sectors_per_block; err =blkdev_report_zones (zbd->bdev, zone_sector,1 , report_one_zone_cb, &zone);if (err !=1 ) {
@@ -4991,10 +4992,10 @@ static int fix_curseg_write_pointer(struct f2fs_sb_info *sbi, int type)if (zone.type !=BLK_ZONE_TYPE_SEQWRITE_REQ )return 0 ; - wp_block = zbd->start_blk + (zone.wp >> sbi->log_sectors_per_block); + wp_block = zbd->start_blk + (zone.wp >> log_sectors_per_block); wp_segno =GET_SEGNO (sbi, wp_block); wp_blkoff = wp_block -START_BLOCK (sbi, wp_segno); - wp_sector_off = zone.wp &GENMASK (sbi->log_sectors_per_block -1 ,0 ); + wp_sector_off = zone.wp &GENMASK (log_sectors_per_block -1 ,0 );if (cs->segno == wp_segno && cs->next_blkoff == wp_blkoff && wp_sector_off ==0 )
@@ -5021,8 +5022,8 @@ static int fix_curseg_write_pointer(struct f2fs_sb_info *sbi, int type)if (!zbd)return 0 ; - zone_sector = (sector_t)(cs_zone_block - zbd->start_blk) << - sbi->log_sectors_per_block; + zone_sector = (sector_t)(cs_zone_block - zbd->start_blk) + << log_sectors_per_block; err =blkdev_report_zones (zbd->bdev, zone_sector,1 , report_one_zone_cb, &zone);if (err !=1 ) {
@@ -5040,7 +5041,7 @@ static int fix_curseg_write_pointer(struct f2fs_sb_info *sbi, int type)"Reset the zone: curseg[0x%x,0x%x]" , type, cs->segno, cs->next_blkoff); err =__f2fs_issue_discard_zone (sbi, zbd->bdev, cs_zone_block, - zone.len >> sbi->log_sectors_per_block); + zone.len >> log_sectors_per_block);if (err) {f2fs_err (sbi,"Discard zone failed: %s (errno=%d)" , zbd->path, err);
Signature · 1 line
2.41.0.640.ga95def55d0-goog
This patch was applied to jaegeuk/f2fs.git (dev) by Jaegeuk Kim <[email protected]>:
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <[email protected]>:
Quoted 9 lines · On Mon, 7 Aug 2023 12:52:19 -0700 you wrote:
This reverts commit
bfd476623999118d9c509cb0fa9380f2912bc225.Shinichiro Kawasaki reported:
When I ran workloads on f2fs using v6.5-rcX with fixes [1][2] and a zoned block devices with 4kb logical block size, I observe mount failure as follows. When I revert this commit, the failure goes away.
[...]
Here is the summary with links:
- [f2fs-dev] Revert "f2fs: clean up w/ sbi->log_sectors_per_block"
https://git.kernel.org/jaegeuk/f2fs/c/f7a177b8690e
You are awesome, thank you!
Signature · 2 lines
Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html
Quoted 23 lines · Jaegeuk Kim
This reverts commit
bfd476623999118d9c509cb0fa9380f2912bc225.Shinichiro Kawasaki reported:
When I ran workloads on f2fs using v6.5-rcX with fixes [1][2] and a zoned block devices with 4kb logical block size, I observe mount failure as follows. When I revert this commit, the failure goes away.
[ 167.781975][ T1555] F2FS-fs (dm-0): IO Block Size: 4 KB [ 167.890728][ T1555] F2FS-fs (dm-0): Found nat_bits in checkpoint [ 171.482588][ T1555] F2FS-fs (dm-0): Zone without valid block has non-zero write pointer. Reset the write pointer: wp[0x1300,0x8] [ 171.496000][ T1555] F2FS-fs (dm-0): (0) : Unaligned zone reset attempted (block 280000 + 80000) [ 171.505037][ T1555] F2FS-fs (dm-0): Discard zone failed: (errno=-5)The patch replaced "
sbi->log_blocksize-SECTOR_SHIFT" with "sbi->log_sectors_per_block". However, I think these two are not equal when the device has 4k logical block size. The former uses Linux kernel sector size 512 byte. The latter use 512b sector size or 4kb sector size depending on the device. mkfs.f2fs obtains logical block size via BLKSSZGET ioctl from the device and reflects it to the valuesbi->log_sector_size_per_block. This causes unexpected write pointer calculations incheck_zone_write_pointer(). This resulted in unexpected zone reset and the mount failure.
Quoted 7 lines
[1] https://lkml.kernel.org/linux-f2fs-devel/[email protected]/
[2] https://lore.kernel.org/linux-f2fs-devel/[email protected]/Reported-by Shinichiro Kawasaki <[email protected]>Fixes bfd476623999 ("f2fs: clean up w/ sbi->log_sectors_per_block")Signed-off-by Jaegeuk Kim <[email protected]>
Thanks,