Chao Yu 20a3d61d46 f2fs: avoid potential deadlock in f2fs_move_file_range ...

Thread A			Thread B
- inode_lock fileA
				- inode_lock fileB
				 - inode_lock fileA
 - inode_lock fileB

We may encounter above potential deadlock during moving file range in
concurrent scenario. This patch fixes the issue by using inode_trylock
instead.

Signed-off-by: Chao Yu <yuchao0@huawei.com>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>

2016-08-19 11:15:08 +09:00

..

acl.c

…

acl.h

…

checkpoint.c

…

data.c

Revert "f2fs: move i_size_write in f2fs_write_end"

2016-08-19 11:15:08 +09:00

debug.c

…

dir.c

Merge branch 'work.const-qstr' of git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs

2016-08-06 09:49:02 -04:00

extent_cache.c

…

f2fs.h

Revert "f2fs: use percpu_rw_semaphore"

2016-08-19 11:15:08 +09:00

file.c

f2fs: avoid potential deadlock in f2fs_move_file_range

2016-08-19 11:15:08 +09:00

gc.c

…

gc.h

…

hash.c

…

inline.c

…

inode.c

…

Kconfig

…

Makefile

…

namei.c

…

node.c

Revert "f2fs: use percpu_rw_semaphore"

2016-08-19 11:15:08 +09:00

node.h

…

recovery.c

…

segment.c

…

segment.h

…

shrinker.c

…

super.c

Revert "f2fs: use percpu_rw_semaphore"

2016-08-19 11:15:08 +09:00

trace.c

…

trace.h

…

xattr.c

…

xattr.h

…