From: Michael Ellerman <mpe@ellerman•id.au>
To: Ard Biesheuvel <ard.biesheuvel@linaro•org>
Cc: leo.barbosa@canonical•com,
Herbert Xu <herbert@gondor•apana.org.au>,
Stephan Mueller <smueller@chronox•de>,
nayna@linux•ibm.com, omosnacek@gmail•com,
Eric Biggers <ebiggers@kernel•org>,
marcelo.cerri@canonical•com, pfsmorigo@gmail•com,
"open list:HARDWARE RANDOM NUMBER GENERATOR CORE"
<linux-crypto@vger•kernel.org>,
leitao@debian•org, linuxppc-dev <linuxppc-dev@lists•ozlabs.org>,
Daniel Axtens <dja@axtens•net>
Subject: Re: [PATCH] crypto: vmx - fix copy-paste error in CTR mode
Date: Tue, 19 Mar 2019 11:52:55 +1100 [thread overview]
Message-ID: <87bm277kig.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <CAKv+Gu_w_d5AbkYu=fdK1ver97G4O_rqu9o9tNy_-zNaAOnkkA@mail.gmail.com>
Ard Biesheuvel <ard.biesheuvel@linaro•org> writes:
> On Mon, 18 Mar 2019 at 09:41, Michael Ellerman <mpe@ellerman•id.au> wrote:
...
>>
>> I don't understand how the crypto core chooses which crypto_alg to use,
>> but I didn't expect enabling the tests to change it?
>
> This is not entirely unexpected. Based on the tests, algos that are
> found to be broken are disregarded for further use, and you should see
> a warning in the kernel log about this.
Ah right that makes sense then. I wasn't looking at the kernel log, just
rerunning the kcapi reproducer. Thanks for clarifying.
cheers
next prev parent reply other threads:[~2019-03-19 0:54 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-15 2:09 [PATCH] crypto: vmx - fix copy-paste error in CTR mode Daniel Axtens
2019-03-15 2:24 ` Eric Biggers
2019-03-15 4:24 ` Daniel Axtens
2019-03-15 4:34 ` Eric Biggers
2019-03-15 5:23 ` Daniel Axtens
2019-04-10 7:02 ` Eric Biggers
2019-04-11 14:47 ` Daniel Axtens
2019-04-11 17:40 ` Nayna
2019-04-13 3:41 ` Michael Ellerman
2019-05-06 15:53 ` Eric Biggers
2019-05-13 0:59 ` Herbert Xu
2019-05-13 11:39 ` Michael Ellerman
2019-05-14 17:35 ` Daniel Axtens
2019-05-15 3:53 ` Herbert Xu
2019-05-15 6:36 ` Daniel Axtens
2019-05-16 2:12 ` Daniel Axtens
2019-05-16 2:56 ` Eric Biggers
2019-05-16 5:28 ` Daniel Axtens
2019-03-18 8:41 ` Michael Ellerman
2019-03-18 9:13 ` Ard Biesheuvel
2019-03-19 0:52 ` Michael Ellerman [this message]
2019-03-18 6:03 ` Michael Ellerman
2019-03-20 8:40 ` Ondrej Mosnáček
2019-03-22 13:04 ` Herbert Xu
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=87bm277kig.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman$(echo .)id.au \
--cc=ard.biesheuvel@linaro$(echo .)org \
--cc=dja@axtens$(echo .)net \
--cc=ebiggers@kernel$(echo .)org \
--cc=herbert@gondor$(echo .)apana.org.au \
--cc=leitao@debian$(echo .)org \
--cc=leo.barbosa@canonical$(echo .)com \
--cc=linux-crypto@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=marcelo.cerri@canonical$(echo .)com \
--cc=nayna@linux$(echo .)ibm.com \
--cc=omosnacek@gmail$(echo .)com \
--cc=pfsmorigo@gmail$(echo .)com \
--cc=smueller@chronox$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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