[moderation] [usb?] KCSAN: data-race in usbdev_ioctl / usbdev_ioctl (8)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 586b5dfb51b9 Merge tag 'cxl-fixes-6.9-rc4' of git://git.ke..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=112da2dd180000
kernel config: https://syzkaller.appspot.com/x/.config?x=6a1ac6d65bf295c5
dashboard link: https://syzkaller.appspot.com/bug?extid=a32532c62da295dfd72b
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
CC: [gre...@linuxfoundation.org linux-...@vger.kernel.org linu...@vger.kernel.org]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/94a94953c597/disk-586b5dfb.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ce6d536d43ff/vmlinux-586b5dfb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c084c35d1588/bzImage-586b5dfb.xz

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

==================================================================
BUG: KCSAN: data-race in usbdev_ioctl / usbdev_ioctl

write to 0xffff888102bfe130 of 8 bytes by task 15702 on cpu 1:
inode_set_atime_to_ts include/linux/fs.h:1566 [inline]
usbdev_do_ioctl drivers/usb/core/devio.c:2815 [inline]
usbdev_ioctl+0x6c2/0x3e10 drivers/usb/core/devio.c:2824
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:904 [inline]
__se_sys_ioctl+0xd3/0x150 fs/ioctl.c:890
__x64_sys_ioctl+0x43/0x50 fs/ioctl.c:890
x64_sys_call+0x155d/0x2d30 arch/x86/include/generated/asm/syscalls_64.h:17
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+0x77/0x7f

write to 0xffff888102bfe130 of 8 bytes by task 15709 on cpu 0:
inode_set_atime_to_ts include/linux/fs.h:1566 [inline]
usbdev_do_ioctl drivers/usb/core/devio.c:2815 [inline]
usbdev_ioctl+0x6c2/0x3e10 drivers/usb/core/devio.c:2824
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:904 [inline]
__se_sys_ioctl+0xd3/0x150 fs/ioctl.c:890
__x64_sys_ioctl+0x43/0x50 fs/ioctl.c:890
x64_sys_call+0x155d/0x2d30 arch/x86/include/generated/asm/syscalls_64.h:17
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+0x77/0x7f

value changed: 0x0000000006b07895 -> 0x000000000a43ff96

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 15709 Comm: syz-executor.0 Not tainted 6.9.0-rc3-syzkaller-00208-g586b5dfb51b9 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/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