WARNING: ODEBUG bug in pm_qos_remove_request

5 views
Skip to first unread message

syzbot

unread,
Apr 22, 2020, 3:38:16 AM4/22/20
to syzkaller...@googlegroups.com
Hello,

syzbot found the following crash on:

HEAD commit: c10b57a5 Linux 4.14.176
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=17d73dc8100000
kernel config: https://syzkaller.appspot.com/x/.config?x=457897b554d08537
dashboard link: https://syzkaller.appspot.com/bug?extid=5dd3d6ac1864b40f1e87
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11245dbfe00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15e01dc8100000

IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+5dd3d6...@syzkaller.appspotmail.com

audit: type=1400 audit(1587540914.383:8): avc: denied { execmem } for pid=6335 comm="syz-executor147" scontext=system_u:system_r:kernel_t:s0 tcontext=system_u:system_r:kernel_t:s0 tclass=process permissive=1
ODEBUG: assert_init not available (active state 0) object type: timer_list hint: (null)
------------[ cut here ]------------
WARNING: CPU: 0 PID: 6342 at lib/debugobjects.c:287 debug_print_object.cold+0xa7/0xdb lib/debugobjects.c:287
Kernel panic - not syncing: panic_on_warn set ...

CPU: 0 PID: 6342 Comm: syz-executor147 Not tainted 4.14.176-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+0x13e/0x194 lib/dump_stack.c:58
panic+0x1f9/0x42d kernel/panic.c:183
__warn.cold+0x2f/0x30 kernel/panic.c:547
report_bug+0x20a/0x248 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:963
RIP: 0010:debug_print_object.cold+0xa7/0xdb lib/debugobjects.c:287
RSP: 0018:ffff888097ff79d0 EFLAGS: 00010082
RAX: 0000000000000061 RBX: 0000000000000005 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff86ac07e0 RDI: ffffed1012ffef30
RBP: ffffffff86abba60 R08: 0000000000000061 R09: 0000000000000000
R10: ffff888097a1ab80 R11: ffff888097a1a300 R12: 0000000000000000
R13: 0000000000000000 R14: 1ffff11012ffef44 R15: ffff888216294e30
debug_object_assert_init lib/debugobjects.c:656 [inline]
debug_object_assert_init+0x22f/0x300 lib/debugobjects.c:627
debug_timer_assert_init kernel/time/timer.c:707 [inline]
debug_assert_init kernel/time/timer.c:755 [inline]
del_timer+0x5d/0xe0 kernel/time/timer.c:1150
try_to_grab_pending+0x261/0x610 kernel/workqueue.c:1225
__cancel_work_timer+0x92/0x460 kernel/workqueue.c:2923
pm_qos_remove_request+0x5e/0x460 kernel/power/qos.c:538
snd_pcm_hw_free sound/core/pcm_native.c:790 [inline]
snd_pcm_common_ioctl+0xa6d/0x1bf0 sound/core/pcm_native.c:2914
snd_pcm_ioctl+0x6d/0xa0 sound/core/pcm_native.c:2993
vfs_ioctl fs/ioctl.c:46 [inline]
file_ioctl fs/ioctl.c:500 [inline]
do_vfs_ioctl+0x75a/0xfe0 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+0x42/0xb7
RIP: 0033:0x445109
RSP: 002b:00007ffead54b368 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 0000000000445109
RDX: 0000000000000000 RSI: 0000000000004112 RDI: 0000000000000004
RBP: 00000000006d0018 R08: 00000000004002e0 R09: 00000000004002e0
R10: 00000000004002e0 R11: 0000000000000246 R12: 00000000004022a0
R13: 0000000000402330 R14: 0000000000000000 R15: 0000000000000000
Kernel Offset: disabled
Rebooting in 86400 seconds..


---
This bug 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 bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot can test patches for this bug, for details see:
https://goo.gl/tpsmEJ#testing-patches
Reply all
Reply to author
Forward
0 new messages