On Fri, Oct 09, 2020 at 09:48:30AM -0700, Jakub Kicinski wrote: > > Are you saying that if we set CRYPTO_TFM_REQ_MAY_BACKLOG we should > never see ENOSPC with a correctly functioning driver? Or do we need > to handle both errors, regardless? Correct, you will never see ENOSPC if you request MAY_BACKLOG. However, you must then ensure that when you get EBUSY that you stop issuing new requests until the Crypto API signals through the callback that you can start again. Cheers, -- Email: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
