[moderation] [mm?] upstream test error: KCSAN: data-race in fill_mg_cmtime / shmem_symlink

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 158f238aa69d Merge tag 'for-linus-6.13-rc1-tag' of git://g..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12dffb5f980000
kernel config: https://syzkaller.appspot.com/x/.config?x=44f4147e19698730
dashboard link: https://syzkaller.appspot.com/bug?extid=33f57ae4fb6a2c31e9b7
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
CC: [ak...@linux-foundation.org hu...@google.com linux-...@vger.kernel.org linu...@kvack.org]

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/412e9e31a9dd/disk-158f238a.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/a1bb03fe3319/vmlinux-158f238a.xz
kernel image: https://storage.googleapis.com/syzbot-assets/0ae5825855c8/bzImage-158f238a.xz

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

==================================================================
BUG: KCSAN: data-race in fill_mg_cmtime / shmem_symlink

write to 0xffff888104124c94 of 4 bytes by task 3305 on cpu 0:
inode_set_mtime_to_ts include/linux/fs.h:1648 [inline]
shmem_symlink+0x349/0x3a0 mm/shmem.c:3912
vfs_symlink+0xca/0x1d0 fs/namei.c:4669
do_symlinkat+0xdf/0x350 fs/namei.c:4695
__do_sys_symlink fs/namei.c:4716 [inline]
__se_sys_symlink fs/namei.c:4714 [inline]
__x64_sys_symlink+0x50/0x60 fs/namei.c:4714
x64_sys_call+0x28b0/0x2dc0 arch/x86/include/generated/asm/syscalls_64.h:89
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xc9/0x1c0 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f

read to 0xffff888104124c94 of 4 bytes by task 3944 on cpu 1:
inode_get_mtime_nsec include/linux/fs.h:1634 [inline]
inode_get_mtime include/linux/fs.h:1640 [inline]
fill_mg_cmtime+0x58/0x280 fs/stat.c:55
generic_fillattr+0x241/0x330 fs/stat.c:99
shmem_getattr+0x17b/0x200 mm/shmem.c:1174
vfs_getattr_nosec fs/stat.c:208 [inline]
vfs_getattr fs/stat.c:246 [inline]
vfs_statx_path+0x171/0x2d0 fs/stat.c:283
vfs_statx+0xe1/0x170 fs/stat.c:347
vfs_fstatat fs/stat.c:366 [inline]
__do_sys_newfstatat fs/stat.c:530 [inline]
__se_sys_newfstatat+0xdc/0x300 fs/stat.c:524
__x64_sys_newfstatat+0x55/0x70 fs/stat.c:524
x64_sys_call+0x236d/0x2dc0 arch/x86/include/generated/asm/syscalls_64.h:263
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xc9/0x1c0 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f

value changed: 0x1617255e -> 0x162dbc4c

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 UID: 0 PID: 3944 Comm: udevd Not tainted 6.12.0-syzkaller-00971-g158f238aa69d #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/30/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.