From: syzbot <syzbot+31117fde582fe6a0cd62@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Forwarded: Re: test patch
Date: Mon, 07 Sep 2026 07:14:07 -0700 [thread overview]
Message-ID: <6a9ec6af.6e6c5f9e.240462.0001.GAE@google.com> (raw)
In-Reply-To: <6a6d375e.2d659fcc.1d46f5.01a4.GAE@google.com>
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.
***
Subject: Re: test patch
Author: syedtayyabfarooq08@gmail.com
#syz test
diff --git a/drivers/usb/usbip/usbip_event.c b/drivers/usb/usbip/usbip_event.c
index 0e00c2d000f8..e498102e8b26 100644
--- a/drivers/usb/usbip/usbip_event.c
+++ b/drivers/usb/usbip/usbip_event.c
@@ -105,6 +105,11 @@ int usbip_start_eh(struct usbip_device *ud)
}
EXPORT_SYMBOL_GPL(usbip_start_eh);
+#define WORK_QUEUE_NAME "usbip_event"
+
+static struct workqueue_struct *usbip_queue;
+static DECLARE_WORK(usbip_work, event_handler);
+
void usbip_stop_eh(struct usbip_device *ud)
{
unsigned long pending = ud->event & ~USBIP_EH_BYE;
@@ -115,16 +120,12 @@ void usbip_stop_eh(struct usbip_device *ud)
if (pending)
usbip_dbg_eh("usbip_eh waiting completion %lx\n", pending);
- wait_event_interruptible(ud->eh_waitq, !(ud->event & ~USBIP_EH_BYE));
+ wait_event(ud->eh_waitq, !(ud->event & ~USBIP_EH_BYE));
+ flush_workqueue(usbip_queue);
usbip_dbg_eh("usbip_eh has stopped\n");
}
EXPORT_SYMBOL_GPL(usbip_stop_eh);
-#define WORK_QUEUE_NAME "usbip_event"
-
-static struct workqueue_struct *usbip_queue;
-static DECLARE_WORK(usbip_work, event_handler);
-
int usbip_init_eh(void)
{
usbip_queue = create_singlethread_workqueue(WORK_QUEUE_NAME);
next prev parent reply other threads:[~2026-09-07 14:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-01 0:01 [syzbot] [usb?] KASAN: slab-use-after-free Read in vhci_shutdown_connection syzbot
2026-08-04 7:58 ` syzbot
2026-09-07 13:57 ` Forwarded: Re: test patch syzbot
2026-09-07 14:14 ` syzbot [this message]
2026-09-08 11:07 ` syzbot
2026-09-09 6:32 ` syzbot
2026-09-09 12:33 ` syzbot
-- strict thread matches above, loose matches on Subject: below --
2026-09-06 20:15 [syzbot] [trace?] WARNING in ring_buffer_map_get_reader (3) syzbot
2026-09-10 11:48 ` Forwarded: Re: test patch syzbot
2026-08-16 14:48 [syzbot] KASAN: slab-out-of-bounds Read in fb_pad_aligned_buffer (3) syzbot
2026-09-22 11:17 ` Forwarded: Re: test patch syzbot
2026-07-31 6:14 [syzbot] [serial?] KASAN: slab-use-after-free Write in tty_init_dev syzbot
2026-09-09 7:10 ` Forwarded: Re: test patch syzbot
2026-09-09 7:44 ` syzbot
2026-09-09 11:35 ` syzbot
2026-09-09 13:06 ` syzbot
2026-09-10 6:09 ` 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=6a9ec6af.6e6c5f9e.240462.0001.GAE@google.com \
--to=syzbot+31117fde582fe6a0cd62@syzkaller.appspotmail.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.