From: syzbot <syzbot+f534bd500d914e34b59e@syzkaller.appspotmail.com>
To: andrii@kernel.org, ast@kernel.org, bpf@vger.kernel.org,
d.dulov@aladdin.ru, daniel@iogearbox.net, davem@davemloft.net,
edumazet@google.com, hawk@kernel.org, john.fastabend@gmail.com,
kuba@kernel.org, linux-kernel@vger.kernel.org,
lorenzo.bianconi@redhat.com, lorenzo@kernel.org,
netdev@vger.kernel.org, pabeni@redhat.com,
syzkaller-bugs@googlegroups.com, toke@redhat.com
Subject: Re: [syzbot] [bpf?] [net?] WARNING in __xdp_reg_mem_model
Date: Thu, 08 Aug 2024 11:20:02 -0700 [thread overview]
Message-ID: <0000000000004c081f061f3013d1@google.com> (raw)
In-Reply-To: <0000000000004cc3030616474b1e@google.com>
syzbot suspects this issue was fixed by commit:
commit 7e9f79428372c6eab92271390851be34ab26bfb4
Author: Daniil Dulov <d.dulov@aladdin.ru>
Date: Mon Jun 24 08:07:47 2024 +0000
xdp: Remove WARN() from __xdp_reg_mem_model()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10df4a5d980000
start commit: f99c5f563c17 Merge tag 'nf-24-03-21' of git://git.kernel.o..
git tree: net
kernel config: https://syzkaller.appspot.com/x/.config?x=6fb1be60a193d440
dashboard link: https://syzkaller.appspot.com/bug?extid=f534bd500d914e34b59e
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17ac600b180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1144b797180000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: xdp: Remove WARN() from __xdp_reg_mem_model()
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2024-08-08 18:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 9:15 [syzbot] [bpf?] [net?] WARNING in __xdp_reg_mem_model syzbot
2024-05-04 18:03 ` syzbot
2024-05-06 14:49 ` Lorenzo Bianconi
2024-08-08 18:20 ` 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=0000000000004c081f061f3013d1@google.com \
--to=syzbot+f534bd500d914e34b59e@syzkaller.appspotmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=d.dulov@aladdin.ru \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo.bianconi@redhat.com \
--cc=lorenzo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=toke@redhat.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 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).