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

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 6613476e225e Linux 6.8-rc1
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=127dd9e3e80000
kernel config: https://syzkaller.appspot.com/x/.config?x=5197e0a6c8448ad3
dashboard link: https://syzkaller.appspot.com/bug?extid=4347ba56278e2fa39976
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/61d720b37887/disk-6613476e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/d122725c1ed5/vmlinux-6613476e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/85b4e6b79b60/bzImage-6613476e.xz

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

vhci_hcd: default hub control req: 0000 v0000 i0000 l0
vhci_hcd: default hub control req: 0000 v0000 i0000 l0
vhci_hcd: default hub control req: 0000 v0000 i0000 l0
vhci_hcd: default hub control req: 0000 v0000 i0000 l0
vhci_hcd: default hub control req: 0000 v0000 i0000 l0
vhci_hcd: default hub control req: 0000 v0000 i0000 l0
vhci_hcd: default hub control req: 0000 v0000 i0000 l0
vhci_hcd: default hub control req: 0000 v0000 i0000 l0
vhci_hcd: default hub control req: 0000 v0000 i0000 l0
==================================================================
BUG: KCSAN: data-race in usbdev_ioctl / usbdev_ioctl

write to 0xffff888102a08f90 of 8 bytes by task 16592 on cpu 0:
inode_set_atime_to_ts include/linux/fs.h:1541 [inline]
usbdev_do_ioctl drivers/usb/core/devio.c:2815 [inline]
usbdev_ioctl+0x6c0/0x3e00 drivers/usb/core/devio.c:2824
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:871 [inline]
__se_sys_ioctl+0xcf/0x140 fs/ioctl.c:857
__x64_sys_ioctl+0x43/0x50 fs/ioctl.c:857
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

write to 0xffff888102a08f90 of 8 bytes by task 16594 on cpu 1:
inode_set_atime_to_ts include/linux/fs.h:1541 [inline]
usbdev_do_ioctl drivers/usb/core/devio.c:2815 [inline]
usbdev_ioctl+0x6c0/0x3e00 drivers/usb/core/devio.c:2824
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:871 [inline]
__se_sys_ioctl+0xcf/0x140 fs/ioctl.c:857
__x64_sys_ioctl+0x43/0x50 fs/ioctl.c:857
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: 0x000000001e9e0923 -> 0x000000001f369fa3

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 PID: 16594 Comm: syz-executor.5 Tainted: G W 6.8.0-rc1-syzkaller #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.