There are some cases of f2fs_is_valid_blkaddr not handled as
ERROR_INVALID_BLKADDR,so unify the error handling about all of
f2fs_is_valid_blkaddr.
Do f2fs_handle_error in __f2fs_is_valid_blkaddr for cleanup.
Signed-off-by: Zhiguo Niu
Signed-off-by: Chao Yu
---
v8: do reboot/monkey stability
On 2020/6/20 6:47, Jaegeuk Kim wrote:
diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c
index 3268f8dd59bb..1862073b96d2 100644
--- a/fs/f2fs/file.c
+++ b/fs/f2fs/file.c
@@ -1250,6 +1250,7 @@ static int __clone_blkaddrs(struct inode *src_inode,
struct inode *dst_inode,
Commit 2e2c6e9b72ce ("f2fs: remove power-of-two limitation of zoned
device") missed to remove pow2 check condition in init_blkz_info(),
fix it.
Fixes: 2e2c6e9b72ce ("f2fs: remove power-of-two limitation of zoned device")
Signed-off-by: Feng Song
Signed-off-by: Yongpeng Yang
Signed-off-by: Chao
Below race case can cause data corruption:
Thread AGC thread
- gc_data_segment
- ra_data_block
- locked meta_inode page
-
On 2024/3/8 2:37, Jaegeuk Kim wrote:
On 03/07, Chao Yu wrote:
Below race case can cause data corruption:
Thread AGC thread
- f2fs_inplace_write_data
- gc_data_segment
-
On 03/07, Chao Yu wrote:
> Below race case can cause data corruption:
>
> Thread A GC thread
> - f2fs_inplace_write_data
> - gc_data_segment
>- ra_data_block
>
Below race case can cause data corruption:
Thread AGC thread
- f2fs_inplace_write_data
- gc_data_segment
- ra_data_block
- locked meta_inode
