From: syzbot <syzbot+67f89551088ea1a6850e@syzkaller•appspotmail.com>
To: andrii@kernel•org, ast@kernel•org, bpf@vger•kernel.org,
daniel@iogearbox•net, davem@davemloft•net, fgheet255t@gmail•com,
hawk@kernel•org, john.fastabend@gmail•com, kafai@fb•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, toke@redhat•com, toke@toke•dk,
yhs@fb•com
Subject: Re: [syzbot] KASAN: use-after-free Read in veth_xdp_rcv
Date: Wed, 12 Jan 2022 10:07:06 -0800 [thread overview]
Message-ID: <0000000000000f890905d56670f5@google.com> (raw)
In-Reply-To: <000000000000c1524005cdeacc5f@google.com>
syzbot suspects this issue was fixed by commit:
commit 2cbad989033bff0256675c38f96f5faab852af4b
Author: Paolo Abeni <pabeni@redhat•com>
Date: Tue Nov 30 10:08:06 2021 +0000
bpf: Do not WARN in bpf_warn_invalid_xdp_action()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14e9e1ddb00000
start commit: 252c765bd764 riscv, bpf: Add BPF exception tables
git tree: bpf-next
kernel config: https://syzkaller.appspot.com/x/.config?x=f60548b4c38ae4a8
dashboard link: https://syzkaller.appspot.com/bug?extid=67f89551088ea1a6850e
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1797fcf2b00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10e71f9f300000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: bpf: Do not WARN in bpf_warn_invalid_xdp_action()
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2022-01-12 18:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-09 12:40 [syzbot] KASAN: use-after-free Read in veth_xdp_rcv syzbot
2021-10-11 23:47 ` Jakub Kicinski
2021-10-12 9:20 ` Paolo Abeni
2021-10-28 21:08 ` syzbot
2022-01-12 18:07 ` 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=0000000000000f890905d56670f5@google.com \
--to=syzbot+67f89551088ea1a6850e@syzkaller$(echo .)appspotmail.com \
--cc=andrii@kernel$(echo .)org \
--cc=ast@kernel$(echo .)org \
--cc=bpf@vger$(echo .)kernel.org \
--cc=daniel@iogearbox$(echo .)net \
--cc=davem@davemloft$(echo .)net \
--cc=fgheet255t@gmail$(echo .)com \
--cc=hawk@kernel$(echo .)org \
--cc=john.fastabend@gmail$(echo .)com \
--cc=kafai@fb$(echo .)com \
--cc=kpsingh@kernel$(echo .)org \
--cc=kuba@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=songliubraving@fb$(echo .)com \
--cc=syzkaller-bugs@googlegroups$(echo .)com \
--cc=toke@redhat$(echo .)com \
--cc=toke@toke$(echo .)dk \
--cc=yhs@fb$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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