crypto: seqiv - Handle EBUSY correctly

As it is seqiv only handles the special return value of EINPROGERSS,
which means that in all other cases it will free data related to the
request.

However, as the caller of seqiv may specify MAY_BACKLOG, we also need
to expect EBUSY and treat it in the same way.  Otherwise backlogged
requests will trigger a use-after-free.

Fixes: 0a270321dbf9 ("[CRYPTO] seqiv: Add Sequence Number IV Generator")
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>

diff --git a/crypto/seqiv.c b/crypto/seqiv.c
index 0899d527c2845b648bc1872daf5409ca1c4a8792..b1bcfe537daf11059aeef1c8aae7b04c2b05641a 100644 (file)
--- a/crypto/seqiv.c
+++ b/crypto/seqiv.c
@@ -23,7 +23,7 @@ static void seqiv_aead_encrypt_complete2(struct aead_request *req, int err)
        struct aead_request *subreq = aead_request_ctx(req);
        struct crypto_aead *geniv;
 
-       if (err == -EINPROGRESS)
+       if (err == -EINPROGRESS || err == -EBUSY)
                return;
 
        if (err)