From: syzbot <syzbot+f3a497f02c389d86ef16@syzkaller.appspotmail.com>
To: davem@davemloft.net, edumazet@google.com, eric.dumazet@gmail.com,
horms@kernel.org, jeremy@azazel.net, jhs@mojatatu.com,
jiri@resnulli.us, kuba@kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, pabeni@redhat.com, pablo@netfilter.org,
syzkaller-bugs@googlegroups.com, tom@herbertland.com,
xiyou.wangcong@gmail.com
Subject: Re: [syzbot] [net?] WARNING in em_nbyte_match
Date: Fri, 21 Nov 2025 17:17:03 -0800 [thread overview]
Message-ID: <69210f0f.a70a0220.d98e3.0050.GAE@google.com> (raw)
In-Reply-To: <6920855a.a70a0220.2ea503.0058.GAE@google.com>
syzbot has bisected this issue to:
commit 66e4c8d950083df8e12981babca788e1635c92b6
Author: Eric Dumazet <edumazet@google.com>
Date: Tue May 10 03:57:39 2022 +0000
net: warn if transport header was not set
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15b34c2a580000
start commit: 8e621c9a3375 Merge tag 'net-6.18-rc7' of git://git.kernel...
git tree: net
final oops: https://syzkaller.appspot.com/x/report.txt?x=17b34c2a580000
console output: https://syzkaller.appspot.com/x/log.txt?x=13b34c2a580000
kernel config: https://syzkaller.appspot.com/x/.config?x=14b6a9313e132a6b
dashboard link: https://syzkaller.appspot.com/bug?extid=f3a497f02c389d86ef16
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15e83658580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=149b4484580000
Reported-by: syzbot+f3a497f02c389d86ef16@syzkaller.appspotmail.com
Fixes: 66e4c8d95008 ("net: warn if transport header was not set")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2025-11-22 1:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-21 15:29 [syzbot] [net?] WARNING in em_nbyte_match syzbot
2025-11-22 1:17 ` 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=69210f0f.a70a0220.d98e3.0050.GAE@google.com \
--to=syzbot+f3a497f02c389d86ef16@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=horms@kernel.org \
--cc=jeremy@azazel.net \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pablo@netfilter.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tom@herbertland.com \
--cc=xiyou.wangcong@gmail.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).