From: Greg KH <greg@kroah.com>
To: Nikolay Borisov <nborisov@suse.com>
Cc: stable@vger.kernel.org, jaegeuk@kernel.org, heyunlei@huawei.com
Subject: Re: [PATCH 4.9.y] f2fs: fix a bug caused by NULL extent tree
Date: Wed, 28 Feb 2018 15:44:51 +0100 [thread overview]
Message-ID: <20180228144451.GA17173@kroah.com> (raw)
In-Reply-To: <1519825601-13329-1-git-send-email-nborisov@suse.com>
On Wed, Feb 28, 2018 at 03:46:41PM +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>
> ---
> Hi,
>
> Here is the 4.9.y backport
Thanks, both now applied.
greg k-h
prev parent reply other threads:[~2018-02-28 14:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-27 11:23 [PATCH 4.4] f2fs: fix a bug caused by NULL extent tree Nikolay Borisov
2018-02-28 12:28 ` Greg KH
2018-02-28 13:46 ` [PATCH 4.9.y] " Nikolay Borisov
2018-02-28 14:44 ` Greg KH [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180228144451.GA17173@kroah.com \
--to=greg@kroah.com \
--cc=heyunlei@huawei.com \
--cc=jaegeuk@kernel.org \
--cc=nborisov@suse.com \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox