All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+bbb353775d51424087f2@syzkaller.appspotmail.com>
To: chao@kernel.org, hsiangkao@linux.alibaba.com, 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: Wed, 17 May 2023 11:38:26 -0700	[thread overview]
Message-ID: <0000000000004ef96f05fbe7fe6f@google.com> (raw)
In-Reply-To: <85c61aae-6716-9936-1533-91624f70eefe@linux.alibaba.com>

Hello,

syzbot has tested the proposed patch and the reproducer did not trigger any issue:

Reported-and-tested-by: syzbot+bbb353775d51424087f2@syzkaller.appspotmail.com

Tested on:

commit:         ae0bac79 erofs: avoid pcpubuf.c inclusion if CONFIG_ER..
git tree:       git://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs.git fixes
console output: https://syzkaller.appspot.com/x/log.txt?x=16793226280000
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

Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.

  reply	other threads:[~2023-05-17 18:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-17 17:35 [syzbot] [erofs?] general protection fault in erofs_bread (2) syzbot
2023-05-17 18:15 ` Gao Xiang
2023-05-17 18:38   ` syzbot [this message]
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=0000000000004ef96f05fbe7fe6f@google.com \
    --to=syzbot+bbb353775d51424087f2@syzkaller.appspotmail.com \
    --cc=chao@kernel.org \
    --cc=hsiangkao@linux.alibaba.com \
    --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=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 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.