From: Dmitry Vyukov <dvyukov@google.com>
To: syzbot <syzbot+245129539c27fecf099a@syzkaller.appspotmail.com>
Cc: andrii@kernel.org, andriin@fb.com, ast@kernel.org,
bpf@vger.kernel.org, clang-built-linux@googlegroups.com,
daniel@iogearbox.net, davem@davemloft.net, haoluo@google.com,
hawk@kernel.org, john.fastabend@gmail.com, jolsa@kernel.org,
kafai@fb.com, kpsingh@kernel.org, kuba@kernel.org,
linux-kernel@vger.kernel.org, llvm@lists.linux.dev,
martin.lau@linux.dev, memxor@gmail.com, nathan@kernel.org,
ndesaulniers@google.com, netdev@vger.kernel.org, sdf@google.com,
shanavas@crystalwater.ae, song@kernel.org, songliubraving@fb.com,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
trix@redhat.com, yhs@fb.com
Subject: Re: [syzbot] WARNING in bpf_check (3)
Date: Tue, 8 Nov 2022 14:53:34 -0800 [thread overview]
Message-ID: <CACT4Y+bnN7oZp2WJf+Jcx8+de1roOdLB=f_Zu+0H4UHEkfcO8A@mail.gmail.com> (raw)
In-Reply-To: <000000000000564bd705ecdf291f@google.com>
On Mon, 7 Nov 2022 at 02:48, syzbot
<syzbot+245129539c27fecf099a@syzkaller.appspotmail.com> wrote:
>
> syzbot suspects this issue was fixed by commit:
>
> commit 34dd3bad1a6f1dc7d18ee8dd53f1d31bffd2aee8
> Author: Alexei Starovoitov <ast@kernel.org>
> Date: Fri Sep 2 21:10:47 2022 +0000
>
> bpf: Relax the requirement to use preallocated hash maps in tracing progs.
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1232e176880000
> start commit: 506357871c18 Merge tag 'spi-fix-v6.0-rc4' of git://git.ker..
> git tree: upstream
> kernel config: https://syzkaller.appspot.com/x/.config?x=1b95a17a5bfb1521
> dashboard link: https://syzkaller.appspot.com/bug?extid=245129539c27fecf099a
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10940477080000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=177e8f43080000
>
> If the result looks correct, please mark the issue as fixed by replying with:
>
> #syz fix: bpf: Relax the requirement to use preallocated hash maps in tracing progs.
>
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection
Looks reasonable based on the subsystem and the patch:
#syz fix:
bpf: Relax the requirement to use preallocated hash maps in tracing progs.
prev parent reply other threads:[~2022-11-08 22:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-12 21:37 WARNING in bpf_check (3) syzbot
2022-11-07 10:48 ` [syzbot] " syzbot
2022-11-08 22:53 ` Dmitry Vyukov [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='CACT4Y+bnN7oZp2WJf+Jcx8+de1roOdLB=f_Zu+0H4UHEkfcO8A@mail.gmail.com' \
--to=dvyukov@google.com \
--cc=andrii@kernel.org \
--cc=andriin@fb.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=clang-built-linux@googlegroups.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=haoluo@google.com \
--cc=hawk@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=netdev@vger.kernel.org \
--cc=sdf@google.com \
--cc=shanavas@crystalwater.ae \
--cc=song@kernel.org \
--cc=songliubraving@fb.com \
--cc=syzbot+245129539c27fecf099a@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=trix@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 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).