WARNING in do_debug

4 views
Skip to first unread message

syzbot

unread,
Jul 22, 2019, 2:28:06 PM7/22/19
to syzkaller-a...@googlegroups.com
Hello,

syzbot found the following crash on:

HEAD commit: 8fe42840 Merge 4.9.141 into android-4.9
git tree: android-4.9
console output: https://syzkaller.appspot.com/x/log.txt?x=1340e120600000
kernel config: https://syzkaller.appspot.com/x/.config?x=22a5ba9f73b6da1d
dashboard link: https://syzkaller.appspot.com/bug?extid=bf9fad16c9279acab6c2
compiler: gcc (GCC) 8.0.1 20180413 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10ce3af0600000

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

audit: type=1400 audit(1563818476.411:8): avc: denied { associate } for
pid=2071 comm="syz-executor.3" name="syz3"
scontext=unconfined_u:object_r:unlabeled_t:s0
tcontext=system_u:object_r:unlabeled_t:s0 tclass=filesystem permissive=1
------------[ cut here ]------------
WARNING: CPU: 1 PID: 2309 at arch/x86/kernel/traps.c:758
do_debug+0x3dc/0x4d0 /arch/x86/kernel/traps.c:758
Kernel panic - not syncing: panic_on_warn set ...

CPU: 1 PID: 2309 Comm: syz-executor.4 Not tainted 4.9.141+ #1
ffff8801db712d68 ffffffff81b42e79 ffffffff82a38ce0 00000000ffffffff
ffffffff82a15a00 0000000000000001 0000000000000009 ffff8801db712e28
ffffffff813f7125 0000000041b58ab3 ffffffff82e2b62b ffffffff813f6f66
Call Trace:
<#DB> [ 46.789181] [<ffffffff81b42e79>] __dump_stack
/lib/dump_stack.c:15 [inline]
<#DB> [ 46.789181] [<ffffffff81b42e79>] dump_stack+0xc1/0x128
/lib/dump_stack.c:51
[<ffffffff813f7125>] panic+0x1bf/0x39f /kernel/panic.c:179
[<ffffffff813f7362>] __warn.cold.8+0x2f/0x2f /kernel/panic.c:542
[<ffffffff810dc02c>] warn_slowpath_null+0x2c/0x40 /kernel/panic.c:585
[<ffffffff81056fac>] do_debug+0x3dc/0x4d0 /arch/x86/kernel/traps.c:758
[<ffffffff828187a7>] debug+0x37/0x70 /arch/x86/entry/entry_64.S:940
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