mirror of
				git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
				synced 2025-09-04 20:19:47 +08:00 
			
		
		
		
	f2fs: check segment type in __f2fs_replace_block
In some case, the node blocks has wrong blkaddr whose segment type is NODE, e.g., recover inode has missing xattr flag and the blkaddr is in the xattr range. Since fsck.f2fs does not check the recovery nodes, this will cause __f2fs_replace_block change the curseg of node and do the update_sit_entry(sbi, new_blkaddr, 1) with no next_blkoff refresh, as a result, when recovery process write checkpoint and sync nodes, the next_blkoff of curseg is used in the segment bit map, then it will cause f2fs_bug_on. So let's check segment type in __f2fs_replace_block. Signed-off-by: Yunlong Song <yunlong.song@huawei.com> Reviewed-by: Chao Yu <yuchao0@huawei.com> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
This commit is contained in:
		
							parent
							
								
									1eca05aa9d
								
							
						
					
					
						commit
						2c1905042c
					
				| @ -2739,6 +2739,7 @@ void __f2fs_replace_block(struct f2fs_sb_info *sbi, struct f2fs_summary *sum, | |||||||
| 		} | 		} | ||||||
| 	} | 	} | ||||||
| 
 | 
 | ||||||
|  | 	f2fs_bug_on(sbi, !IS_DATASEG(type)); | ||||||
| 	curseg = CURSEG_I(sbi, type); | 	curseg = CURSEG_I(sbi, type); | ||||||
| 
 | 
 | ||||||
| 	mutex_lock(&curseg->curseg_mutex); | 	mutex_lock(&curseg->curseg_mutex); | ||||||
|  | |||||||
		Loading…
	
		Reference in New Issue
	
	Block a user
	 Yunlong Song
						Yunlong Song