From: syzbot <syzbot+e3f8d4df1e1981a97abb@syzkaller.appspotmail.com>
To: andrii@kernel.org, ast@kernel.org, bpf@vger.kernel.org,
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,
song@kernel.org, songliubraving@fb.com,
syzkaller-bugs@googlegroups.com, trix@redhat.com, yhs@fb.com
Subject: Re: [syzbot] WARNING in check_map_prog_compatibility
Date: Fri, 04 Nov 2022 15:50:23 -0700 [thread overview]
Message-ID: <0000000000002227cf05ecace68c@google.com> (raw)
In-Reply-To: <0000000000009da4c705dcb87735@google.com>
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=1599d319880000
start commit: 200e340f2196 Merge tag 'pull-work.dcache' of git://git.ker..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=1b664fba5e66c4bf
dashboard link: https://syzkaller.appspot.com/bug?extid=e3f8d4df1e1981a97abb
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=165415a7080000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1716f705080000
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
next prev parent reply other threads:[~2022-11-04 22:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-15 21:55 [syzbot] WARNING in check_map_prog_compatibility syzbot
2022-11-04 22:50 ` syzbot [this message]
2022-11-04 23:05 ` Andrii Nakryiko
2023-02-02 23:06 ` syzbot
2023-02-03 5:07 ` 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=0000000000002227cf05ecace68c@google.com \
--to=syzbot+e3f8d4df1e1981a97abb@syzkaller.appspotmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--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=song@kernel.org \
--cc=songliubraving@fb.com \
--cc=syzkaller-bugs@googlegroups.com \
--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 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.