From: Gao Xiang <hsiangkao@linux.alibaba.com>
To: syzbot <syzbot+bbb353775d51424087f2@syzkaller.appspotmail.com>,
chao@kernel.org, huyue2@coolpad.com, jefflexu@linux.alibaba.com,
linux-erofs@lists.ozlabs.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
xiang@kernel.org
Subject: Re: [syzbot] [erofs?] general protection fault in erofs_bread (2)
Date: Thu, 18 May 2023 02:15:12 +0800 [thread overview]
Message-ID: <85c61aae-6716-9936-1533-91624f70eefe@linux.alibaba.com> (raw)
In-Reply-To: <000000000000d03b0805fbe71d55@google.com>
On 2023/5/18 10:35, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: f1fcbaa18b28 Linux 6.4-rc2
> git tree: upstream
> console+strace: https://syzkaller.appspot.com/x/log.txt?x=114aa029280000
> kernel config: https://syzkaller.appspot.com/x/.config?x=6beb6ffe4f59ef2a
> dashboard link: https://syzkaller.appspot.com/bug?extid=bbb353775d51424087f2
> 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=13dd834e280000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=167ef106280000
>
> Downloadable assets:
> disk image: https://storage.googleapis.com/syzbot-assets/4adf207e9d5e/disk-f1fcbaa1.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/9e7cce92f611/vmlinux-f1fcbaa1.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/cfd911b80f89/bzImage-f1fcbaa1.xz
> mounted in repro: https://storage.googleapis.com/syzbot-assets/a2583fbaaf14/mount_2.gz
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+bbb353775d51424087f2@syzkaller.appspotmail.com
#syz test: git://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs.git fixes
next prev parent reply other threads:[~2023-05-17 18:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 17:35 syzbot
2023-05-17 18:15 ` Gao Xiang [this message]
2023-05-17 18:38 ` syzbot
2023-05-18 0:06 ` syzbot
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=85c61aae-6716-9936-1533-91624f70eefe@linux.alibaba.com \
--to=hsiangkao@linux.alibaba.com \
--cc=chao@kernel.org \
--cc=huyue2@coolpad.com \
--cc=jefflexu@linux.alibaba.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+bbb353775d51424087f2@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=xiang@kernel.org \
/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®