KCSAN: data-race in evict / move_expired_inodes

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 3d5e28bf Merge branch 'stable/for-linus-5.10-rc2' of git:/..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12e291e6500000
kernel config: https://syzkaller.appspot.com/x/.config?x=671e27f23e60a67b
dashboard link: https://syzkaller.appspot.com/bug?extid=ec08fd7847dd12f73b33
compiler: clang version 12.0.0 (https://github.com/llvm/llvm-project.git 913f6005669cfb590c99865a90bc51ed0983d09d)
CC: [linux-...@vger.kernel.org linux-...@vger.kernel.org vi...@zeniv.linux.org.uk]

Unfortunately, I don't have any reproducer for this issue yet.

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+ec08fd...@syzkaller.appspotmail.com

==================================================================
BUG: KCSAN: data-race in evict / move_expired_inodes

read-write to 0xffff88810d71c6f8 of 8 bytes by task 8 on cpu 1:
move_expired_inodes+0x1bf/0x490 fs/fs-writeback.c:1257
queue_io+0xe1/0x2b0 fs/fs-writeback.c:1304
wb_writeback+0x255/0x660 fs/fs-writeback.c:1892
wb_do_writeback+0x101/0x5d0 fs/fs-writeback.c:2039
wb_workfn+0xb8/0x410 fs/fs-writeback.c:2080
process_one_work+0x3e1/0x950 kernel/workqueue.c:2272
worker_thread+0x635/0xb90 kernel/workqueue.c:2418
kthread+0x1fa/0x220 kernel/kthread.c:292
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:296

read to 0xffff88810d71c6f8 of 8 bytes by task 8456 on cpu 0:
evict+0x42/0x470 fs/inode.c:561
iput_final fs/inode.c:1654 [inline]
iput+0x421/0x510 fs/inode.c:1680
do_unlinkat+0x2c9/0x4d0 fs/namei.c:3903
__do_sys_unlink fs/namei.c:3943 [inline]
__se_sys_unlink fs/namei.c:3941 [inline]
__x64_sys_unlink+0x2c/0x30 fs/namei.c:3941
do_syscall_64+0x39/0x80 arch/x86/entry/common.c:46
entry_SYSCALL_64_after_hwframe+0x44/0xa9

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 8456 Comm: syz-executor.2 Not tainted 5.10.0-rc3-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
==================================================================


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.