Hello,
syzbot found the following issue on:
HEAD commit: 4ec71a9ec769 ANDROID: cpu/hotplug: call perf event through..
git tree: android13-5.15-lts
console+strace:
https://syzkaller.appspot.com/x/log.txt?x=14041b21880000
kernel config:
https://syzkaller.appspot.com/x/.config?x=5f64a7340a9acccc
dashboard link:
https://syzkaller.appspot.com/bug?extid=a6a3eb29e4bd79f252f6
compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro:
https://syzkaller.appspot.com/x/repro.syz?x=157ec4e5880000
C reproducer:
https://syzkaller.appspot.com/x/repro.c?x=1132a531880000
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/93b972e96678/disk-4ec71a9e.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/10d3ac64bada/vmlinux-4ec71a9e.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/70ae0159c6d1/bzImage-4ec71a9e.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+a6a3eb...@syzkaller.appspotmail.com
skbuff: skb_over_panic: text:ffffffff845d9324 len:76 put:20 head:ffff88810e53e400 data:ffff88810e53e440 tail:0x8c end:0x80 dev:syztnl1
------------[ cut here ]------------
kernel BUG at net/core/skbuff.c:113!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 423 Comm: kworker/0:2 Not tainted 5.15.74-syzkaller-00001-g4ec71a9ec769 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
Workqueue: ipv6_addrconf addrconf_dad_work
RIP: 0010:skb_panic+0x14c/0x150 net/core/skbuff.c:113
Code: c7 a0 70 be 85 48 8b 75 c0 48 8b 55 b8 8b 4d d4 44 8b 45 d0 4c 8b 4d c8 31 c0 53 41 56 41 55 41 54 e8 03 fe dc 00 48 83 c4 20 <0f> 0b 66 90 55 48 89 e5 41 57 41 56 41 55 41 54 53 48 83 ec 78 4c
RSP: 0018:ffffc9000033f8c8 EFLAGS: 00010282
RAX: 0000000000000086 RBX: ffff88810b756000 RCX: bea430fce5d36e00
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: ffffc9000033f910 R08: ffffffff815838e9 R09: ffffed103ee065e8
R10: ffffed103ee065e8 R11: 1ffff1103ee065e7 R12: ffff88810e53e440
R13: 000000000000008c R14: 0000000000000080 R15: dffffc0000000000
FS: 0000000000000000(0000) GS:ffff8881f7000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 000000010d1b0000 CR4: 00000000003506b0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
skb_over_panic net/core/skbuff.c:118 [inline]
skb_put+0x153/0x210 net/core/skbuff.c:2039
add_grhead net/ipv6/mcast.c:1855 [inline]
add_grec+0xf74/0x13d0 net/ipv6/mcast.c:1989
mld_send_initial_cr net/ipv6/mcast.c:2236 [inline]
ipv6_mc_dad_complete+0x246/0x5f0 net/ipv6/mcast.c:2247
addrconf_dad_completed+0x733/0xe20 net/ipv6/addrconf.c:4248
addrconf_dad_work+0xd8f/0x1680
process_one_work+0x6db/0xc00 kernel/workqueue.c:2313
worker_thread+0xb3e/0x1340 kernel/workqueue.c:2460
kthread+0x41c/0x500 kernel/kthread.c:319
ret_from_fork+0x1f/0x30
</TASK>
Modules linked in:
---[ end trace 7e3eaf38d94d6fae ]---
RIP: 0010:skb_panic+0x14c/0x150 net/core/skbuff.c:113
Code: c7 a0 70 be 85 48 8b 75 c0 48 8b 55 b8 8b 4d d4 44 8b 45 d0 4c 8b 4d c8 31 c0 53 41 56 41 55 41 54 e8 03 fe dc 00 48 83 c4 20 <0f> 0b 66 90 55 48 89 e5 41 57 41 56 41 55 41 54 53 48 83 ec 78 4c
RSP: 0018:ffffc9000033f8c8 EFLAGS: 00010282
RAX: 0000000000000086 RBX: ffff88810b756000 RCX: bea430fce5d36e00
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: ffffc9000033f910 R08: ffffffff815838e9 R09: ffffed103ee065e8
R10: ffffed103ee065e8 R11: 1ffff1103ee065e7 R12: ffff88810e53e440
R13: 000000000000008c R14: 0000000000000080 R15: dffffc0000000000
FS: 0000000000000000(0000) GS:ffff8881f7000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 000000000680f000 CR4: 00000000003506b0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
---
This report 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 issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches