All of lore.kernel.org
 help / color / mirror / Atom feed
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: [syzbot] [pm?] WARNING in enable_work
Date: Wed, 21 Aug 2024 03:14:26 -0700	[thread overview]
Message-ID: <0000000000008c97fd06202ece3b@google.com> (raw)

Hello,

syzbot found the following issue on:

HEAD commit:    e5fa841af679 Merge tag 'pull-fixes' of git://git.kernel.or..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16b8adf3980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=7229118d88b4a71b
dashboard link: https://syzkaller.appspot.com/bug?extid=7053fbd8757fecbbe492
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/2f8ce1609883/disk-e5fa841a.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/3a0d8aabc8a5/vmlinux-e5fa841a.xz
kernel image: https://storage.googleapis.com/syzbot-assets/7a7f6c33922b/bzImage-e5fa841a.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: 5233 at kernel/workqueue.c:4290 work_offqd_enable kernel/workqueue.c:4290 [inline]
WARNING: CPU: 1 PID: 5233 at kernel/workqueue.c:4290 enable_work+0x34d/0x360 kernel/workqueue.c:4461
Modules linked in:
CPU: 1 UID: 0 PID: 5233 Comm: kworker/1:3 Not tainted 6.11.0-rc3-syzkaller-00279-ge5fa841af679 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024
Workqueue: usb_hub_wq hub_event
RIP: 0010:work_offqd_enable kernel/workqueue.c:4290 [inline]
RIP: 0010:enable_work+0x34d/0x360 kernel/workqueue.c:4461
Code: d8 5b 41 5c 41 5d 41 5e 41 5f 5d e9 88 cd 92 0a e8 68 17 36 00 c6 05 bf 2e a4 0e 01 90 48 c7 c7 80 10 0a 8c e8 a4 3e f8 ff 90 <0f> 0b 90 90 e9 56 ff ff ff e8 e5 25 59 0a 0f 1f 44 00 00 90 90 90
RSP: 0018:ffffc900042270c0 EFLAGS: 00010046
RAX: 022b146294645100 RBX: 0000000000000000 RCX: 0000000000100000
RDX: ffffc900177a9000 RSI: 00000000000fffff RDI: 0000000000100000
RBP: ffffc90004227190 R08: ffffffff8155b4d2 R09: 1ffff1101726519a
R10: dffffc0000000000 R11: ffffed101726519b R12: 1ffff92000844e1c
R13: 1ffff92000844e24 R14: 0000000000800001 R15: ffff88802d570738
FS:  0000000000000000(0000) GS:ffff8880b9300000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b3321bff8 CR3: 000000005bbf0000 CR4: 0000000000350ef0
Call Trace:
 <TASK>
 __cancel_work_sync+0xf5/0x110 kernel/workqueue.c:4331
 thermal_zone_device_unregister+0x296/0x3f0 drivers/thermal/thermal_core.c:1660
 psy_unregister_thermal drivers/power/supply/power_supply_core.c:1333 [inline]
 power_supply_unregister+0xe8/0x140 drivers/power/supply/power_supply_core.c:1610
 thunderstrike_destroy drivers/hid/hid-nvidia-shield.c:927 [inline]
 shield_remove+0x72/0x120 drivers/hid/hid-nvidia-shield.c:1104
 hid_device_remove+0x227/0x370
 device_remove drivers/base/dd.c:566 [inline]
 __device_release_driver drivers/base/dd.c:1272 [inline]
 device_release_driver_internal+0x4ab/0x7c0 drivers/base/dd.c:1295
 bus_remove_device+0x34f/0x420 drivers/base/bus.c:574
 device_del+0x57a/0x9b0 drivers/base/core.c:3871
 hid_remove_device drivers/hid/hid-core.c:2914 [inline]
 hid_destroy_device+0x68/0x100 drivers/hid/hid-core.c:2934
 usbhid_disconnect+0x9e/0xc0 drivers/hid/usbhid/hid-core.c:1458
 usb_unbind_interface+0x260/0x940 drivers/usb/core/driver.c:461
 device_remove drivers/base/dd.c:568 [inline]
 __device_release_driver drivers/base/dd.c:1272 [inline]
 device_release_driver_internal+0x505/0x7c0 drivers/base/dd.c:1295
 bus_remove_device+0x34f/0x420 drivers/base/bus.c:574
 device_del+0x57a/0x9b0 drivers/base/core.c:3871
 usb_disable_device+0x3bf/0x850 drivers/usb/core/message.c:1418
 usb_disconnect+0x340/0x950 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+0x1ebc/0x5150 drivers/usb/core/hub.c:5903
 process_one_work kernel/workqueue.c:3231 [inline]
 process_scheduled_works+0xa2e/0x1830 kernel/workqueue.c:3312
 worker_thread+0x86d/0xd40 kernel/workqueue.c:3390
 kthread+0x2f2/0x390 kernel/kthread.c:389
 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
 </TASK>


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

             reply	other threads:[~2024-08-21 10:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-21 10:14 syzbot [this message]
2024-09-18  4:50 ` [syzbot] [pm?] WARNING in enable_work 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=0000000000008c97fd06202ece3b@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.