From: syzbot <syzbot+94c6d316eec8a68cc993@syzkaller.appspotmail.com>
To: brauner@kernel.org, davem@davemloft.net, dsahern@kernel.org,
edumazet@google.com, horms@kernel.org, jack@suse.cz,
kent.overstreet@linux.dev, kuba@kernel.org,
linux-bcachefs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com, syzkaller-bugs@googlegroups.com,
viro@zeniv.linux.org.uk
Subject: [syzbot] [net?] [bcachefs?] general protection fault in ipv6_get_saddr_eval
Date: Mon, 10 Feb 2025 00:29:29 -0800 [thread overview]
Message-ID: <67a9b8e9.050a0220.3d72c.004c.GAE@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 69b8923f5003 Merge tag 'for-linus-6.14-ofs4' of git://git...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=15912eb0580000
kernel config: https://syzkaller.appspot.com/x/.config?x=57ab43c279fa614d
dashboard link: https://syzkaller.appspot.com/bug?extid=94c6d316eec8a68cc993
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=169983df980000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/ea84ac864e92/disk-69b8923f.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/6a465997b4e0/vmlinux-69b8923f.xz
kernel image: https://storage.googleapis.com/syzbot-assets/d72b67b2bd15/bzImage-69b8923f.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/0073f7fa8a9c/mount_0.gz
The issue was bisected to:
commit 14152654805256d760315ec24e414363bfa19a06
Author: Kent Overstreet <kent.overstreet@linux.dev>
Date: Mon Nov 25 05:21:27 2024 +0000
bcachefs: Bad btree roots are now autofix
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13505df8580000
final oops: https://syzkaller.appspot.com/x/report.txt?x=10d05df8580000
console output: https://syzkaller.appspot.com/x/log.txt?x=17505df8580000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+94c6d316eec8a68cc993@syzkaller.appspotmail.com
Fixes: 141526548052 ("bcachefs: Bad btree roots are now autofix")
Oops: general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] PREEMPT SMP KASAN PTI
KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]
CPU: 0 UID: 0 PID: 12 Comm: kworker/u8:1 Not tainted 6.13.0-syzkaller-09793-g69b8923f5003 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 12/27/2024
Workqueue: ipv6_addrconf addrconf_dad_work
RIP: 0010:ipv6_get_saddr_eval+0x511/0xf50 net/ipv6/addrconf.c:1666
Code: e8 03 42 80 3c 28 00 74 08 4c 89 f7 e8 98 a9 97 f7 48 89 6c 24 08 4d 8b 2e 4c 89 e8 48 c1 e8 03 48 b9 00 00 00 00 00 fc ff df <80> 3c 08 00 74 08 4c 89 ef e8 71 a9 97 f7 41 be e0 00 00 00 4d 03
RSP: 0018:ffffc900001168b8 EFLAGS: 00010246
RAX: 0000000000000000 RBX: ffff888024f99e40 RCX: dffffc0000000000
RDX: ffff88805fc0dc00 RSI: ffffffff8fdb28c0 RDI: ffffc900001169e8
RBP: 0000000000000006 R08: 0000000000000005 R09: ffffffff8a8bbc59
R10: 000000000000000b R11: ffff88801c285a00 R12: ffffc90000116a40
R13: 0000000000000000 R14: ffff88805fc0dd38 R15: 0000000000000006
FS: 0000000000000000(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fa3ddba7bac CR3: 0000000024428000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
__ipv6_dev_get_saddr+0x1d3/0x4b0 net/ipv6/addrconf.c:1753
ipv6_dev_get_saddr+0x555/0xc10 net/ipv6/addrconf.c:1889
ip6_route_get_saddr include/net/ip6_route.h:147 [inline]
ip6_dst_lookup_tail+0xf18/0x14f0 net/ipv6/ip6_output.c:1133
ip6_dst_lookup_flow+0xb9/0x180 net/ipv6/ip6_output.c:1259
udp_tunnel6_dst_lookup+0x2be/0x520 net/ipv6/ip6_udp_tunnel.c:165
geneve6_xmit_skb drivers/net/geneve.c:950 [inline]
geneve_xmit+0xcf2/0x2cf0 drivers/net/geneve.c:1036
__netdev_start_xmit include/linux/netdevice.h:5144 [inline]
netdev_start_xmit include/linux/netdevice.h:5153 [inline]
xmit_one net/core/dev.c:3735 [inline]
dev_hard_start_xmit+0x27a/0x7d0 net/core/dev.c:3751
__dev_queue_xmit+0x1b73/0x3f50 net/core/dev.c:4584
dev_queue_xmit include/linux/netdevice.h:3305 [inline]
neigh_hh_output include/net/neighbour.h:523 [inline]
neigh_output include/net/neighbour.h:537 [inline]
ip6_finish_output2+0x1263/0x1780 net/ipv6/ip6_output.c:141
ip6_finish_output+0x41e/0x840 net/ipv6/ip6_output.c:226
NF_HOOK+0x9e/0x430 include/linux/netfilter.h:314
mld_sendpack+0x843/0xdb0 net/ipv6/mcast.c:1862
ipv6_mc_dad_complete+0x88/0x490 net/ipv6/mcast.c:2288
addrconf_dad_completed+0x712/0xcd0 net/ipv6/addrconf.c:4336
addrconf_dad_work+0xdbc/0x16a0
process_one_work kernel/workqueue.c:3236 [inline]
process_scheduled_works+0xa66/0x1840 kernel/workqueue.c:3317
worker_thread+0x870/0xd30 kernel/workqueue.c:3398
kthread+0x7a9/0x920 kernel/kthread.c:464
ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:148
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:ipv6_get_saddr_eval+0x511/0xf50 net/ipv6/addrconf.c:1666
Code: e8 03 42 80 3c 28 00 74 08 4c 89 f7 e8 98 a9 97 f7 48 89 6c 24 08 4d 8b 2e 4c 89 e8 48 c1 e8 03 48 b9 00 00 00 00 00 fc ff df <80> 3c 08 00 74 08 4c 89 ef e8 71 a9 97 f7 41 be e0 00 00 00 4d 03
RSP: 0018:ffffc900001168b8 EFLAGS: 00010246
RAX: 0000000000000000 RBX: ffff888024f99e40 RCX: dffffc0000000000
RDX: ffff88805fc0dc00 RSI: ffffffff8fdb28c0 RDI: ffffc900001169e8
RBP: 0000000000000006 R08: 0000000000000005 R09: ffffffff8a8bbc59
R10: 000000000000000b R11: ffff88801c285a00 R12: ffffc90000116a40
R13: 0000000000000000 R14: ffff88805fc0dd38 R15: 0000000000000006
FS: 0000000000000000(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fa3ddba7bac CR3: 0000000024428000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
0: e8 03 42 80 3c call 0x3c804208
5: 28 00 sub %al,(%rax)
7: 74 08 je 0x11
9: 4c 89 f7 mov %r14,%rdi
c: e8 98 a9 97 f7 call 0xf797a9a9
11: 48 89 6c 24 08 mov %rbp,0x8(%rsp)
16: 4d 8b 2e mov (%r14),%r13
19: 4c 89 e8 mov %r13,%rax
1c: 48 c1 e8 03 shr $0x3,%rax
20: 48 b9 00 00 00 00 00 movabs $0xdffffc0000000000,%rcx
27: fc ff df
* 2a: 80 3c 08 00 cmpb $0x0,(%rax,%rcx,1) <-- trapping instruction
2e: 74 08 je 0x38
30: 4c 89 ef mov %r13,%rdi
33: e8 71 a9 97 f7 call 0xf797a9a9
38: 41 be e0 00 00 00 mov $0xe0,%r14d
3e: 4d rex.WRB
3f: 03 .byte 0x3
---
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.
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup
reply other threads:[~2025-02-10 8:29 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=67a9b8e9.050a0220.3d72c.004c.GAE@google.com \
--to=syzbot+94c6d316eec8a68cc993@syzkaller.appspotmail.com \
--cc=brauner@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jack@suse.cz \
--cc=kent.overstreet@linux.dev \
--cc=kuba@kernel.org \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.