From: syzbot <syzbot+c298c9f0e46a3c86332b@syzkaller.appspotmail.com>
To: davem@davemloft.net, dsahern@kernel.org, edumazet@google.com,
fw@strlen.de, horms@kernel.org, kuba@kernel.org,
kuniyu@amazon.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, pabeni@redhat.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [net?] WARNING in gre_tap_xmit (2)
Date: Sat, 20 Apr 2024 11:35:04 -0700 [thread overview]
Message-ID: <0000000000007aa28106168b76c9@google.com> (raw)
In-Reply-To: <000000000000c6405606166fdc68@google.com>
syzbot has bisected this issue to:
commit 219eee9c0d16f1b754a8b85275854ab17df0850a
Author: Florian Westphal <fw@strlen.de>
Date: Fri Feb 16 11:36:57 2024 +0000
net: skbuff: add overflow debug check to pull/push helpers
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=167a954f180000
start commit: 443574b03387 riscv, bpf: Fix kfunc parameters incompatibil..
git tree: bpf
final oops: https://syzkaller.appspot.com/x/report.txt?x=157a954f180000
console output: https://syzkaller.appspot.com/x/log.txt?x=117a954f180000
kernel config: https://syzkaller.appspot.com/x/.config?x=6fb1be60a193d440
dashboard link: https://syzkaller.appspot.com/bug?extid=c298c9f0e46a3c86332b
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14a94f00980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15bce6ab180000
Reported-by: syzbot+c298c9f0e46a3c86332b@syzkaller.appspotmail.com
Fixes: 219eee9c0d16 ("net: skbuff: add overflow debug check to pull/push helpers")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2024-04-20 18:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-19 9:39 [syzbot] [net?] WARNING in gre_tap_xmit (2) syzbot
2024-04-19 10:10 ` Eric Dumazet
2024-04-19 17:22 ` Kuniyuki Iwashima
2024-04-19 10:24 ` syzbot
2024-04-20 18:35 ` syzbot [this message]
2024-04-22 16:11 ` Kuniyuki Iwashima
2024-04-23 3:28 ` syzbot
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=0000000000007aa28106168b76c9@google.com \
--to=syzbot+c298c9f0e46a3c86332b@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.com \
--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).