From: syzbot <syzbot+a6abcf08bad8b18fd198@syzkaller.appspotmail.com>
To: ap420073@gmail.com, ardb@kernel.org, bp@alien8.de,
dave.hansen@linux.intel.com, davem@davemloft.net,
herbert@gondor.apana.org.au, hpa@zytor.com,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
mingo@redhat.com, syzkaller-bugs@googlegroups.com,
tglx@linutronix.de, x86@kernel.org
Subject: Re: [syzbot] [crypto?] general protection fault in __aria_aesni_avx_gfni_crypt_16way
Date: Tue, 16 May 2023 11:08:28 -0700 [thread overview]
Message-ID: <00000000000057f58705fbd375a3@google.com> (raw)
In-Reply-To: <CAMj1kXH8B6dmt0LVVyyorAzrKmkD2uFZ-5r4w0kMTYKbhqSPMA@mail.gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+a6abcf08bad8b18fd198@syzkaller.appspotmail.com
Tested on:
commit: d5253ed2 crypto: x86/aria - Use 16 byte alignment for ..
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/ardb/linux.git crypto-aria-x86-fix
console output: https://syzkaller.appspot.com/x/log.txt?x=17fed781280000
kernel config: https://syzkaller.appspot.com/x/.config?x=8bc832f563d8bf38
dashboard link: https://syzkaller.appspot.com/bug?extid=a6abcf08bad8b18fd198
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: i386
Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.
prev parent reply other threads:[~2023-05-16 18:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-08 7:53 [syzbot] [crypto?] general protection fault in __aria_aesni_avx_gfni_crypt_16way syzbot
2023-05-15 3:09 ` syzbot
2023-05-15 5:57 ` Herbert Xu
2023-05-16 17:48 ` Ard Biesheuvel
2023-05-16 18:08 ` 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=00000000000057f58705fbd375a3@google.com \
--to=syzbot+a6abcf08bad8b18fd198@syzkaller.appspotmail.com \
--cc=ap420073@gmail.com \
--cc=ardb@kernel.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=hpa@zytor.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).