[moderation] [usb?] KCSAN: data-race in __usb_hcd_giveback_urb / mon_reader_del

10 views
Skip to first unread message

syzbot

unread,
Nov 20, 2024, 6:49:22 PM11/20/24
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 8f7c8b88bda4 Merge tag 'sched_ext-for-6.13' of git://git.k..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=17ddbae8580000
kernel config: https://syzkaller.appspot.com/x/.config?x=a4239a0e02e161ec
dashboard link: https://syzkaller.appspot.com/bug?extid=18079e8398e66af13287
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/aa6454497bbf/disk-8f7c8b88.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/dd054d382c7b/vmlinux-8f7c8b88.xz
kernel image: https://storage.googleapis.com/syzbot-assets/864b540a4402/bzImage-8f7c8b88.xz

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

==================================================================
BUG: KCSAN: data-race in __usb_hcd_giveback_urb / mon_reader_del

write to 0xffff88810216b088 of 4 bytes by task 20067 on cpu 0:
mon_stop drivers/usb/mon/mon_main.c:166 [inline]
mon_reader_del+0x1bd/0x260 drivers/usb/mon/mon_main.c:73
mon_bin_release+0x66/0x120 drivers/usb/mon/mon_bin.c:793
__fput+0x17a/0x6d0 fs/file_table.c:450
____fput+0x1c/0x30 fs/file_table.c:478
task_work_run+0x13a/0x1a0 kernel/task_work.c:239
exit_task_work include/linux/task_work.h:43 [inline]
do_exit+0x5dd/0x17f0 kernel/exit.c:938
do_group_exit+0x102/0x150 kernel/exit.c:1087
get_signal+0xeb9/0x1000 kernel/signal.c:3016
arch_do_signal_or_restart+0x95/0x4b0 arch/x86/kernel/signal.c:337
exit_to_user_mode_loop kernel/entry/common.c:111 [inline]
exit_to_user_mode_prepare include/linux/entry-common.h:329 [inline]
__syscall_exit_to_user_mode_work kernel/entry/common.c:207 [inline]
syscall_exit_to_user_mode+0x62/0x120 kernel/entry/common.c:218
do_syscall_64+0xd6/0x1c0 arch/x86/entry/common.c:89
entry_SYSCALL_64_after_hwframe+0x77/0x7f

read to 0xffff88810216b088 of 4 bytes by interrupt on cpu 1:
usbmon_urb_complete include/linux/usb/hcd.h:737 [inline]
__usb_hcd_giveback_urb+0x13d/0x370 drivers/usb/core/hcd.c:1635
usb_giveback_urb_bh+0x170/0x280 drivers/usb/core/hcd.c:1684
process_one_work kernel/workqueue.c:3229 [inline]
process_scheduled_works+0x483/0x9a0 kernel/workqueue.c:3310
bh_worker+0x21f/0x370 kernel/workqueue.c:3570
workqueue_softirq_action+0xaa/0xc0 kernel/workqueue.c:3597
tasklet_action+0xb/0x30 kernel/softirq.c:829
handle_softirqs+0xbf/0x280 kernel/softirq.c:554
run_ksoftirqd+0x1c/0x30 kernel/softirq.c:943
smpboot_thread_fn+0x31c/0x4c0 kernel/smpboot.c:164
kthread+0x1d1/0x210 kernel/kthread.c:389
ret_from_fork+0x4b/0x60 arch/x86/kernel/process.c:147
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244

value changed: 0x00000001 -> 0x00000000

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 UID: 0 PID: 23 Comm: ksoftirqd/1 Not tainted 6.12.0-syzkaller-01892-g8f7c8b88bda4 #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

unread,
Apr 22, 2025, 2:04:15 PM4/22/25
to syzkaller-upst...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages