From: syzbot <syzbot+79fd1ab62b382be6f337@syzkaller.appspotmail.com>
To: andrii@kernel.org, ast@kernel.org, boris.ostrovsky@oracle.com,
bpf@vger.kernel.org, daniel@iogearbox.net, davem@davemloft.net,
hawk@kernel.org, jgross@suse.com, 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, roger.pau@citrix.com,
songliubraving@fb.com, syzkaller-bugs@googlegroups.com,
toke@redhat.com, yhs@fb.com
Subject: Re: [syzbot] WARNING in bpf_prog_test_run_xdp
Date: Fri, 04 Mar 2022 20:12:06 -0800 [thread overview]
Message-ID: <000000000000934ec105d970d589@google.com> (raw)
In-Reply-To: <00000000000061d7eb05d7057144@google.com>
syzbot suspects this issue was fixed by commit:
commit c8980fcb210851138cb34c9a8cb0cf0c09f07bf9
Author: Roger Pau Monne <roger.pau@citrix.com>
Date: Fri Jan 21 09:01:46 2022 +0000
xen/x2apic: enable x2apic mode when supported for HVM
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13b1991a700000
start commit: 000fe940e51f sfc: The size of the RX recycle ring should b..
git tree: net-next
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
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: xen/x2apic: enable x2apic mode when supported for HVM
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2022-03-05 4:23 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
2022-03-05 4:12 ` 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=000000000000934ec105d970d589@google.com \
--to=syzbot+79fd1ab62b382be6f337@syzkaller.appspotmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=boris.ostrovsky@oracle.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=hawk@kernel.org \
--cc=jgross@suse.com \
--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=roger.pau@citrix.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.