From: syzbot <syzbot+88f4b1e6cf88da11f5cd@syzkaller.appspotmail.com>
To: Jiadong.Zhu@amd.com, alexander.deucher@amd.com,
davem@davemloft.net, dhowells@redhat.com,
herbert@gondor.apana.org.au, jiadong.zhu@amd.com,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, pabeni@redhat.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [crypto?] general protection fault in shash_ahash_update
Date: Wed, 19 Jul 2023 10:42:27 -0700 [thread overview]
Message-ID: <0000000000002361ee0600da8ec5@google.com> (raw)
In-Reply-To: <000000000000ada87505fe7cf809@google.com>
syzbot suspects this issue was fixed by commit:
commit 1dbcf770cc2d15baf8a1e8174d6fd014a68b45ca
Author: Jiadong Zhu <Jiadong.Zhu@amd.com>
Date: Wed May 24 03:42:19 2023 +0000
drm/amdgpu: Reset CP_VMID_PREEMPT after trailing fence signaled
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1622cafaa80000
start commit: 9a94d764e9bc Merge tag 'mlx5-updates-2023-06-16' of git://..
git tree: net-next
kernel config: https://syzkaller.appspot.com/x/.config?x=a4a7d74e6a7c3211
dashboard link: https://syzkaller.appspot.com/bug?extid=88f4b1e6cf88da11f5cd
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1152c4ff280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1307cbcf280000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: drm/amdgpu: Reset CP_VMID_PREEMPT after trailing fence signaled
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-07-19 17:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-19 15:13 [syzbot] [crypto?] general protection fault in shash_ahash_update syzbot
2023-06-19 18:39 ` syzbot
2023-06-19 21:45 ` David Howells
2023-06-19 22:09 ` syzbot
2023-06-20 7:43 ` David Howells
2023-06-20 8:09 ` syzbot
2023-07-25 15:18 ` David Howells
2023-07-19 17:42 ` syzbot [this message]
2023-07-19 17:56 ` Aleksandr Nogikh
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=0000000000002361ee0600da8ec5@google.com \
--to=syzbot+88f4b1e6cf88da11f5cd@syzkaller.appspotmail.com \
--cc=Jiadong.Zhu@amd.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=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).