From: Hillf Danton <hdanton@sina.com>
To: syzbot <syzbot+c793a7eca38803212c61@syzkaller.appspotmail.com>
Cc: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [usb?] INFO: rcu detected stall in schedule_timeout (6)
Date: Fri, 17 May 2024 06:28:43 +0800 [thread overview]
Message-ID: <20240516222843.1500-1-hdanton@sina.com> (raw)
In-Reply-To: <000000000000051b2d06189716c3@google.com>
On Thu, 16 May 2024 12:17:28 -0700
> syzbot found the following issue on:
>
> HEAD commit: 75fa778d74b7 Add linux-next specific files for 20240510
> git tree: linux-next
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=151d9c78980000
#syz test https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git 75fa778d74b7
--- x/drivers/media/rc/imon.c
+++ y/drivers/media/rc/imon.c
@@ -1758,6 +1758,7 @@ static void usb_rx_callback_intf0(struct
switch (urb->status) {
case -ENOENT: /* usbcore unlink successful! */
+ case -EPROTO:
return;
case -ESHUTDOWN: /* transport endpoint was shut down */
--
next prev parent reply other threads:[~2024-05-16 22:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-16 19:17 syzbot
2024-05-16 22:01 ` syzbot
2024-06-04 12:05 ` Marcello Sylvester Bauer
2024-06-04 14:20 ` Alan Stern
2024-06-24 10:25 ` Needed help: dummy_hcd: Fix stalls/inconsistent_lock_state due to hrtimer migration Marcello Sylvester Bauer
2024-06-24 13:19 ` Thomas Gleixner
2024-05-16 22:28 ` Hillf Danton [this message]
2024-05-17 0:18 ` [syzbot] [usb?] INFO: rcu detected stall in schedule_timeout (6) syzbot
2024-06-25 9:02 ` [syzbot] " syzbot
2024-06-25 10:24 ` syzbot
2024-07-08 10:56 ` syzbot
[not found] <b4ace972d8d8125d04851f9961399270fa297747.camel@9elements.com>
2024-06-25 9:22 ` syzbot
[not found] <dd54a706e0d5ba7cb01e073a256b6855409684db.camel@9elements.com>
2024-06-25 11:31 ` syzbot
[not found] <167e42c556fa9f7e59f8ada1957d17f950befa42.camel@9elements.com>
2024-07-08 12:57 ` 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=20240516222843.1500-1-hdanton@sina.com \
--to=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+c793a7eca38803212c61@syzkaller.appspotmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®