aboutsummaryrefslogtreecommitdiffstats
path: root/lib/mpi/mpi-mpow.c
diff options
context:
space:
mode:
authorJaegeuk Kim <[email protected]>2025-10-07 03:32:30 +0000
committerJaegeuk Kim <[email protected]>2025-10-13 23:55:44 +0000
commit9d5c4f5c7a2c7677e1b3942772122b032c265aae (patch)
tree8868344e65f3478e9f1e004994449b36d367ad5f /lib/mpi/mpi-mpow.c
parentf2fs: don't call iput() from f2fs_drop_inode() (diff)
downloadkernel-9d5c4f5c7a2c7677e1b3942772122b032c265aae.tar.gz
kernel-9d5c4f5c7a2c7677e1b3942772122b032c265aae.zip
f2fs: fix wrong block mapping for multi-devices
Assuming the disk layout as below, disk0: 0 --- 0x00035abfff disk1: 0x00035ac000 --- 0x00037abfff disk2: 0x00037ac000 --- 0x00037ebfff and we want to read data from offset=13568 having len=128 across the block devices, we can illustrate the block addresses like below. 0 .. 0x00037ac000 ------------------- 0x00037ebfff, 0x00037ec000 ------- | ^ ^ ^ | fofs 0 13568 13568+128 | ------------------------------------------------------ | LBA 0x37e8aa9 0x37ebfa9 0x37ec029 --- map 0x3caa9 0x3ffa9 In this example, we should give the relative map of the target block device ranging from 0x3caa9 to 0x3ffa9 where the length should be calculated by 0x37ebfff + 1 - 0x37ebfa9. In the below equation, however, map->m_pblk was supposed to be the original address instead of the one from the target block address. - map->m_len = min(map->m_len, dev->end_blk + 1 - map->m_pblk); Cc: [email protected] Fixes: 71f2c8206202 ("f2fs: multidevice: support direct IO") Reviewed-by: Chao Yu <[email protected]> Signed-off-by: Jaegeuk Kim <[email protected]>
Diffstat (limited to 'lib/mpi/mpi-mpow.c')
0 files changed, 0 insertions, 0 deletions