From: syzbot <syzbot+0141c834e47059395621@syzkaller.appspotmail.com>
To: bpoirier@nvidia.com, davem@davemloft.net, dsahern@kernel.org,
edumazet@google.com, eric.dumazet@gmail.com, horms@kernel.org,
idosch@nvidia.com, kuba@kernel.org, kuniyu@google.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com, petrm@nvidia.com, razor@blackwall.org,
roopa@nvidia.com, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [net?] WARNING in ip6_mr_output
Date: Fri, 27 Jun 2025 22:14:02 -0700 [thread overview]
Message-ID: <685f7a1a.a70a0220.2f4de1.0007.GAE@google.com> (raw)
In-Reply-To: <685e86b3.a00a0220.129264.0003.GAE@google.com>
syzbot has bisected this issue to:
commit 96e8f5a9fe2d91b9f9eb8b45cc13ce1ca6a8af82
Author: Petr Machata <petrm@nvidia.com>
Date: Mon Jun 16 22:44:18 2025 +0000
net: ipv6: Add ip6_mr_output()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13bcfb70580000
start commit: 5d4809e25903 Add linux-next specific files for 20250620
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=107cfb70580000
console output: https://syzkaller.appspot.com/x/log.txt?x=17bcfb70580000
kernel config: https://syzkaller.appspot.com/x/.config?x=58afc4b78b52b7e3
dashboard link: https://syzkaller.appspot.com/bug?extid=0141c834e47059395621
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=138a2dd4580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=171c5b0c580000
Reported-by: syzbot+0141c834e47059395621@syzkaller.appspotmail.com
Fixes: 96e8f5a9fe2d ("net: ipv6: Add ip6_mr_output()")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2025-06-28 5:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-27 11:55 syzbot
2025-06-28 5:14 ` syzbot [this message]
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=685f7a1a.a70a0220.2f4de1.0007.GAE@google.com \
--to=syzbot+0141c834e47059395621@syzkaller.appspotmail.com \
--cc=bpoirier@nvidia.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=razor@blackwall.org \
--cc=roopa@nvidia.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
all inboxes | Powered by JetHome®