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 17:06:25 -0700 [thread overview]
Message-ID: <0000000000004ea77505fbec93b6@google.com> (raw)
In-Reply-To: <000000000000d03b0805fbe71d55@google.com>
syzbot has bisected this issue to:
commit 6a318ccd7e083729cbcdbd174d7070f6b7d24130
Author: Jingbo Xu <jefflexu@linux.alibaba.com>
Date: Fri Apr 7 22:28:08 2023 +0000
erofs: enable long extended attribute name prefixes
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=159afed9280000
start commit: f1fcbaa18b28 Linux 6.4-rc2
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=179afed9280000
console output: https://syzkaller.appspot.com/x/log.txt?x=139afed9280000
kernel config: https://syzkaller.appspot.com/x/.config?x=6beb6ffe4f59ef2a
dashboard link: https://syzkaller.appspot.com/bug?extid=bbb353775d51424087f2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13dd834e280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=167ef106280000
Reported-by: syzbot+bbb353775d51424087f2@syzkaller.appspotmail.com
Fixes: 6a318ccd7e08 ("erofs: enable long extended attribute name prefixes")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2023-05-18 0:06 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
2023-05-18 0:06 ` syzbot [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=0000000000004ea77505fbec93b6@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox