From: syzbot <syzbot+ebd1a02208026c9e5722@syzkaller.appspotmail.com>
To: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com, syzkaller-bugs@googlegroups.com
Subject: [syzbot] BUG: corrupted list in dst_init
Date: Tue, 15 Nov 2022 20:40:33 -0800 [thread overview]
Message-ID: <000000000000b5c7dc05ed8f124c@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 1621b6eaebf7 Merge branch 'for-next/fixes' into for-kernelci
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
console output: https://syzkaller.appspot.com/x/log.txt?x=16c34435880000
kernel config: https://syzkaller.appspot.com/x/.config?x=606e57fd25c5c6cc
dashboard link: https://syzkaller.appspot.com/bug?extid=ebd1a02208026c9e5722
compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1508d766880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=114bd8e6880000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/82aa7741098d/disk-1621b6ea.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f6be08c4e4c2/vmlinux-1621b6ea.xz
kernel image: https://storage.googleapis.com/syzbot-assets/296b6946258a/Image-1621b6ea.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+ebd1a02208026c9e5722@syzkaller.appspotmail.com
list_add corruption. next->prev should be prev (ffff0000ce522608), but was 0000000000000000. (next=ffff0000cde85e00).
------------[ cut here ]------------
kernel BUG at lib/list_debug.c:29!
Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 3036 Comm: kworker/1:4 Not tainted 6.1.0-rc4-syzkaller-31872-g1621b6eaebf7 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/30/2022
Workqueue: mld mld_ifc_work
pstate: 604000c5 (nZCv daIF +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : __list_add_valid+0x9c/0xb8 lib/list_debug.c:27
lr : __list_add_valid+0x9c/0xb8 lib/list_debug.c:27
sp : ffff800012bfba40
x29: ffff800012bfba40 x28: 00007bfdfe1edc60 x27: 0000000000000015
x26: ffff0000ce5225b0 x25: ffff0000c3d82d70 x24: ffff0000ce522000
x23: ffff0000cde85e00 x22: ffff0000c3f5cd80 x21: ffff0000ce522608
x20: 0000000000000000 x19: ffff0000ce5225b8 x18: 00000000000000c0
x17: 3830363232356563 x16: ffff80000db1a158 x15: ffff0000c4f44ec0
x14: 0000000000000000 x13: 00000000ffffffff x12: ffff0000c4f44ec0
x11: ff808000081c06c8 x10: 0000000000000000 x9 : 6e082120c18aba00
x8 : 6e082120c18aba00 x7 : ffff80000c01775c x6 : 0000000000000000
x5 : 0000000000000080 x4 : 0000000000000001 x3 : 0000000000000000
x2 : ffff0001fefddcc8 x1 : 0000000100000001 x0 : 0000000000000075
Call trace:
__list_add_valid+0x9c/0xb8 lib/list_debug.c:27
__list_add include/linux/list.h:69 [inline]
list_add include/linux/list.h:88 [inline]
ref_tracker_alloc+0x118/0x280 lib/ref_tracker.c:95
__netdev_tracker_alloc include/linux/netdevice.h:3995 [inline]
netdev_hold include/linux/netdevice.h:4024 [inline]
dst_init+0x98/0x17c net/core/dst.c:52
dst_alloc+0x118/0x158 net/core/dst.c:96
ip6_dst_alloc net/ipv6/route.c:344 [inline]
icmp6_dst_alloc+0x54/0x22c net/ipv6/route.c:3261
mld_sendpack+0x348/0x864 net/ipv6/mcast.c:1809
mld_send_cr+0x4e8/0x5a8 net/ipv6/mcast.c:2121
mld_ifc_work+0x38/0x290 net/ipv6/mcast.c:2653
process_one_work+0x2d8/0x504 kernel/workqueue.c:2289
worker_thread+0x340/0x610 kernel/workqueue.c:2436
kthread+0x12c/0x158 kernel/kthread.c:376
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:863
Code: b001b0e0 9132ac00 aa0803e1 94a8304b (d4210000)
---[ end trace 0000000000000000 ]---
---
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 syzkaller@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
reply other threads:[~2022-11-16 4:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=000000000000b5c7dc05ed8f124c@google.com \
--to=syzbot+ebd1a02208026c9e5722@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).