From: syzbot <syzbot+ded267b328e950a7c0c4@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: [syzbot] BUG: Address fc00:: on device lo is missing its host route.
Date: Fri, 07 Aug 2026 05:56:37 -0700 [thread overview]
Message-ID: <6a75d605.01d0871a.3a0d52.0047.GAE@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 364465ab19de Merge tag 'v7.2-rc6-smb3-server-fixes' of git..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=108402c6580000
kernel config: https://syzkaller.appspot.com/x/.config?x=acc0a882b963ae23
dashboard link: https://syzkaller.appspot.com/bug?extid=ded267b328e950a7c0c4
compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/a16108cc17bc/disk-364465ab.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/06f139add938/vmlinux-364465ab.xz
kernel image: https://storage.googleapis.com/syzbot-assets/7d4060230883/bzImage-364465ab.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+ded267b328e950a7c0c4@syzkaller.appspotmail.com
IPv6: BUG: Address fc00:: on device lo is missing its host route.
bond9: (slave ip6gretap1): link status up, enabling it in 0 ms
bond9: (slave ip6gretap1): failed to get link speed/duplex
bond9: (slave ip6gretap1): link status up, enabling it in 0 ms
bond9: (slave ip6gretap1): failed to get link speed/duplex
bond9: (slave ip6gretap1): link status up, enabling it in 0 ms
bond9: (slave ip6gretap1): failed to get link speed/duplex
net_ratelimit: 80 callbacks suppressed
bond9: (slave ip6gretap1): link status up, enabling it in 0 ms
bond9: (slave ip6gretap1): failed to get link speed/duplex
bond9: (slave ip6gretap1): link status up, enabling it in 0 ms
bond9: (slave ip6gretap1): failed to get link speed/duplex
---
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.
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
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:[~2026-08-07 12:56 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=6a75d605.01d0871a.3a0d52.0047.GAE@google.com \
--to=syzbot+ded267b328e950a7c0c4@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--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 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.