From: syzbot <syzbot+8baacc4139f12fa77909@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [usb?] BUG: sleeping function called from invalid context in dummy_dequeue
Date: Mon, 25 Aug 2025 05:53:02 -0700 [thread overview]
Message-ID: <68ac5cae.a70a0220.303e5.0002.GAE@google.com> (raw)
In-Reply-To: <20250825102648.5395-1-hdanton@sina.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
WARNING in dummy_dequeue
------------[ cut here ]------------
raw_local_irq_restore() called with IRQs enabled
WARNING: CPU: 0 PID: 6659 at kernel/locking/irqflag-debug.c:10 warn_bogus_irq_restore+0x2a/0x40 kernel/locking/irqflag-debug.c:10
Modules linked in:
CPU: 0 UID: 0 PID: 6659 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT_{RT,(full)}
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
RIP: 0010:warn_bogus_irq_restore+0x2a/0x40 kernel/locking/irqflag-debug.c:10
Code: f3 0f 1e fa 90 80 3d 83 fb 10 04 00 74 07 90 c3 cc cc cc cc cc c6 05 73 fb 10 04 01 90 48 c7 c7 40 ee 0a 8b e8 d7 dc 8c f6 90 <0f> 0b 90 90 90 e9 cc ad 03 00 cc cc cc cc cc cc cc cc cc cc cc cc
RSP: 0018:ffffc900041378f8 EFLAGS: 00010246
RAX: 7b813d5b6b8f1700 RBX: 0000000000000000 RCX: ffff888036dc9dc0
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc900041379d8 R08: 0000000000000000 R09: 0000000000000000
R10: dffffc0000000000 R11: ffffed1017104863 R12: dffffc0000000000
R13: ffff8880374cde64 R14: 1ffff92000826f28 R15: 0000000000000200
FS: 00007f4ab96ee6c0(0000) GS:ffff8881268c2000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b34363fff CR3: 000000001da8c000 CR4: 00000000003526f0
Call Trace:
<TASK>
dummy_dequeue+0x2d7/0x3d0 drivers/usb/gadget/udc/dummy_hcd.c:786
usb_ep_dequeue+0x66/0x250 drivers/usb/gadget/udc/core.c:330
raw_process_ep_io+0x5a3/0xaf0 drivers/usb/gadget/legacy/raw_gadget.c:1124
raw_ioctl_ep_write drivers/usb/gadget/legacy/raw_gadget.c:1152 [inline]
raw_ioctl+0x22dc/0x3ba0 drivers/usb/gadget/legacy/raw_gadget.c:1324
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:598 [inline]
__se_sys_ioctl+0xfc/0x170 fs/ioctl.c:584
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f4aba07e7eb
Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 1c 48 8b 44 24 18 64 48 2b 04 25 28 00 00
RSP: 002b:00007f4ab96ecf70 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0000000000000044 RCX: 00007f4aba07e7eb
RDX: 00007f4ab96ecff0 RSI: 0000000040085507 RDI: 0000000000000003
RBP: 0000000000000003 R08: 00007f4aba3d0320 R09: 0000000000000000
R10: 0000000000000003 R11: 0000000000000246 R12: 0000200000000080
R13: 000000000000000a R14: 00007f4aba2a5fa0 R15: 00007ffc6e132658
</TASK>
Tested on:
commit: 1b237f19 Linux 6.17-rc3
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=144a6862580000
kernel config: https://syzkaller.appspot.com/x/.config?x=e1e1566c7726877e
dashboard link: https://syzkaller.appspot.com/bug?extid=8baacc4139f12fa77909
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
patch: https://syzkaller.appspot.com/x/patch.diff?x=174aec42580000
next prev parent reply other threads:[~2025-08-25 12:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-25 8:51 [syzbot] [usb?] BUG: sleeping function called from invalid context in dummy_dequeue syzbot
2025-08-25 10:26 ` Hillf Danton
2025-08-25 12:53 ` syzbot [this message]
2025-08-25 14:18 ` Alan Stern
2025-08-25 14:54 ` syzbot
2025-08-25 16:00 ` [PATCH] USB: gadget: dummy-hcd: Fix locking bug in RT-enabled kernels Alan Stern
2025-08-25 16:05 ` Sebastian Andrzej Siewior
2025-08-26 1:58 ` [syzbot] [usb?] BUG: sleeping function called from invalid context in dummy_dequeue Hillf Danton
2025-08-26 3:14 ` syzbot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=68ac5cae.a70a0220.303e5.0002.GAE@google.com \
--to=syzbot+8baacc4139f12fa77909@syzkaller.appspotmail.com \
--cc=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.