BUG: corrupted list in pm_qos_update_target

6 views
Skip to first unread message

syzbot

unread,
Apr 14, 2020, 7:14:11 AM4/14/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=12d7f0abe00000
kernel config: https://syzkaller.appspot.com/x/.config?x=457897b554d08537
dashboard link: https://syzkaller.appspot.com/bug?extid=33b44e0abdb8b999db3c
compiler: gcc (GCC) 9.0.0 20181231 (experimental)

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

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

gfs2: not a GFS2 filesystem
list_add corruption. prev->next should be next (ffffffff87d74c00), but was ffff8882162c1258. (prev=ffff8882162c1258).
------------[ cut here ]------------
kernel BUG at lib/list_debug.c:26!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
Modules linked in:
CPU: 1 PID: 13397 Comm: syz-executor.1 Not tainted 4.14.176-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
task: ffff888087c3e500 task.stack: ffff8880612f0000
RIP: 0010:__list_add_valid.cold+0x3a/0x3c lib/list_debug.c:26
RSP: 0018:ffff8880612f78d8 EFLAGS: 00010086
RAX: 0000000000000075 RBX: ffff8882162c1258 RCX: 0000000000000000
RDX: 0000000000018662 RSI: ffffffff81491390 RDI: ffffed100c25ef11
RBP: ffff8882162c1258 R08: 0000000000000075 R09: 0000000000000002
R10: ffff888087c3edd0 R11: ffff888087c3e500 R12: ffffffff87d74c00
R13: 000000000005dc00 R14: ffff8882162c1240 R15: ffff8882162c1240
FS: 00007fa25faa6700(0000) GS:ffff8880aeb00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b30625000 CR3: 00000000a445b000 CR4: 00000000001406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
__list_add include/linux/list.h:60 [inline]
list_add_tail include/linux/list.h:93 [inline]
plist_add+0x2a9/0x460 lib/plist.c:102
pm_qos_update_target+0x4bc/0x9a0 kernel/power/qos.c:300
pm_qos_add_request+0x21f/0x4f0 kernel/power/qos.c:459
snd_pcm_hw_params+0x13a0/0x19e0 sound/core/pcm_native.c:733
snd_pcm_kernel_ioctl+0xbd/0x200 sound/core/pcm_native.c:3023
snd_pcm_oss_change_params_locked+0x13ca/0x30a0 sound/core/oss/pcm_oss.c:959
snd_pcm_oss_make_ready_locked+0x99/0x110 sound/core/oss/pcm_oss.c:1184
snd_pcm_oss_write1 sound/core/oss/pcm_oss.c:1398 [inline]
snd_pcm_oss_write+0x342/0x730 sound/core/oss/pcm_oss.c:2776
__vfs_write+0xe4/0x630 fs/read_write.c:480
vfs_write+0x192/0x4e0 fs/read_write.c:544
SYSC_write fs/read_write.c:590 [inline]
SyS_write+0xf2/0x210 fs/read_write.c:582
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x42/0xb7
RIP: 0033:0x45c889
RSP: 002b:00007fa25faa5c78 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007fa25faa66d4 RCX: 000000000045c889
RDX: 0000000000000020 RSI: 0000000020000240 RDI: 0000000000000005
RBP: 000000000076bf00 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00000000ffffffff
R13: 0000000000000cba R14: 00000000004d8218 R15: 000000000076bf0c
Code: 0f 0b 48 89 f2 4c 89 e1 48 89 ee 48 c7 c7 80 58 e4 86 e8 56 bf 4a fe 0f 0b 48 89 f1 48 c7 c7 00 58 e4 86 4c 89 e6 e8 42 bf 4a fe <0f> 0b 48 89 ee 48 c7 c7 a0 59 e4 86 e8 31 bf 4a fe 0f 0b 4c 89
RIP: __list_add_valid.cold+0x3a/0x3c lib/list_debug.c:26 RSP: ffff8880612f78d8
---[ end trace 2d11a88684e513d4 ]---


---
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

unread,
Aug 12, 2020, 7:14:11 AM8/12/20
to syzkaller...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages