From: syzbot <syzbot+b97d20ed568ce0951a06@syzkaller.appspotmail.com>
To: andrii@kernel.org, ast@kernel.org, bpf@vger.kernel.org,
daniel@iogearbox.net, haoluo@google.com,
john.fastabend@gmail.com, jolsa@kernel.org, kpsingh@kernel.org,
kuba@kernel.org, linux-kernel@vger.kernel.org,
martin.lau@linux.dev, netdev@vger.kernel.org, sdf@google.com,
song@kernel.org, syzkaller-bugs@googlegroups.com, yhs@fb.com,
yonghong.song@linux.dev
Subject: Re: [syzbot] [bpf?] WARNING in bpf_mprog_pos_before
Date: Tue, 26 Sep 2023 14:38:26 -0700 [thread overview]
Message-ID: <00000000000022eedd060649e522@google.com> (raw)
In-Reply-To: <0000000000002c6cf80606492f14@google.com>
syzbot has bisected this issue to:
commit e420bed025071a623d2720a92bc2245c84757ecb
Author: Daniel Borkmann <daniel@iogearbox.net>
Date: Wed Jul 19 14:08:52 2023 +0000
bpf: Add fd-based tcx multi-prog infra with link support
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=116ab4b6680000
start commit: a59addacf899 drivers/net: process the result of hdlc_open(..
git tree: net
final oops: https://syzkaller.appspot.com/x/report.txt?x=136ab4b6680000
console output: https://syzkaller.appspot.com/x/log.txt?x=156ab4b6680000
kernel config: https://syzkaller.appspot.com/x/.config?x=d594086f139d167
dashboard link: https://syzkaller.appspot.com/bug?extid=b97d20ed568ce0951a06
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10dc3946680000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=107f4e1e680000
Reported-by: syzbot+b97d20ed568ce0951a06@syzkaller.appspotmail.com
Fixes: e420bed02507 ("bpf: Add fd-based tcx multi-prog infra with link support")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2023-09-26 21:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-26 20:47 [syzbot] [bpf?] WARNING in bpf_mprog_pos_before syzbot
2023-09-26 21:38 ` 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=00000000000022eedd060649e522@google.com \
--to=syzbot+b97d20ed568ce0951a06@syzkaller.appspotmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=netdev@vger.kernel.org \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=yhs@fb.com \
--cc=yonghong.song@linux.dev \
/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).