WARNING in pm_qos_remove_request

9 views
Skip to first unread message

syzbot

unread,
Nov 29, 2020, 6:53:16 PM11/29/20
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 87335852 Linux 4.14.209
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=177dffb3500000
kernel config: https://syzkaller.appspot.com/x/.config?x=a932ed2a762225b
dashboard link: https://syzkaller.appspot.com/bug?extid=8cb60ca357880f414585
compiler: gcc (GCC) 10.1.0-syz 20200507
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12aa54ad500000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1517f445500000

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+8cb60c...@syzkaller.appspotmail.com

pm_qos_remove_request() called for unknown object
------------[ cut here ]------------
WARNING: CPU: 0 PID: 8772 at kernel/power/qos.c:534 pm_qos_remove_request.cold+0x11/0x18 kernel/power/qos.c:534
Kernel panic - not syncing: panic_on_warn set ...

CPU: 0 PID: 8772 Comm: syz-executor949 Not tainted 4.14.209-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0x1b2/0x283 lib/dump_stack.c:58
panic+0x1f9/0x42d kernel/panic.c:183
__warn.cold+0x20/0x4b kernel/panic.c:547
report_bug+0x208/0x249 lib/bug.c:186
fixup_bug arch/x86/kernel/traps.c:177 [inline]
fixup_bug arch/x86/kernel/traps.c:172 [inline]
do_error_trap+0x195/0x2d0 arch/x86/kernel/traps.c:295
invalid_op+0x1b/0x40 arch/x86/entry/entry_64.S:964
RIP: 0010:pm_qos_remove_request.cold+0x11/0x18 kernel/power/qos.c:534
RSP: 0018:ffff888093dd7c58 EFLAGS: 00010282
RAX: 0000000000000031 RBX: ffff8880a54c2e00 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff878bbac0 RDI: ffffed10127baf81
RBP: ffff888235a8d240 R08: 0000000000000031 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 1ffff110127baf99
R13: 0000000000004112 R14: ffff888235a8d268 R15: 0000000000000000
snd_pcm_hw_free sound/core/pcm_native.c:790 [inline]
snd_pcm_common_ioctl+0x12da/0x2990 sound/core/pcm_native.c:2919
snd_pcm_ioctl+0x6d/0xa0 sound/core/pcm_native.c:2998
vfs_ioctl fs/ioctl.c:46 [inline]
file_ioctl fs/ioctl.c:500 [inline]
do_vfs_ioctl+0x75a/0xff0 fs/ioctl.c:684
SYSC_ioctl fs/ioctl.c:701 [inline]
SyS_ioctl+0x7f/0xb0 fs/ioctl.c:692
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x4450e9
RSP: 002b:00007ffe56ed3b98 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00000000004450e9
RDX: 0000000000000000 RSI: 0000000000004112 RDI: 0000000000000004
RBP: 0000000000007469 R08: 00000000004002e0 R09: 00000000004002e0
R10: 000000000000000f R11: 0000000000000246 R12: 0000000000402200
R13: 0000000000402290 R14: 0000000000000000 R15: 0000000000000000
Kernel Offset: disabled
Rebooting in 86400 seconds..


---
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 syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches
Reply all
Reply to author
Forward
0 new messages