Re: [PATCH 4.4] f2fs: fix a bug caused by NULL extent tree

[Greg KH <greg@kroah.com>]

On Tue, Feb 27, 2018 at 01:23:05PM +0200, Nikolay Borisov wrote:
> From: Yunlei He <heyunlei@huawei.com>
> 
> 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@huawei.com>
> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
> Signed-off-by: Nikolay Borisov <nborisov@suse.com>
> ---
> 
> Hello Greg, 
> 
> I would like to have upstream commit dad48e73127b ("f2fs: fix a bug
> caused by NULL extent tree") included in the 4.4 stable kernel. This is the 
> backport of it. 

It also needs to go to 4.9.y, right?

Can you provide a backport for that?

thanks,

greg k-h