From: syzbot <syzbot+b6f11035e572f08bc20f@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [usb?] INFO: task hung in hub_port_init (3)
Date: Sat, 04 Nov 2023 01:07:07 -0700 [thread overview]
Message-ID: <0000000000006e018d06094f1ba1@google.com> (raw)
In-Reply-To: <20231104074445.1237-1-hdanton@sina.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
kernel panic: KASAN: panic_on_warn set ...
>ffff888020985500: fa fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
^
ffff888020985580: fb fb fb fb fb fb fb fb fc fc fc fc fc fc fc fc
ffff888020985600: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
==================================================================
Kernel panic - not syncing: KASAN: panic_on_warn set ...
CPU: 0 PID: 2911 Comm: kworker/u4:13 Not tainted 6.6.0-syzkaller-14142-g90b0c2b2edd1-dirty #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/09/2023
Workqueue: usbip_event event_handler
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e7/0x2d0 lib/dump_stack.c:106
panic+0x349/0x850 kernel/panic.c:344
check_panic_on_warn+0x82/0xa0 kernel/panic.c:237
end_report+0x6e/0x130 mm/kasan/report.c:225
kasan_report+0x153/0x170 mm/kasan/report.c:590
pickup_urb_and_free_priv+0x282/0x370 drivers/usb/usbip/vhci_rx.c:24
vhci_cleanup_unlink_list+0x12d/0x490 drivers/usb/usbip/vhci_hcd.c:966
vhci_device_unlink_cleanup drivers/usb/usbip/vhci_hcd.c:1000 [inline]
vhci_shutdown_connection+0x203/0x4a0 drivers/usb/usbip/vhci_hcd.c:1037
event_handler+0x24e/0x4b0 drivers/usb/usbip/usbip_event.c:79
process_one_work kernel/workqueue.c:2630 [inline]
process_scheduled_works+0x90f/0x1400 kernel/workqueue.c:2703
worker_thread+0xa5f/0xff0 kernel/workqueue.c:2784
kthread+0x2d3/0x370 kernel/kthread.c:388
ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:147
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:242
</TASK>
Kernel Offset: disabled
Rebooting in 86400 seconds..
Tested on:
commit: 90b0c2b2 Merge tag 'pinctrl-v6.7-1' of git://git.kerne..
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
console output: https://syzkaller.appspot.com/x/log.txt?x=11d567f3680000
kernel config: https://syzkaller.appspot.com/x/.config?x=93ac5233c138249e
dashboard link: https://syzkaller.appspot.com/bug?extid=b6f11035e572f08bc20f
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=15c49eeb680000
next parent reply other threads:[~2023-11-04 8:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231104074445.1237-1-hdanton@sina.com>
2023-11-04 8:07 ` syzbot [this message]
[not found] <20231104112657.1312-1-hdanton@sina.com>
2023-11-04 12:50 ` syzbot
[not found] <20231104010547.1505-1-hdanton@sina.com>
2023-11-04 1:23 ` syzbot
2023-03-28 12:23 syzbot
2023-06-09 19:25 ` syzbot
2023-11-03 14:03 ` Muhammad Usama Anjum
2023-11-03 15:04 ` Alan Stern
2023-11-08 11:25 ` Muhammad Usama Anjum
2023-11-08 16:12 ` Alan Stern
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=0000000000006e018d06094f1ba1@google.com \
--to=syzbot+b6f11035e572f08bc20f@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 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®