From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out5-smtp.messagingengine.com ([66.111.4.29]:43961 "EHLO out5-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752328AbeB1M2e (ORCPT ); Wed, 28 Feb 2018 07:28:34 -0500 Date: Wed, 28 Feb 2018 13:28:33 +0100 From: Greg KH To: Nikolay Borisov Cc: stable@vger.kernel.org, chao2.yu@samsung.com, jaegeuk@kernel.org, cm224.lee@samsung.com, Yunlei He Subject: Re: [PATCH 4.4] f2fs: fix a bug caused by NULL extent tree Message-ID: <20180228122833.GB28076@kroah.com> References: <1519730585-909-1-git-send-email-nborisov@suse.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1519730585-909-1-git-send-email-nborisov@suse.com> Sender: stable-owner@vger.kernel.org List-ID: On Tue, Feb 27, 2018 at 01:23:05PM +0200, Nikolay Borisov wrote: > From: Yunlei He > > 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 > Signed-off-by: Jaegeuk Kim > Signed-off-by: Nikolay Borisov > --- > > 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