[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250120191250.GA39025@sol.localdomain>
Date: Mon, 20 Jan 2025 11:12:50 -0800
From: Eric Biggers <ebiggers@...nel.org>
To: David Howells <dhowells@...hat.com>
Cc: Simon Horman <horms@...nel.org>,
Herbert Xu <herbert@...dor.apana.org.au>,
Chuck Lever <chuck.lever@...cle.com>,
Trond Myklebust <trond.myklebust@...merspace.com>,
"David S. Miller" <davem@...emloft.net>,
Marc Dionne <marc.dionne@...istor.com>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
Ard Biesheuvel <ardb@...nel.org>, linux-crypto@...r.kernel.org,
linux-afs@...ts.infradead.org, linux-nfs@...r.kernel.org,
linux-fsdevel@...r.kernel.org, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH 03/24] crypto: Add 'krb5enc' hash and cipher AEAD
algorithm
On Mon, Jan 20, 2025 at 06:59:40PM +0000, David Howells wrote:
> Eric Biggers <ebiggers@...nel.org> wrote:
>
> > Multiple requests in parallel, I think you mean? No, it doesn't, but it
> > should.
>
> Not so much. This bug is on the asynchronous path and not tested by my
> rxrpc/rxgk code which only exercises the synchronous path. I haven't tried to
> make that asynchronous yet. I presume testmgr also only tests the sync path.
>
> David
>
I'm not sure I understand your question. Users of the crypto API can exclude
asynchronous algorithms when selecting one, but the self-tests do not do that.
In any case, why would you need anything to do asynchronous at all here?
- Eric
Powered by blists - more mailing lists