[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200623170217.GB150582@gmail.com>
Date: Tue, 23 Jun 2020 10:02:17 -0700
From: Eric Biggers <ebiggers@...nel.org>
To: Herbert Xu <herbert@...dor.apana.org.au>
Cc: Naresh Kamboju <naresh.kamboju@...aro.org>,
Luis Chamberlain <mcgrof@...nel.org>,
LTP List <ltp@...ts.linux.it>,
open list <linux-kernel@...r.kernel.org>,
linux-security-module@...r.kernel.org, keyrings@...r.kernel.org,
lkft-triage@...ts.linaro.org, linux-crypto@...r.kernel.org,
Jan Stancek <jstancek@...hat.com>, chrubis <chrubis@...e.cz>,
"Serge E. Hallyn" <serge@...lyn.com>,
James Morris <jmorris@...ei.org>,
Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>,
David Howells <dhowells@...hat.com>,
"David S. Miller" <davem@...emloft.net>
Subject: Re: LTP: crypto: af_alg02 regression on linux-next 20200621 tag
On Tue, Jun 23, 2020 at 04:40:56PM +1000, Herbert Xu wrote:
> On Tue, Jun 23, 2020 at 11:53:43AM +0530, Naresh Kamboju wrote:
> >
> > Thanks for the investigation.
> > After reverting, two test cases got PASS out of four reported failure cases.
> > ltp-crypto-tests:
> > * af_alg02 - still failing - Hung and time out
> > * af_alg05 - still failing - Hung and time out
> > ltp-syscalls-tests:
> > * keyctl07 - PASS
> > * request_key03 - PASS
> >
> > Please suggest the way to debug / fix the af_alg02 and af_alg05 failures.
>
> Did you clear the MSG_MORE flag in the final send(2) call before
> you call recv(2)?
>
The source code for the two failing AF_ALG tests is here:
https://github.com/linux-test-project/ltp/blob/master/testcases/kernel/crypto/af_alg02.c
https://github.com/linux-test-project/ltp/blob/master/testcases/kernel/crypto/af_alg05.c
They use read() and write(), not send() and recv().
af_alg02 uses read() to read from a "salsa20" request socket without writing
anything to it. It is expected that this returns 0, i.e. that behaves like
encrypting an empty message.
af_alg05 uses write() to write 15 bytes to a "cbc(aes-generic)" request socket,
then read() to read 15 bytes. It is expected that this fails with EINVAL, since
the length is not aligned to the AES block size (16 bytes).
- Eric
Powered by blists - more mailing lists