[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <0000000000005b7456057a9abc57@google.com>
Date: Tue, 13 Nov 2018 23:18:07 -0800
From: syzbot <syzbot+2182db487a523d86bf34@...kaller.appspotmail.com>
To: linux-kernel@...r.kernel.org, syzkaller-bugs@...glegroups.com
Subject: kernel BUG at mm/slab.c:LINE! (3)
Hello,
syzbot found the following crash on:
HEAD commit: 3e536cff3424 net: phy: check if advertising is zero using ..
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=16f95b83400000
kernel config: https://syzkaller.appspot.com/x/.config?x=4a0a89f12ca9b0f5
dashboard link: https://syzkaller.appspot.com/bug?extid=2182db487a523d86bf34
compiler: gcc (GCC) 8.0.1 20180413 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=148d46d5400000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15c6a225400000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+2182db487a523d86bf34@...kaller.appspotmail.com
------------[ cut here ]------------
DEBUG_LOCKS_WARN_ON(depth >= MAX_LOCK_DEPTH)
------------[ cut here ]------------
kernel BUG at mm/slab.c:4425!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: -642842048 Comm: ksoftirqd/0 Not tainted 4.20.0-rc2+ #294
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
RIP: 0010:__check_heap_object+0xa7/0xb5 mm/slab.c:4450
Code: 48 c7 c7 15 73 12 89 e8 97 e3 0a 00 5d c3 41 8b 91 04 01 00 00 48 29
c7 48 39 d7 77 be 48 01 d0 48 29 c8 48 39 f0 72 b3 5d c3 <0f> 0b 48 c7 c7
15 73 12 89 e8 fd eb 0a 00 44 89 e9 48 c7 c7 d0 73
RSP: 0018:ffff8881d9af0030 EFLAGS: 00010093
RAX: 00000000000a57eb RBX: 1ffff1103b35e00d RCX: 000000000000000c
RDX: ffff8881d9af0240 RSI: 0000000000000002 RDI: ffff8881d9af01d8
RBP: ffff8881d9af0030 R08: ffff8881d9af0240 R09: ffff8881da970180
R10: 000000004afd69e7 R11: 0000000000000000 R12: ffff8881d9af01d8
R13: 0000000000000002 R14: ffffea000766bc00 R15: 0000000000000001
FS: 0000000000000000(0000) GS:ffff8881dae00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000068 CR3: 00000001bb987000 CR4: 00000000001406f0
Call Trace:
Modules linked in:
---[ end trace 1c9eb38e9e38ee03 ]---
RIP: 0010:__check_heap_object+0xa7/0xb5 mm/slab.c:4450
Code: 48 c7 c7 15 73 12 89 e8 97 e3 0a 00 5d c3 41 8b 91 04 01 00 00 48 29
c7 48 39 d7 77 be 48 01 d0 48 29 c8 48 39 f0 72 b3 5d c3 <0f> 0b 48 c7 c7
15 73 12 89 e8 fd eb 0a 00 44 89 e9 48 c7 c7 d0 73
RSP: 0018:ffff8881d9af0030 EFLAGS: 00010093
RAX: 00000000000a57eb RBX: 1ffff1103b35e00d RCX: 000000000000000c
RDX: ffff8881d9af0240 RSI: 0000000000000002 RDI: ffff8881d9af01d8
RBP: ffff8881d9af0030 R08: ffff8881d9af0240 R09: ffff8881da970180
R10: 000000004afd69e7 R11: 0000000000000000 R12: ffff8881d9af01d8
R13: 0000000000000002 R14: ffffea000766bc00 R15: 0000000000000001
FS: 0000000000000000(0000) GS:ffff8881dae00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000068 CR3: 00000001bb987000 CR4: 00000000001406f0
---
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 syzkaller@...glegroups.com.
syzbot will keep track of this bug report. See:
https://goo.gl/tpsmEJ#bug-status-tracking for how to communicate with
syzbot.
syzbot can test patches for this bug, for details see:
https://goo.gl/tpsmEJ#testing-patches
Powered by blists - more mailing lists