From: Herbert Xu <herbert@gondor.apana.org.au>
Date: Fri, 29 Nov 2019 08:40:24 +0000 (+0800)
Subject: crypto: pcrypt - Do not clear MAY_SLEEP flag in original request
X-Git-Tag: v4.19.103~98
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=c90aa32df0c3d1fe8adbb346185cdbbaf9eff571;p=thirdparty%2Fkernel%2Fstable.git

crypto: pcrypt - Do not clear MAY_SLEEP flag in original request

commit e8d998264bffade3cfe0536559f712ab9058d654 upstream.

We should not be modifying the original request's MAY_SLEEP flag
upon completion.  It makes no sense to do so anyway.

Reported-by: Eric Biggers <ebiggers@kernel.org>
Fixes: 5068c7a883d1 ("crypto: pcrypt - Add pcrypt crypto...")
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Tested-by: Eric Biggers <ebiggers@kernel.org>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
---

diff --git a/crypto/pcrypt.c b/crypto/pcrypt.c
index 1348541da463a..85082574c5154 100644
--- a/crypto/pcrypt.c
+++ b/crypto/pcrypt.c
@@ -130,7 +130,6 @@ static void pcrypt_aead_done(struct crypto_async_request *areq, int err)
 	struct padata_priv *padata = pcrypt_request_padata(preq);
 
 	padata->info = err;
-	req->base.flags &= ~CRYPTO_TFM_REQ_MAY_SLEEP;
 
 	padata_do_serial(padata);
 }