[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20200703133558.GX4332@42.do-not-panic.com>
Date: Fri, 3 Jul 2020 13:35:58 +0000
From: Luis Chamberlain <mcgrof@...nel.org>
To: Herbert Xu <herbert@...dor.apana.org.au>
Cc: Naresh Kamboju <naresh.kamboju@...aro.org>,
Eric Biggers <ebiggers@...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 Mailing List <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>,
Sachin Sant <sachinp@...ux.vnet.ibm.com>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
linuxppc-dev <linuxppc-dev@...ts.ozlabs.org>,
linux- stable <stable@...r.kernel.org>
Subject: Re: [v2 PATCH] crypto: af_alg - Fix regression on empty requests
On Thu, Jul 02, 2020 at 01:32:21PM +1000, Herbert Xu wrote:
> On Tue, Jun 30, 2020 at 02:18:11PM +0530, Naresh Kamboju wrote:
> >
> > Since we are on this subject,
> > LTP af_alg02 test case fails on stable 4.9 and stable 4.4
> > This is not a regression because the test case has been failing from
> > the beginning.
> >
> > Is this test case expected to fail on stable 4.9 and 4.4 ?
> > or any chance to fix this on these older branches ?
> >
> > Test output:
> > af_alg02.c:52: BROK: Timed out while reading from request socket.
> >
> > ref:
> > https://qa-reports.linaro.org/lkft/linux-stable-rc-4.9-oe/build/v4.9.228-191-g082e807235d7/testrun/2884917/suite/ltp-crypto-tests/test/af_alg02/history/
> > https://qa-reports.linaro.org/lkft/linux-stable-rc-4.9-oe/build/v4.9.228-191-g082e807235d7/testrun/2884606/suite/ltp-crypto-tests/test/af_alg02/log
>
> Actually this test really is broken.
FWIW the patch "umh: fix processed error when UMH_WAIT_PROC is used" was
dropped from linux-next for now as it was missing checking for signals.
I'll be open coding iall checks for each UMH_WAIT_PROC callers next. Its
not clear if this was the issue with this test case, but figured I'd let
you know.
Luis
Powered by blists - more mailing lists