From: syzbot <syzbot+8baacc4139f12fa77909@syzkaller.appspotmail.com>
To: bigeasy@linutronix.de, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
stern@rowland.harvard.edu, syzkaller-bugs@googlegroups.com,
ysk@kzalloc.com
Subject: Re: [syzbot] [usb?] BUG: sleeping function called from invalid context in dummy_dequeue
Date: Mon, 25 Aug 2025 07:54:04 -0700 [thread overview]
Message-ID: <68ac790c.050a0220.37038e.0095.GAE@google.com> (raw)
In-Reply-To: <0d6d8778-a45e-498f-9e31-1d926f582d7e@rowland.harvard.edu>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+8baacc4139f12fa77909@syzkaller.appspotmail.com
Tested-by: syzbot+8baacc4139f12fa77909@syzkaller.appspotmail.com
Tested on:
commit: 8d245acc Merge tag 'char-misc-6.17-rc3' of git://git.k..
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/
console output: https://syzkaller.appspot.com/x/log.txt?x=17b38462580000
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=15ee6862580000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2025-08-25 14:54 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
2025-08-25 14:18 ` Alan Stern
2025-08-25 14:54 ` syzbot [this message]
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=68ac790c.050a0220.37038e.0095.GAE@google.com \
--to=syzbot+8baacc4139f12fa77909@syzkaller.appspotmail.com \
--cc=bigeasy@linutronix.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=syzkaller-bugs@googlegroups.com \
--cc=ysk@kzalloc.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.