f2fs: fix a bug caused by NULL extent tree
authorYunlei He <heyunlei@huawei.com>
Fri, 19 May 2017 07:06:12 +0000 (15:06 +0800)
committerJaegeuk Kim <jaegeuk@kernel.org>
Wed, 24 May 2017 04:07:18 +0000 (21:07 -0700)
commitdad48e73127ba10279ea33e6dbc8d3905c4d31c0
tree7594af62186ba7a56da3f25e2e442137a0183ce5
parent1d7be2708277edfef95171d52fb65ee26eaa076b
f2fs: fix a bug caused by NULL extent tree

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>
fs/f2fs/extent_cache.c