From: syzbot <syzbot+7053fbd8757fecbbe492@syzkaller.appspotmail.com>
To: daniel.lezcano@linaro.org, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org, lukasz.luba@arm.com,
rafael@kernel.org, rui.zhang@intel.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [pm?] WARNING in enable_work
Date: Tue, 17 Sep 2024 21:50:23 -0700 [thread overview]
Message-ID: <000000000000428af806225d8bf6@google.com> (raw)
In-Reply-To: <0000000000008c97fd06202ece3b@google.com>
syzbot has found a reproducer for the following issue on:
HEAD commit: a940d9a43e62 Merge tag 'soc-arm-6.12' of git://git.kernel...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1236bfc7980000
kernel config: https://syzkaller.appspot.com/x/.config?x=44d46e514184cd24
dashboard link: https://syzkaller.appspot.com/bug?extid=7053fbd8757fecbbe492
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=144a9207980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=124a9207980000
Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/7bc7510fe41f/non_bootable_disk-a940d9a4.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/e9929bfe422c/vmlinux-a940d9a4.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a6c74ee261ed/bzImage-a940d9a4.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+7053fbd8757fecbbe492@syzkaller.appspotmail.com
------------[ cut here ]------------
workqueue: work disable count underflowed
WARNING: CPU: 1 PID: 56 at kernel/workqueue.c:4298 work_offqd_enable kernel/workqueue.c:4298 [inline]
WARNING: CPU: 1 PID: 56 at kernel/workqueue.c:4298 enable_work+0x2fa/0x340 kernel/workqueue.c:4469
Modules linked in:
CPU: 1 UID: 0 PID: 56 Comm: kworker/1:1 Not tainted 6.11.0-syzkaller-03917-ga940d9a43e62 #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014
Workqueue: usb_hub_wq hub_event
RIP: 0010:work_offqd_enable kernel/workqueue.c:4298 [inline]
RIP: 0010:enable_work+0x2fa/0x340 kernel/workqueue.c:4469
Code: 89 ee e8 f9 4d 35 00 45 84 ed 0f 85 28 fe ff ff e8 0b 4c 35 00 c6 05 50 81 af 0e 01 90 48 c7 c7 80 dc 4b 8b e8 47 32 f7 ff 90 <0f> 0b 90 90 e9 05 fe ff ff 48 89 ef e8 05 09 94 00 e9 a9 fe ff ff
RSP: 0018:ffffc90000a87448 EFLAGS: 00010082
RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffff814e2c49
RDX: ffff88802052c880 RSI: ffffffff814e2c56 RDI: 0000000000000001
RBP: ffff888027663718 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 1ffff92000150e8a
R13: 0000000000000000 R14: ffffffff8f5ed040 R15: ffffffff8f5ed040
FS: 0000000000000000(0000) GS:ffff88806a700000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fc995722e18 CR3: 000000000db7c000 CR4: 0000000000350ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
__cancel_work_sync+0xe7/0x130 kernel/workqueue.c:4339
thermal_zone_device_unregister drivers/thermal/thermal_core.c:1599 [inline]
thermal_zone_device_unregister+0x27c/0x460 drivers/thermal/thermal_core.c:1569
psy_unregister_thermal drivers/power/supply/power_supply_core.c:1333 [inline]
power_supply_unregister+0x10a/0x150 drivers/power/supply/power_supply_core.c:1610
thunderstrike_destroy drivers/hid/hid-nvidia-shield.c:927 [inline]
shield_remove+0x75/0x130 drivers/hid/hid-nvidia-shield.c:1104
hid_device_remove+0xce/0x260 drivers/hid/hid-core.c:2730
device_remove+0xc8/0x170 drivers/base/dd.c:566
__device_release_driver drivers/base/dd.c:1272 [inline]
device_release_driver_internal+0x44a/0x610 drivers/base/dd.c:1295
bus_remove_device+0x22f/0x420 drivers/base/bus.c:574
device_del+0x396/0x9f0 drivers/base/core.c:3871
hid_remove_device drivers/hid/hid-core.c:2914 [inline]
hid_destroy_device+0xe5/0x150 drivers/hid/hid-core.c:2934
usbhid_disconnect+0xa0/0xe0 drivers/hid/usbhid/hid-core.c:1458
usb_unbind_interface+0x1e8/0x970 drivers/usb/core/driver.c:461
device_remove drivers/base/dd.c:568 [inline]
device_remove+0x122/0x170 drivers/base/dd.c:560
__device_release_driver drivers/base/dd.c:1272 [inline]
device_release_driver_internal+0x44a/0x610 drivers/base/dd.c:1295
bus_remove_device+0x22f/0x420 drivers/base/bus.c:574
device_del+0x396/0x9f0 drivers/base/core.c:3871
usb_disable_device+0x36c/0x7f0 drivers/usb/core/message.c:1418
usb_disconnect+0x2e1/0x920 drivers/usb/core/hub.c:2304
hub_port_connect drivers/usb/core/hub.c:5361 [inline]
hub_port_connect_change drivers/usb/core/hub.c:5661 [inline]
port_event drivers/usb/core/hub.c:5821 [inline]
hub_event+0x1da5/0x4e10 drivers/usb/core/hub.c:5903
process_one_work+0x9c5/0x1b40 kernel/workqueue.c:3231
process_scheduled_works kernel/workqueue.c:3312 [inline]
worker_thread+0x6c8/0xf00 kernel/workqueue.c:3393
kthread+0x2c1/0x3a0 kernel/kthread.c:389
ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
</TASK>
---
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
prev parent reply other threads:[~2024-09-18 4:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-21 10:14 [syzbot] [pm?] WARNING in enable_work syzbot
2024-09-18 4:50 ` syzbot [this message]
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=000000000000428af806225d8bf6@google.com \
--to=syzbot+7053fbd8757fecbbe492@syzkaller.appspotmail.com \
--cc=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=rafael@kernel.org \
--cc=rui.zhang@intel.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.