WARNING: ODEBUG bug in corrupted

6 views
Skip to first unread message

syzbot

unread,
Apr 14, 2019, 5:28:20 AM4/14/19
to syzkaller-a...@googlegroups.com
Hello,

syzbot found the following crash on:

HEAD commit: 9e790395 Merge 4.9.112 into android-4.9
git tree: android-4.9
console output: https://syzkaller.appspot.com/x/log.txt?x=13531ec2400000
kernel config: https://syzkaller.appspot.com/x/.config?x=426e5da9eb2ee17a
dashboard link: https://syzkaller.appspot.com/bug?extid=dc2404d8861c4265853b
compiler: gcc (GCC) 8.0.1 20180413 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12371578400000

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

IPVS: Creating netns size=2536 id=5
IPVS: Creating netns size=2536 id=6
IPVS: Creating netns size=2536 id=7
IPVS: Creating netns size=2536 id=8
------------[ cut here ]------------
WARNING: CPU: 1 PID: 9268 at lib/debugobjects.c:263
debug_print_object+0x181/0x210 lib/debugobjects.c:260
ODEBUG: free active (active state 0) object type: work_struct hint:
p9_read_work+0x0/0xac0 include/linux/workqueue.h:535
Kernel panic - not syncing: panic_on_warn set ...

CPU: 1 PID: 9268 Comm: syz-executor3 Not tainted 4.9.112-g9e79039 #7
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
ffff8801b23e7520 ffffffff81eb3249 ffffffff83c48980 00000000ffffffff
0000000000000000 0000000000000001 0000000000000107 ffff8801b23e75e0
ffffffff81421a55 0000000041b58ab3 ffffffff843bae78 ffffffff81421896
Call Trace:
[<ffffffff81eb3249>] __dump_stack lib/dump_stack.c:15 [inline]
[<ffffffff81eb3249>] dump_stack+0xc1/0x128 lib/dump_stack.c:51
[<ffffffff81421a55>] panic+0x1bf/0x3bc kernel/panic.c:179
[<ffffffff81f1b741>] ? debug_print_obje


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