From: syzbot <syzbot+79fd1ab62b382be6f337@syzkaller.appspotmail.com>
To: andrii@kernel.org, ast@kernel.org, bpf@vger.kernel.org,
daniel@iogearbox.net, davem@davemloft.net, hawk@kernel.org,
john.fastabend@gmail.com, kafai@fb.com, kpsingh@kernel.org,
kuba@kernel.org, linux-kernel@vger.kernel.org,
lorenzo@kernel.org, netdev@vger.kernel.org,
songliubraving@fb.com, syzkaller-bugs@googlegroups.com,
toke@redhat.com, yhs@fb.com
Subject: Re: [syzbot] WARNING in bpf_prog_test_run_xdp
Date: Wed, 02 Feb 2022 22:15:13 -0800 [thread overview]
Message-ID: <0000000000009fe31405d7170e81@google.com> (raw)
In-Reply-To: <00000000000061d7eb05d7057144@google.com>
syzbot has bisected this issue to:
commit 1c194998252469cad00a08bd9ef0b99fd255c260
Author: Lorenzo Bianconi <lorenzo@kernel.org>
Date: Fri Jan 21 10:09:58 2022 +0000
bpf: introduce frags support to bpf_prog_test_run_xdp()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=16d81634700000
start commit: 000fe940e51f sfc: The size of the RX recycle ring should b..
git tree: net-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=15d81634700000
console output: https://syzkaller.appspot.com/x/log.txt?x=11d81634700000
kernel config: https://syzkaller.appspot.com/x/.config?x=e029d3b2ccd4c91a
dashboard link: https://syzkaller.appspot.com/bug?extid=79fd1ab62b382be6f337
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12a719cc700000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15851cec700000
Reported-by: syzbot+79fd1ab62b382be6f337@syzkaller.appspotmail.com
Fixes: 1c1949982524 ("bpf: introduce frags support to bpf_prog_test_run_xdp()")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2022-02-03 6:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-02 9:14 [syzbot] WARNING in bpf_prog_test_run_xdp syzbot
2022-02-02 23:12 ` syzbot
2022-02-03 6:15 ` syzbot [this message]
2022-03-05 4:12 ` 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=0000000000009fe31405d7170e81@google.com \
--to=syzbot+79fd1ab62b382be6f337@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=hawk@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=toke@redhat.com \
--cc=yhs@fb.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.