diff options
author | Zhihao Cheng <chengzhihao1@huawei.com> | 2021-06-18 11:11:03 +0300 |
---|---|---|
committer | Richard Weinberger <richard@nod.at> | 2021-06-22 10:21:39 +0300 |
commit | a801fcfeef96702fa3f9b22ad56c5eb1989d9221 (patch) | |
tree | 9a8b614e0e2c55ca96358caafd0135d508db3bba /drivers/mtd | |
parent | 07c32de44e67882e66f4f81f78d2a16bb72337e4 (diff) | |
download | linux-a801fcfeef96702fa3f9b22ad56c5eb1989d9221.tar.xz |
ubifs: Set/Clear I_LINKABLE under i_lock for whiteout inode
xfstests-generic/476 reports a warning message as below:
WARNING: CPU: 2 PID: 30347 at fs/inode.c:361 inc_nlink+0x52/0x70
Call Trace:
do_rename+0x502/0xd40 [ubifs]
ubifs_rename+0x8b/0x180 [ubifs]
vfs_rename+0x476/0x1080
do_renameat2+0x67c/0x7b0
__x64_sys_renameat2+0x6e/0x90
do_syscall_64+0x66/0xe0
entry_SYSCALL_64_after_hwframe+0x44/0xae
Following race case can cause this:
rename_whiteout(Thread 1) wb_workfn(Thread 2)
ubifs_rename
do_rename
__writeback_single_inode
spin_lock(&inode->i_lock)
whiteout->i_state |= I_LINKABLE
inode->i_state &= ~dirty;
---- How race happens on i_state:
(tmp = whiteout->i_state | I_LINKABLE)
(tmp = inode->i_state & ~dirty)
(whiteout->i_state = tmp)
(inode->i_state = tmp)
----
spin_unlock(&inode->i_lock)
inc_nlink(whiteout)
WARN_ON(!(inode->i_state & I_LINKABLE)) !!!
Fix to add i_lock to avoid i_state update race condition.
Fixes: 9e0a1fff8db56ea ("ubifs: Implement RENAME_WHITEOUT")
Signed-off-by: Zhihao Cheng <chengzhihao1@huawei.com>
Signed-off-by: Richard Weinberger <richard@nod.at>
Diffstat (limited to 'drivers/mtd')
0 files changed, 0 insertions, 0 deletions