From: syzbot <syzbot+090d23ddbd5cd185c2e0@syzkaller.appspotmail.com>
To: andrii@kernel.org, ast@kernel.org, bpf@vger.kernel.org,
daniel@iogearbox.net, davem@davemloft.net, dsahern@kernel.org,
edumazet@google.com, john.fastabend@gmail.com, kafai@fb.com,
kgraul@linux.ibm.com, kpsingh@kernel.org, kuba@kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com, songliubraving@fb.com,
syzkaller-bugs@googlegroups.com, yhs@fb.com,
yoshfuji@linux-ipv6.org
Subject: Re: [syzbot] BUG: unable to handle kernel NULL pointer dereference in __tcp_transmit_skb
Date: Thu, 24 Mar 2022 01:10:14 -0700 [thread overview]
Message-ID: <000000000000392f6005daf26000@google.com> (raw)
In-Reply-To: <000000000000acf1e405daebb7c7@google.com>
syzbot has bisected this issue to:
commit f2f2325ec79970807012dfc9e716cdbb02d9b574
Author: Eric Dumazet <edumazet@google.com>
Date: Fri Feb 4 20:15:46 2022 +0000
ip6mr: ip6mr_sk_done() can exit early in common cases
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=16299d7b700000
start commit: 36c2e31ad25b net: geneve: add missing netlink policy and s..
git tree: net-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=15299d7b700000
console output: https://syzkaller.appspot.com/x/log.txt?x=11299d7b700000
kernel config: https://syzkaller.appspot.com/x/.config?x=4a15e2288cf165c9
dashboard link: https://syzkaller.appspot.com/bug?extid=090d23ddbd5cd185c2e0
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=171eadbd700000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12cacda3700000
Reported-by: syzbot+090d23ddbd5cd185c2e0@syzkaller.appspotmail.com
Fixes: f2f2325ec799 ("ip6mr: ip6mr_sk_done() can exit early in common cases")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2022-03-24 8:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-24 0:13 [syzbot] BUG: unable to handle kernel NULL pointer dereference in __tcp_transmit_skb syzbot
2022-03-24 1:41 ` Eric Dumazet
2022-03-24 8:11 ` Karsten Graul
2022-03-24 8:10 ` 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=000000000000392f6005daf26000@google.com \
--to=syzbot+090d23ddbd5cd185c2e0@syzkaller.appspotmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kgraul@linux.ibm.com \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=songliubraving@fb.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=yhs@fb.com \
--cc=yoshfuji@linux-ipv6.org \
/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).