From: syzbot <syzbot+05139c4039d0679e19ff@syzkaller.appspotmail.com>
To: Su.Chung@amd.com, alexander.deucher@amd.com, chao@kernel.org,
drosen@google.com, ebiggers@kernel.org, jaegeuk@kernel.org,
jun.lei@amd.com, krisman@collabora.com,
linux-f2fs-devel@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
su.chung@amd.com, sunpeng.li@amd.com,
syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk,
yuchao0@huawei.com
Subject: Re: general protection fault in utf8_casefold
Date: Thu, 08 Oct 2020 19:40:04 -0700 [thread overview]
Message-ID: <000000000000bb48fb05b133ddf5@google.com> (raw)
In-Reply-To: <00000000000085be6f05b12a1366@google.com>
syzbot has bisected this issue to:
commit 91db9311945f01901ddb9813ce11364de214a156
Author: Su Sung Chung <Su.Chung@amd.com>
Date: Mon Jul 8 15:31:39 2019 +0000
drm/amd/display: refactor gpio to allocate hw_container in constructor
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1012ee8b900000
start commit: c85fb28b Merge tag 'arm64-fixes' of git://git.kernel.org/p..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=1212ee8b900000
console output: https://syzkaller.appspot.com/x/log.txt?x=1412ee8b900000
kernel config: https://syzkaller.appspot.com/x/.config?x=de7f697da23057c7
dashboard link: https://syzkaller.appspot.com/bug?extid=05139c4039d0679e19ff
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12316e00500000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16e80420500000
Reported-by: syzbot+05139c4039d0679e19ff@syzkaller.appspotmail.com
Fixes: 91db9311945f ("drm/amd/display: refactor gpio to allocate hw_container in constructor")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2020-10-09 2:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-08 14:59 general protection fault in utf8_casefold syzbot
2020-10-08 19:15 ` [PATCH] f2fs: reject CASEFOLD inode flag without casefold feature Eric Biggers
2020-10-08 19:26 ` Gabriel Krisman Bertazi
2020-10-09 1:30 ` Chao Yu
2020-10-09 2:40 ` 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=000000000000bb48fb05b133ddf5@google.com \
--to=syzbot+05139c4039d0679e19ff@syzkaller.appspotmail.com \
--cc=Su.Chung@amd.com \
--cc=alexander.deucher@amd.com \
--cc=chao@kernel.org \
--cc=drosen@google.com \
--cc=ebiggers@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=jun.lei@amd.com \
--cc=krisman@collabora.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sunpeng.li@amd.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
--cc=yuchao0@huawei.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;
as well as URLs for NNTP newsgroup(s).