[moderation] [fs?] KCSAN: data-race in generic_fillattr / inode_update_timestamps (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 3e7aeb78ab01 Merge tag 'net-next-6.8' of git://git.kernel...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16262f7be80000
kernel config: https://syzkaller.appspot.com/x/.config?x=959a33b0b76d1140
dashboard link: https://syzkaller.appspot.com/bug?extid=f0d4f770c86e2c6424c8
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/16aa9be6c3e7/disk-3e7aeb78.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/eff136e3dba0/vmlinux-3e7aeb78.xz
kernel image: https://storage.googleapis.com/syzbot-assets/d9080e2a2d6b/bzImage-3e7aeb78.xz

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

==================================================================
BUG: KCSAN: data-race in generic_fillattr / inode_update_timestamps

write to 0xffff8881281486c0 of 8 bytes by task 3575 on cpu 1:
inode_set_atime_to_ts include/linux/fs.h:1541 [inline]
inode_update_timestamps+0x4d1/0x560 fs/inode.c:1913
generic_update_time fs/inode.c:1935 [inline]
inode_update_time fs/inode.c:1955 [inline]
touch_atime+0x15c/0x2d0 fs/inode.c:2027
file_accessed include/linux/fs.h:2437 [inline]
iterate_dir+0x30f/0x340 fs/readdir.c:113
__do_sys_getdents64 fs/readdir.c:409 [inline]
__se_sys_getdents64+0x88/0x1a0 fs/readdir.c:394
__x64_sys_getdents64+0x43/0x50 fs/readdir.c:394
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0x59/0x120 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x63/0x6b

read to 0xffff8881281486c0 of 8 bytes by task 3267 on cpu 0:
inode_get_atime include/linux/fs.h:1535 [inline]
generic_fillattr+0x16f/0x2f0 fs/stat.c:60
shmem_getattr+0x17b/0x200 mm/shmem.c:1139
vfs_getattr_nosec fs/stat.c:135 [inline]
vfs_getattr fs/stat.c:176 [inline]
vfs_fstat+0x1b5/0x460 fs/stat.c:198
vfs_fstatat+0x85/0x100 fs/stat.c:300
__do_sys_newfstatat fs/stat.c:468 [inline]
__se_sys_newfstatat+0x58/0x260 fs/stat.c:462
__x64_sys_newfstatat+0x55/0x60 fs/stat.c:462
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0x59/0x120 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x63/0x6b

value changed: 0x00000000015c5ce2 -> 0x0000000003beb6e2

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 3267 Comm: udevd Not tainted 6.7.0-syzkaller-04629-g3e7aeb78ab01 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023
==================================================================


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