From: syzbot <syzbot+8ce4113dadc4789fac74@syzkaller.appspotmail.com>
To: andrii@kernel.org, andriin@fb.com, ast@kernel.org,
bpf@vger.kernel.org, corbet@lwn.net, daniel@iogearbox.net,
davem@davemloft.net, dsahern@gmail.com, dvyukov@google.com,
eric.dumazet@gmail.com, hawk@kernel.org,
john.fastabend@gmail.com, kafai@fb.com, kpsingh@kernel.org,
kuba@kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com, songliubraving@fb.com,
syzkaller-bugs@googlegroups.com, toke@redhat.com, yhs@fb.com
Subject: Re: [syzbot] WARNING in bpf_warn_invalid_xdp_action
Date: Thu, 10 Feb 2022 01:29:05 -0800 [thread overview]
Message-ID: <000000000000e238bf05d7a69450@google.com> (raw)
In-Reply-To: <000000000000a16ad7059cbcbe43@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=10d50baa700000
start commit: b3c8e0de473e Merge branch '40GbE' of git://git.kernel.org/..
git tree: net
kernel config: https://syzkaller.appspot.com/x/.config?x=1a86c22260afac2f
dashboard link: https://syzkaller.appspot.com/bug?extid=8ce4113dadc4789fac74
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=113c8a3bb00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16eb4307b00000
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
next prev parent reply other threads:[~2022-02-10 9:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-22 16:09 WARNING in bpf_warn_invalid_xdp_action syzbot
2020-01-22 21:01 ` syzbot
2020-01-22 21:38 ` Eric Dumazet
2020-01-23 6:19 ` Dmitry Vyukov
2022-02-10 9:29 ` syzbot [this message]
2022-02-16 15:33 ` [syzbot] " Dmitry Vyukov
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=000000000000e238bf05d7a69450@google.com \
--to=syzbot+8ce4113dadc4789fac74@syzkaller.appspotmail.com \
--cc=andrii@kernel.org \
--cc=andriin@fb.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=dvyukov@google.com \
--cc=eric.dumazet@gmail.com \
--cc=hawk@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.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=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.