[moderation] [fs?] KCSAN: data-race in fsnotify_perm / setattr_copy (5)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 0dd3ee311255 Linux 6.7
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=10f85c25e80000
kernel config: https://syzkaller.appspot.com/x/.config?x=1bb2daade28c90a5
dashboard link: https://syzkaller.appspot.com/bug?extid=48662affc221aa5e3a78
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
CC: [bra...@kernel.org 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/b3bdaecbc4f5/disk-0dd3ee31.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/6656b77ef58a/vmlinux-0dd3ee31.xz
kernel image: https://storage.googleapis.com/syzbot-assets/85fa7f08c720/bzImage-0dd3ee31.xz

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

udevd[3154]: inotify_add_watch(7, /dev/loop11, 10) failed: No such file or directory
==================================================================
BUG: KCSAN: data-race in fsnotify_perm / setattr_copy

write to 0xffff88813d36c660 of 2 bytes by task 24 on cpu 1:
setattr_copy+0x29d/0x2b0 fs/attr.c:321
shmem_setattr+0x52e/0x830 mm/shmem.c:1219
notify_change+0x866/0x8e0 fs/attr.c:499
handle_remove drivers/base/devtmpfs.c:337 [inline]
handle drivers/base/devtmpfs.c:386 [inline]
devtmpfs_work_loop+0x828/0x8e0 drivers/base/devtmpfs.c:399
devtmpfsd+0x43/0x50 drivers/base/devtmpfs.c:441
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 0xffff88813d36c660 of 2 bytes by task 3154 on cpu 0:
fsnotify_parent include/linux/fsnotify.h:65 [inline]
fsnotify_file include/linux/fsnotify.h:100 [inline]
fsnotify_perm+0x2a5/0x380 include/linux/fsnotify.h:125
security_file_open+0x53/0x70 security/security.c:2840
do_dentry_open+0x224/0xbd0 fs/open.c:935
vfs_open+0x4a/0x50 fs/open.c:1082
do_open fs/namei.c:3622 [inline]
path_openat+0x1819/0x1d70 fs/namei.c:3779
do_filp_open+0xf6/0x200 fs/namei.c:3809
do_sys_openat2+0xab/0x110 fs/open.c:1437
do_sys_open fs/open.c:1452 [inline]
__do_sys_openat fs/open.c:1468 [inline]
__se_sys_openat fs/open.c:1463 [inline]
__x64_sys_openat+0xf3/0x120 fs/open.c:1463
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0x44/0x110 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x63/0x6b

value changed: 0x6180 -> 0x6000

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 3154 Comm: udevd Not tainted 6.7.0-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023
==================================================================
block device autoloading is deprecated and will be removed.
udevd[3154]: inotify_add_watch(7, /dev/loop11, 10) failed: No such file or directory
udevd[3154]: inotify_add_watch(7, /dev/loop11, 10) failed: No such file or directory
udevd[3154]: inotify_add_watch(7, /dev/loop11, 10) failed: No such file or directory
udevd[3154]: inotify_add_watch(7, /dev/loop11, 10) failed: No such file or directory
udevd[3154]: inotify_add_watch(7, /dev/loop11, 10) failed: No such file or directory
udevd[3154]: inotify_add_watch(7, /dev/loop11, 10) failed: No such file or directory
udevd[3154]: inotify_add_watch(7, /dev/loop11, 10) failed: No such file or directory
udevd[3154]: inotify_add_watch(7, /dev/loop11, 10) failed: No such file or directory
udevd[3154]: inotify_add_watch(7, /dev/loop11, 10) failed: No such file or directory
udevd[3154]: inotify_add_watch(7, /dev/loop11, 10) failed: No such file or directory


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