summaryrefslogtreecommitdiff
path: root/fs/jffs2/nodelist.c
diff options
context:
space:
mode:
authorChao Yu <chao2.yu@samsung.com>2014-08-30 05:52:34 +0400
committerJaegeuk Kim <jaegeuk@kernel.org>2014-09-02 11:22:24 +0400
commitb73e52824c8920a5ff754e3c8ff68466a7dd61f9 (patch)
tree9f3d869cb4e7cb96b6992da333e9daec987ca86b /fs/jffs2/nodelist.c
parent3304b56401c4509ffaa74705b49edc9e13cee195 (diff)
downloadlinux-b73e52824c8920a5ff754e3c8ff68466a7dd61f9.tar.xz
f2fs: reposition unlock_new_inode to prevent accessing invalid inode
As the race condition on the inode cache, following scenario can appear: [Thread a] [Thread b] ->f2fs_mkdir ->f2fs_add_link ->__f2fs_add_link ->init_inode_metadata failed here ->gc_thread_func ->f2fs_gc ->do_garbage_collect ->gc_data_segment ->f2fs_iget ->iget_locked ->wait_on_inode ->unlock_new_inode ->move_data_page ->make_bad_inode ->iput When we fail in create/symlink/mkdir/mknod/tmpfile, the new allocated inode should be set as bad to avoid being accessed by other thread. But in above scenario, it allows f2fs to access the invalid inode before this inode was set as bad. This patch fix the potential problem, and this issue was found by code review. change log from v1: o Add condition judgment in gc_data_segment() suggested by Changman Lee. o use iget_failed to simplify code. Signed-off-by: Chao Yu <chao2.yu@samsung.com> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
Diffstat (limited to 'fs/jffs2/nodelist.c')
0 files changed, 0 insertions, 0 deletions