From: David Miller <davem@davemloft.net>
To: herbert@gondor.apana.org.au
Cc: matorola@gmail.com, linux-crypto@vger.kernel.org,
sparclinux@vger.kernel.org, nicstange@gmail.com
Subject: Re: [crypto / sparc64] cryptomgr_test OOPS
Date: Fri, 06 May 2016 15:52:46 -0400 (EDT) [thread overview]
Message-ID: <20160506.155246.1005161410295236920.davem@davemloft.net> (raw)
In-Reply-To: <20160505084249.GA4971@gondor.apana.org.au>
From: Herbert Xu <herbert@gondor.apana.org.au>
Date: Thu, 5 May 2016 16:42:49 +0800
> Subject: crypto: testmgr - Use kmalloc memory for RSA input
>
> As akcipher uses an SG interface, you must not use vmalloc memory
> as input for it. This patch fixes testmgr to copy the vmalloc
> test vectors to kmalloc memory before running the test.
>
> This patch also removes a superfluous sg_virt call in do_test_rsa.
>
> Cc: <stable@vger.kernel.org>
> Reported-by: Anatoly Pugachev <matorola@gmail.com>
> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
I'm really surprised this didn't trigger on non-sparc64 systems, but
what do I know :-)
next prev parent reply other threads:[~2016-05-06 19:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-03 13:54 [crypto / sparc64] cryptomgr_test OOPS Anatoly Pugachev
2016-05-03 16:33 ` David Miller
2016-05-04 4:07 ` Herbert Xu
2016-05-04 14:49 ` Anatoly Pugachev
2016-05-05 8:42 ` Herbert Xu
2016-05-05 9:40 ` Anatoly Pugachev
2016-05-05 9:50 ` Herbert Xu
2016-05-05 16:17 ` Tadeusz Struk
2016-05-05 15:00 ` Tadeusz Struk
2016-05-05 15:31 ` Anatoly Pugachev
2016-05-05 15:52 ` John Paul Adrian Glaubitz
2016-05-05 16:09 ` Tadeusz Struk
2016-05-05 15:12 ` Anatoly Pugachev
2016-05-05 15:17 ` John Paul Adrian Glaubitz
2016-05-06 19:52 ` David Miller [this message]
2016-05-04 19:10 ` Anatoly Pugachev
2016-05-04 20:02 ` Tadeusz Struk
2016-05-04 20:51 ` David Miller
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=20160506.155246.1005161410295236920.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=matorola@gmail.com \
--cc=nicstange@gmail.com \
--cc=sparclinux@vger.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