Re: [PATCH 4.9.y] f2fs: fix a bug caused by NULL extent tree

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Feb 28, 2018 at 03:46:41PM +0200, Nikolay Borisov wrote:
> From: Yunlei He <heyunlei@xxxxxxxxxx>
> 
> Thread A:					Thread B:
> 
> -f2fs_remount
>     -sbi->mount_opt.opt = 0;
> 						<--- -f2fs_iget
> 						         -do_read_inode
> 							     -f2fs_init_extent_tree
> 							         -F2FS_I(inode)->extent_tree is NULL
>         -default_options && parse_options
> 	    -remount return
> 						<---  -f2fs_map_blocks
> 						          -f2fs_lookup_extent_tree
>                                                               -f2fs_bug_on(sbi, !et);
> 
> The same problem with f2fs_new_inode.
> 
> Signed-off-by: Yunlei He <heyunlei@xxxxxxxxxx>
> Signed-off-by: Jaegeuk Kim <jaegeuk@xxxxxxxxxx>
> Signed-off-by: Nikolay Borisov <nborisov@xxxxxxxx>
> ---
> Hi, 
> 
> Here is the 4.9.y backport

Thanks, both now applied.

greg k-h



[Index of Archives]     [Linux Kernel]     [Kernel Development Newbies]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Hiking]     [Linux Kernel]     [Linux SCSI]