From: Hillf Danton <hdanton@sina.com>
To: syzbot <syzbot+6f433bde86418d3f4fec@syzkaller.appspotmail.com>
Cc: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [usb?] WARNING in flush_delayed_work
Date: Sat, 28 Jun 2025 11:49:40 +0800 [thread overview]
Message-ID: <20250628034941.2001-1-hdanton@sina.com> (raw)
In-Reply-To: <685f1221.a00a0220.274b5f.0002.GAE@google.com>
> Date: Fri, 27 Jun 2025 14:50:25 -0700
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 2aeda9592360 Add linux-next specific files for 20250627
> git tree: linux-next
> console+strace: https://syzkaller.appspot.com/x/log.txt?x=1331908c580000
> kernel config: https://syzkaller.appspot.com/x/.config?x=9e7e53eaffada5f7
> dashboard link: https://syzkaller.appspot.com/bug?extid=6f433bde86418d3f4fec
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1484e08c580000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=141c43d4580000
#syz test
--- x/drivers/usb/core/hub.c
+++ y/drivers/usb/core/hub.c
@@ -1872,6 +1872,7 @@ static bool hub_descriptor_is_sane(struc
return true;
}
+static void hub_init_dumy_func(struct work_struct *ws) {}
static int hub_probe(struct usb_interface *intf, const struct usb_device_id *id)
{
struct usb_host_interface *desc;
@@ -1976,7 +1977,7 @@ static int hub_probe(struct usb_interfac
hub->intfdev = &intf->dev;
hub->hdev = hdev;
INIT_DELAYED_WORK(&hub->leds, led_work);
- INIT_DELAYED_WORK(&hub->init_work, NULL);
+ INIT_DELAYED_WORK(&hub->init_work, hub_init_dumy_func);
INIT_WORK(&hub->events, hub_event);
INIT_LIST_HEAD(&hub->onboard_devs);
spin_lock_init(&hub->irq_urb_lock);
--
next prev parent reply other threads:[~2025-06-28 3:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-27 21:50 [syzbot] [usb?] WARNING in flush_delayed_work syzbot
2025-06-28 3:49 ` Hillf Danton [this message]
2025-06-28 6:28 ` syzbot
2025-07-04 13:42 ` Tetsuo Handa
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=20250628034941.2001-1-hdanton@sina.com \
--to=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+6f433bde86418d3f4fec@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 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.