[moderation] [fs?] KCSAN: data-race in iput / move_expired_inodes (10)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: e6f39a90de92 Merge tag 'efi-fixes-for-v6.8-1' of git://git..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=13298c42180000
kernel config: https://syzkaller.appspot.com/x/.config?x=3cd0dc1b46a5bc5c
dashboard link: https://syzkaller.appspot.com/bug?extid=72946170a52e6207a749
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
CC: [bra...@kernel.org ja...@suse.cz linux-...@vger.kernel.org linux-...@vger.kernel.org vi...@zeniv.linux.org.uk]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/b03303eeb2c2/disk-e6f39a90.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/72c5ffb55217/vmlinux-e6f39a90.xz
kernel image: https://storage.googleapis.com/syzbot-assets/281fcd2e60f4/bzImage-e6f39a90.xz

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

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

read-write to 0xffff8881064eef60 of 8 bytes by task 11 on cpu 0:
move_expired_inodes+0x17b/0x410 fs/fs-writeback.c:1405
queue_io+0xe1/0x2e0 fs/fs-writeback.c:1457
wb_writeback+0x22a/0x6e0 fs/fs-writeback.c:2090
wb_do_writeback fs/fs-writeback.c:2239 [inline]
wb_workfn+0x1a8/0x8d0 fs/fs-writeback.c:2279
process_one_work kernel/workqueue.c:2633 [inline]
process_scheduled_works+0x5b8/0xa40 kernel/workqueue.c:2706
worker_thread+0x525/0x730 kernel/workqueue.c:2787
kthread+0x1d7/0x210 kernel/kthread.c:388
ret_from_fork+0x48/0x60 arch/x86/kernel/process.c:147
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:242

read to 0xffff8881064eef60 of 8 bytes by task 3090 on cpu 1:
iput+0x32/0x5c0 fs/inode.c:1755
dentry_unlink_inode+0x22a/0x240 fs/dcache.c:400
d_delete+0x76/0xf0 fs/dcache.c:2389
d_delete_notify include/linux/fsnotify.h:299 [inline]
vfs_rmdir+0x1a0/0x2f0 fs/namei.c:4218
do_rmdir+0x194/0x320 fs/namei.c:4264
__do_sys_unlinkat fs/namei.c:4440 [inline]
__se_sys_unlinkat fs/namei.c:4434 [inline]
__x64_sys_unlinkat+0xa4/0xb0 fs/namei.c:4434
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xcd/0x1d0 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x63/0x6b

value changed: 0x0000000000000001 -> 0x0000000000020080

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 PID: 3090 Comm: syz-executor.4 Not tainted 6.8.0-rc3-syzkaller-00215-ge6f39a90de92 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024
==================================================================


---
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.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

[syzbot]

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