From: syzbot <syzbot+319a9b09e5de1ecae1e1@syzkaller.appspotmail.com>
To: brauner@kernel.org
Cc: ast@kernel.org, brauner@kernel.org, daniel@iogearbox.net,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [kernel?] bpf-next test error: UBSAN: array-index-out-of-bounds in alloc_pid
Date: Mon, 03 Jul 2023 01:01:58 -0700 [thread overview]
Message-ID: <000000000000b359eb05ff9094f0@google.com> (raw)
In-Reply-To: <20230703-richten-ehren-5a4c9b042a23@brauner>
> On Mon, Jul 03, 2023 at 12:14:17AM -0700, syzbot wrote:
>> Hello,
>>
>> syzbot found the following issue on:
>>
>> HEAD commit: c20f9cef725b Merge branch 'libbpf: add netfilter link atta..
>> git tree: bpf-next
>> console output: https://syzkaller.appspot.com/x/log.txt?x=127adbfb280000
>> kernel config: https://syzkaller.appspot.com/x/.config?x=924167e3666ff54c
>> dashboard link: https://syzkaller.appspot.com/bug?extid=319a9b09e5de1ecae1e1
>> compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
>>
>> Downloadable assets:
>> disk image: https://storage.googleapis.com/syzbot-assets/bf9c9608a1e0/disk-c20f9cef.raw.xz
>> vmlinux: https://storage.googleapis.com/syzbot-assets/3bde4e994bd0/vmlinux-c20f9cef.xz
>> kernel image: https://storage.googleapis.com/syzbot-assets/5d80f8634183/bzImage-c20f9cef.xz
>>
>> IMPORTANT: if you fix the issue, please add the following tag to the commit:
>> Reported-by: syzbot+319a9b09e5de1ecae1e1@syzkaller.appspotmail.com
>
> #syz dup: [syzbot] [kernel?] net-next test error: UBSAN: array-index-out-of-bounds in alloc_pid
can't find the dup bug
next prev parent reply other threads:[~2023-07-03 8:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 7:14 [syzbot] [kernel?] bpf-next test error: UBSAN: array-index-out-of-bounds in alloc_pid syzbot
2023-07-03 8:00 ` Christian Brauner
2023-07-03 8:01 ` Christian Brauner
2023-07-03 8:01 ` syzbot [this message]
2023-07-03 8:25 ` Aleksandr Nogikh
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=000000000000b359eb05ff9094f0@google.com \
--to=syzbot+319a9b09e5de1ecae1e1@syzkaller.appspotmail.com \
--cc=ast@kernel.org \
--cc=brauner@kernel.org \
--cc=daniel@iogearbox.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.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.