From: Daniel Borkmann <daniel@iogearbox.net>
To: syzbot <syzbot+33f36d0754d4c5c0e102@syzkaller.appspotmail.com>,
andrii@kernel.org, ast@kernel.org, bpf@vger.kernel.org,
davem@davemloft.net, hawk@kernel.org, john.fastabend@gmail.com,
kafai@fb.com, kpsingh@kernel.org, kuba@kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
songliubraving@fb.com, syzkaller-bugs@googlegroups.com,
yhs@fb.com
Subject: Re: [syzbot] general protection fault in bpf_skb_cgroup_id
Date: Fri, 17 Sep 2021 23:59:46 +0200 [thread overview]
Message-ID: <a0ad330c-3caa-5c56-3f1c-c600fe6dacbe@iogearbox.net> (raw)
In-Reply-To: <000000000000f152a305cc374d7b@google.com>
On 9/17/21 11:06 PM, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 2865ba82476a Merge git://git.kernel.org/pub/scm/linux/kern..
> git tree: bpf
> console output: https://syzkaller.appspot.com/x/log.txt?x=15089853300000
> kernel config: https://syzkaller.appspot.com/x/.config?x=c31c0936547df9ea
> dashboard link: https://syzkaller.appspot.com/bug?extid=33f36d0754d4c5c0e102
> compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14dbd7ed300000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1586f83b300000
>
> Bisection is inconclusive: the first bad commit could be any of:
>
> 0e6491b55970 bpf: Add oversize check before call kvcalloc()
> 2f1aaf3ea666 bpf, mm: Fix lockdep warning triggered by stack_map_get_build_id_offset()
> 8520e224f547 bpf, cgroups: Fix cgroup v2 fallback on v1/v2 mixed mode
> 3a029e1f3d6e selftests/bpf: Fix build of task_pt_regs test for arm64
> d8079d8026f8 bpf, selftests: Add cgroup v1 net_cls classid helpers
> 43d2b88c29f2 bpf, selftests: Add test case for mixed cgroup v1/v2
> 49ca6153208f bpf: Relicense disassembler as GPL-2.0-only OR BSD-2-Clause
> 2865ba82476a Merge git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=16b5ccdd300000
I'll take a look at the report.
Thanks,
Daniel
prev parent reply other threads:[~2021-09-17 21:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-17 21:06 syzbot
2021-09-17 21:59 ` Daniel Borkmann [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=a0ad330c-3caa-5c56-3f1c-c600fe6dacbe@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=hawk@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=syzbot+33f36d0754d4c5c0e102@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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
all inboxes | Powered by JetHome®