From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-oa1-f77.google.com (mail-oa1-f77.google.com [209.85.160.77]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 08AD74A21 for ; Sun, 23 Aug 2026 02:47:34 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.160.77 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1787453256; cv=none; b=d0giSponkpEQaeI0O9/c4OldKMlN3v0A4jDWFaX+vsTHzByxvkUVn1YqinL3L+x8UuYuimm28n6VSs3k23jF6sP/0+P6b72TCNcO2+7XCOwn5zphm7fzOt/HRi9xhWvB2vLIOCOllx9HwbgrmE9LBTsMd4pEA39YNgQOgCeytRc= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1787453256; c=relaxed/simple; bh=WGhv0o9hRX/dVQEj1Kr1jmywgAwEdfO3T2sJK93Jq4A=; h=MIME-Version:Date:Message-ID:Subject:From:To:Content-Type; b=TjcjisZJILALa29hrSDx9TeWi71+kIcPWYKUABItvKAFslGEWW+8pjdsI1RMtyd6mOfh5HjYOlOFE6Qv93cZogj1FyFKIGssnbWha4gu+DHeevO3Lew5ux/VZf/U65nY8GVXjEN+LIbGvys6BOuYsYicP8n+JQ3HSNAtCqJK2ao= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com; arc=none smtp.client-ip=209.85.160.77 Authentication-Results: smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com Received: by mail-oa1-f77.google.com with SMTP id 586e51a60fabf-44899f99756so5106460fac.2 for ; Sat, 22 Aug 2026 19:47:34 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1787453254; x=1788058054; h=content-type:to:from:subject:message-id:date:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to :content-type; bh=kDf/7JC6FeZQTxP2pfIuHzhUMWglrAAnuMzLa1od0KY=; b=r2HYeCO/e1Fc/MiBckpP3XFHWJQ78N/Li2ZA2tToKXJvCGyWr5qjmBYINvhew3iKdh GU9fXjviP2gBBEIT6gnb9Iic6/77ZwbvakCv9HfzvUe8KQFbxs2BtkS8yqQEbIiuHO06 uDPTMTpaEmhTJT7x8DOS+8C/XqlbVQjsf7u4CqZg/0HDYQsySO1KNEhR3qTn7vZfyGM+ OrXRWpA6cblH5hNjRs8l/oxbleHJlWSORh14el+d4mPG7CJ+T56+ALKaPh2VLQ6evYJO RJCliGHhFXjYzP+GzCPrF3ekPQEKrcvpbowuffuDayTZkY15XPWGU1a/ySUd4WxcxhyF zC1w== X-Forwarded-Encrypted: i=1; AHgh+Rq6ZmIFOVuOZdsYSUTcpYQUKfpxPYfieXfKJxp/bhnJjiBJBXkLbpRGUpDUMiZ5bWKosw/trMqnDH7U8AI=@vger.kernel.org X-Gm-Message-State: AFuF++khWBJMDa58UBW/f5FCeUYTFORN/z2Wfk7fdPxUKOiNixOLarcN osJrZhiKqEe0Ysdjqa8MiDfHcf9ypj6U0XE8abCw4ycZLM2LyaRarFY19p/nPy9FdAtqI/P4d93 Mw0u4+61ldMt3kP6YmZslDWLvtoCAE47SBYob7eaMsVEwDrCd06I7/bHAgAA= Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Received: by 2002:a05:6820:c2c3:20b0:6aa:e252:dc59 with SMTP id 006d021491bc7-6b1591d5593mr13671847eaf.5.1787453253873; Sat, 22 Aug 2026 19:47:33 -0700 (PDT) Date: Sat, 22 Aug 2026 19:47:33 -0700 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <6a8a5f45.ae6ddae5.3da009.005f.GAE@google.com> Subject: [syzbot] [kernel?] BUG: scheduling while atomic in drain_urb_queue From: syzbot To: anna-maria@linutronix.de, frederic@kernel.org, linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com, tglx@kernel.org Content-Type: text/plain; charset="UTF-8" Hello, syzbot found the following issue on: HEAD commit: 26260251022f Merge tag 'livepatching-for-7.3' of git://git.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=137d9179580000 kernel config: https://syzkaller.appspot.com/x/.config?x=b0978f5ed2905b98 dashboard link: https://syzkaller.appspot.com/bug?extid=919c31c248e8a37b89d1 compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44 Unfortunately, I don't have any reproducer for this issue yet. Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/6faac2ffacf9/disk-26260251.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/ea31321aed8f/vmlinux-26260251.xz kernel image: https://storage.googleapis.com/syzbot-assets/143bbfb147dc/bzImage-26260251.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+919c31c248e8a37b89d1@syzkaller.appspotmail.com BUG: scheduling while atomic: kworker/0:0/9670/0x00010001 locks held by kworker/0:0/9670: 7, on CPU#0: #0: ffff88801fe91540 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: process_one_work+0x1466/0x1b10 kernel/workqueue.c:3362 #1: ffffc90005037d08 ((work_completion)(&hub->events)){+.+.}-{0:0}, at: process_one_work+0xa2c/0x1b10 kernel/workqueue.c:3363 #2: ffff88802ad3d1d8 (&dev->mutex){....}-{4:4}, at: device_lock include/linux/device.h:1104 [inline] #2: ffff88802ad3d1d8 (&dev->mutex){....}-{4:4}, at: hub_event+0x1bb/0x4420 drivers/usb/core/hub.c:5907 #3: ffff88807a08b1d8 (&dev->mutex){....}-{4:4}, at: device_lock include/linux/device.h:1104 [inline] #3: ffff88807a08b1d8 (&dev->mutex){....}-{4:4}, at: __device_attach+0x7e/0x4d0 drivers/base/dd.c:1073 #4: ffff8880762091a0 (&dev->mutex){....}-{4:4}, at: device_lock include/linux/device.h:1104 [inline] #4: ffff8880762091a0 (&dev->mutex){....}-{4:4}, at: __device_attach+0x7e/0x4d0 drivers/base/dd.c:1073 #5: ffffffff90bb8560 (register_mutex#6){+.+.}-{4:4}, at: class_mutex_constructor include/linux/mutex.h:253 [inline] #5: ffffffff90bb8560 (register_mutex#6){+.+.}-{4:4}, at: usb_audio_probe+0x385/0x3b10 sound/usb/card.c:985 #6: ffff88807e55a160 (&rmidi->open_mutex){+.+.}-{4:4}, at: class_mutex_constructor include/linux/mutex.h:253 [inline] #6: ffff88807e55a160 (&rmidi->open_mutex){+.+.}-{4:4}, at: rawmidi_release_priv+0x45/0x280 sound/core/rawmidi.c:574 Modules linked in: Preemption disabled at: [] softirq_handle_begin kernel/softirq.c:486 [inline] [] handle_softirqs+0xf3/0x9d0 kernel/softirq.c:621 Kernel panic - not syncing: scheduling while atomic: panic_on_warn set ... CPU: 0 UID: 0 PID: 9670 Comm: kworker/0:0 Tainted: G L syzkaller #0 PREEMPT(full) Tainted: [L]=SOFTLOCKUP Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/05/2026 Workqueue: usb_hub_wq hub_event Call Trace: __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x100/0x190 lib/dump_stack.c:120 vpanic+0x553/0x970 kernel/panic.c:651 panic+0xd1/0xe0 kernel/panic.c:788 check_panic_on_warn kernel/panic.c:525 [inline] check_panic_on_warn.cold+0x19/0x34 kernel/panic.c:520 __schedule_bug.cold+0xc4/0xf4 kernel/sched/core.c:6076 schedule_debug kernel/sched/core.c:6105 [inline] __schedule+0x4066/0x6920 kernel/sched/core.c:7119 __schedule_loop kernel/sched/core.c:7347 [inline] schedule+0xdd/0x2c0 kernel/sched/core.c:7362 schedule_timeout+0x127/0x280 kernel/time/sleep_timeout.c:99 drain_urb_queue.part.0+0x303/0x470 sound/usb/midi2.c:246 drain_urb_queue sound/usb/midi2.c:242 [inline] snd_usb_midi_v2_drain+0x79/0xb0 sound/usb/midi2.c:383 snd_ump_rawmidi_drain+0x85/0xb0 sound/core/ump.c:294 snd_rawmidi_drain_output+0x3b3/0x880 sound/core/rawmidi.c:282 close_substream.part.0+0x3eb/0x860 sound/core/rawmidi.c:551 close_substream include/linux/mutex.h:253 [inline] rawmidi_release_priv+0x210/0x280 sound/core/rawmidi.c:580 snd_rawmidi_kernel_release+0x3a/0xd0 sound/core/rawmidi.c:596 ump_request_close sound/core/ump.c:623 [inline] snd_ump_parse_endpoint+0x15f/0xb00 sound/core/ump.c:1135 parse_ump_endpoints sound/usb/midi2.c:810 [inline] snd_usb_midi_v2_create+0x1b97/0x4070 sound/usb/midi2.c:1158 snd_usb_create_stream.isra.0+0x386/0x4d0 sound/usb/card.c:290 snd_usb_create_streams sound/usb/card.c:392 [inline] usb_audio_probe+0xf0b/0x3b10 sound/usb/card.c:1065 usb_probe_interface+0x303/0x8f0 drivers/usb/core/driver.c:396 call_driver_probe drivers/base/dd.c:628 [inline] really_probe+0x241/0xa60 drivers/base/dd.c:706 __driver_probe_device+0x210/0x460 drivers/base/dd.c:868 driver_probe_device+0x4a/0x140 drivers/base/dd.c:898 __device_attach_driver+0x1df/0x320 drivers/base/dd.c:1026 bus_for_each_drv+0x159/0x1e0 drivers/base/bus.c:500 __device_attach+0x1e4/0x4d0 drivers/base/dd.c:1098 device_initial_probe+0xaf/0xd0 drivers/base/dd.c:1153 bus_probe_device+0x64/0x160 drivers/base/bus.c:620 device_add+0x121d/0x1970 drivers/base/core.c:3776 usb_set_configuration+0xd97/0x1c60 drivers/usb/core/message.c:2268 usb_generic_driver_probe+0xa1/0xe0 drivers/usb/core/generic.c:250 usb_probe_device+0xef/0x400 drivers/usb/core/driver.c:291 call_driver_probe drivers/base/dd.c:628 [inline] really_probe+0x241/0xa60 drivers/base/dd.c:706 __driver_probe_device+0x210/0x460 drivers/base/dd.c:868 driver_probe_device+0x4a/0x140 drivers/base/dd.c:898 __device_attach_driver+0x1df/0x320 drivers/base/dd.c:1026 bus_for_each_drv+0x159/0x1e0 drivers/base/bus.c:500 __device_attach+0x1e4/0x4d0 drivers/base/dd.c:1098 device_initial_probe+0xaf/0xd0 drivers/base/dd.c:1153 bus_probe_device+0x64/0x160 drivers/base/bus.c:620 device_add+0x121d/0x1970 drivers/base/core.c:3776 usb_new_device.part.0+0xcc2/0x1686 drivers/usb/core/hub.c:2703 usb_new_device include/linux/workqueue.h:714 [inline] hub_port_connect drivers/usb/core/hub.c:5575 [inline] hub_port_connect_change drivers/usb/core/hub.c:5715 [inline] port_event drivers/usb/core/hub.c:5879 [inline] hub_event.cold+0x1e3/0xe90 drivers/usb/core/hub.c:5961 process_one_work+0xac7/0x1b10 kernel/workqueue.c:3387 process_scheduled_works kernel/workqueue.c:3470 [inline] worker_thread+0x5ef/0xe50 kernel/workqueue.c:3551 kthread+0x373/0x450 kernel/kthread.c:436 ret_from_fork+0x730/0xd60 arch/x86/kernel/process.c:158 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245 Kernel Offset: disabled Rebooting in 86400 seconds.. --- 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 syzkaller@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