crypto: drop mask=CRYPTO_ALG_ASYNC from 'shash' tfm allocations

'shash' algorithms are always synchronous, so passing CRYPTO_ALG_ASYNC
in the mask to crypto_alloc_shash() has no effect.  Many users therefore
already don't pass it, but some still do.  This inconsistency can cause
confusion, especially since the way the 'mask' argument works is
somewhat counterintuitive.

Thus, just remove the unneeded CRYPTO_ALG_ASYNC flags.

This patch shouldn't change any actual behavior.

Signed-off-by: Eric Biggers <ebiggers@google.com>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>

1 files changed, 2 insertions, 3 deletions

diff --git a/fs/ubifs/auth.c b/fs/ubifs/auth.c
index 124e965a28b3..5bf5fd08879e 100644
--- a/fs/ubifs/auth.c
+++ b/fs/ubifs/auth.c
@@ -269,8 +269,7 @@ int ubifs_init_authentication(struct ubifs_info *c)
                 goto out;
         }
 
-        c->hash_tfm = crypto_alloc_shash(c->auth_hash_name, 0,
-                                         CRYPTO_ALG_ASYNC);
+        c->hash_tfm = crypto_alloc_shash(c->auth_hash_name, 0, 0);
         if (IS_ERR(c->hash_tfm)) {
                 err = PTR_ERR(c->hash_tfm);
                 ubifs_err(c, "Can not allocate %s: %d",
@@ -286,7 +285,7 @@ int ubifs_init_authentication(struct ubifs_info *c)
                 goto out_free_hash;
         }
 
-        c->hmac_tfm = crypto_alloc_shash(hmac_name, 0, CRYPTO_ALG_ASYNC);
+        c->hmac_tfm = crypto_alloc_shash(hmac_name, 0, 0);
         if (IS_ERR(c->hmac_tfm)) {
                 err = PTR_ERR(c->hmac_tfm);
                 ubifs_err(c, "Can not allocate %s: %d", hmac_name, err);