From: Christian Brauner <brauner@kernel.org>
To: syzbot <syzbot+c84b326736ee471158dc@syzkaller.appspotmail.com>,
syzbot <syzbot+729f1325904c82acd601@syzkaller.appspotmail.com>
Cc: bpf@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [kernel?] Internal error in should_fail_ex
Date: Tue, 16 May 2023 14:32:03 +0200 [thread overview]
Message-ID: <20230516-saftig-einbog-ef2981f0dec2@brauner> (raw)
In-Reply-To: <000000000000bff72505fbcd1f74@google.com> <000000000000bc152005fbcd1fa2@google.com>
On Tue, May 16, 2023 at 03:35:03AM -0700, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 457391b03803 Linux 6.3
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=15671fa2280000
> kernel config: https://syzkaller.appspot.com/x/.config?x=385e197a58ca4afe
> dashboard link: https://syzkaller.appspot.com/bug?extid=c84b326736ee471158dc
> compiler: arm-linux-gnueabi-gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
> userspace arch: arm
>
> Unfortunately, I don't have any reproducer for this issue yet.
>
> Downloadable assets:
> disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/c35b5b2731d2/non_bootable_disk-457391b0.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/2a1bf3bafeb6/vmlinux-457391b0.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/21f1e3b4a5a9/zImage-457391b0.xz
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+c84b326736ee471158dc@syzkaller.appspotmail.com
On Tue, May 16, 2023 at 03:35:02AM -0700, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 457391b03803 Linux 6.3
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=134e0b01280000
> kernel config: https://syzkaller.appspot.com/x/.config?x=385e197a58ca4afe
> dashboard link: https://syzkaller.appspot.com/bug?extid=729f1325904c82acd601
> compiler: arm-linux-gnueabi-gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
> userspace arch: arm
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=118f964e280000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16f6e776280000
>
> Downloadable assets:
> disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/c35b5b2731d2/non_bootable_disk-457391b0.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/2a1bf3bafeb6/vmlinux-457391b0.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/21f1e3b4a5a9/zImage-457391b0.xz
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+729f1325904c82acd601@syzkaller.appspotmail.com
Not complaining but why am I blessed with an explicit Cc on this?
next prev parent reply other threads:[~2023-05-16 12:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-16 10:35 syzbot
2023-05-16 10:35 ` [syzbot] [kernel?] Internal error in __zone_watermark_ok syzbot
2023-05-16 12:32 ` Christian Brauner [this message]
2023-05-16 17:23 ` [syzbot] [kernel?] Internal error in should_fail_ex 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=20230516-saftig-einbog-ef2981f0dec2@brauner \
--to=brauner@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+729f1325904c82acd601@syzkaller.appspotmail.com \
--cc=syzbot+c84b326736ee471158dc@syzkaller.appspotmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome