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

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 0bc21e701a6f MAINTAINERS: Remove Olof from SoC maintainers
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=149da6f8580000
kernel config: https://syzkaller.appspot.com/x/.config?x=c5e179f449c1ff36
dashboard link: https://syzkaller.appspot.com/bug?extid=67ae22672126e35ea950
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/6eb39bae2122/disk-0bc21e70.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/5ff6343fa675/vmlinux-0bc21e70.xz
kernel image: https://storage.googleapis.com/syzbot-assets/47ad0cc0d3c3/bzImage-0bc21e70.xz

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

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

write to 0xffff88810283ac88 of 4 bytes by task 15112 on cpu 0:
inode_set_atime_to_ts include/linux/fs.h:1614 [inline]
usbdev_do_ioctl drivers/usb/core/devio.c:2818 [inline]
usbdev_ioctl+0x6b6/0x3e00 drivers/usb/core/devio.c:2827
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:906 [inline]
__se_sys_ioctl+0xc9/0x140 fs/ioctl.c:892
__x64_sys_ioctl+0x43/0x50 fs/ioctl.c:892
x64_sys_call+0x1690/0x2dc0 arch/x86/include/generated/asm/syscalls_64.h:17
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

write to 0xffff88810283ac88 of 4 bytes by task 15116 on cpu 1:
inode_set_atime_to_ts include/linux/fs.h:1614 [inline]
usbdev_do_ioctl drivers/usb/core/devio.c:2818 [inline]
usbdev_ioctl+0x6b6/0x3e00 drivers/usb/core/devio.c:2827
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:906 [inline]
__se_sys_ioctl+0xc9/0x140 fs/ioctl.c:892
__x64_sys_ioctl+0x43/0x50 fs/ioctl.c:892
x64_sys_call+0x1690/0x2dc0 arch/x86/include/generated/asm/syscalls_64.h:17
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: 0x3634be8f -> 0x392faf0e

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 UID: 0 PID: 15116 Comm: syz.8.15698 Not tainted 6.13.0-rc5-syzkaller-00012-g0bc21e701a6f #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/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.