From: syzbot <syzbot+e79818f5c12416aba9de@syzkaller.appspotmail.com>
To: alexander.deucher@amd.com, davem@davemloft.net,
dhowells@redhat.com, herbert@gondor.apana.org.au,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
mario.limonciello@amd.com, netdev@vger.kernel.org,
pabeni@redhat.com, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [crypto?] general protection fault in cryptd_hash_export
Date: Tue, 25 Jul 2023 05:57:22 -0700 [thread overview]
Message-ID: <0000000000009eae2406014f451d@google.com> (raw)
In-Reply-To: <0000000000000cb2c305fdeb8e30@google.com>
syzbot suspects this issue was fixed by commit:
commit 30c3d3b70aba2464ee8c91025e91428f92464077
Author: Mario Limonciello <mario.limonciello@amd.com>
Date: Tue May 30 16:57:59 2023 +0000
drm/amd: Disallow s0ix without BIOS support again
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13ad506ea80000
start commit: ded5c1a16ec6 Merge branch 'tools-ynl-gen-code-gen-improvem..
git tree: net-next
kernel config: https://syzkaller.appspot.com/x/.config?x=526f919910d4a671
dashboard link: https://syzkaller.appspot.com/bug?extid=e79818f5c12416aba9de
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13c6193b280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16c7a795280000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: drm/amd: Disallow s0ix without BIOS support again
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-07-25 12:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-12 9:43 [syzbot] [crypto?] general protection fault in cryptd_hash_export syzbot
2023-06-13 10:24 ` Herbert Xu
2023-06-14 12:04 ` David Howells
2023-06-14 14:54 ` David Howells
2023-06-14 22:42 ` syzbot
2023-07-25 12:57 ` syzbot [this message]
2023-07-25 12:58 ` Aleksandr Nogikh
2023-07-25 15:29 ` David Howells
2023-07-25 16:02 ` syzbot
2023-07-26 13:01 ` David Howells
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=0000000000009eae2406014f451d@google.com \
--to=syzbot+e79818f5c12416aba9de@syzkaller.appspotmail.com \
--cc=alexander.deucher@amd.com \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).