linux_dsm_epyc7002/drivers/nfc/s3fwrn5
Eric Biggers 877b5691f2 crypto: shash - remove shash_desc::flags
The flags field in 'struct shash_desc' never actually does anything.
The only ostensibly supported flag is CRYPTO_TFM_REQ_MAY_SLEEP.
However, no shash algorithm ever sleeps, making this flag a no-op.

With this being the case, inevitably some users who can't sleep wrongly
pass MAY_SLEEP.  These would all need to be fixed if any shash algorithm
actually started sleeping.  For example, the shash_ahash_*() functions,
which wrap a shash algorithm with the ahash API, pass through MAY_SLEEP
from the ahash API to the shash API.  However, the shash functions are
called under kmap_atomic(), so actually they're assumed to never sleep.

Even if it turns out that some users do need preemption points while
hashing large buffers, we could easily provide a helper function
crypto_shash_update_large() which divides the data into smaller chunks
and calls crypto_shash_update() and cond_resched() for each chunk.  It's
not necessary to have a flag in 'struct shash_desc', nor is it necessary
to make individual shash algorithms aware of this at all.

Therefore, remove shash_desc::flags, and document that the
crypto_shash_*() functions can be called from any context.

Signed-off-by: Eric Biggers <ebiggers@google.com>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
2019-04-25 15:38:12 +08:00
..
core.c nfc: s3fwrn5: constify s3fwrn5_phy_ops structures 2015-12-20 18:32:39 +01:00
firmware.c crypto: shash - remove shash_desc::flags 2019-04-25 15:38:12 +08:00
firmware.h
i2c.c nfc: s3fwrn5: constify i2c_device_id 2017-11-06 00:56:56 +01:00
Kconfig nfc: s3fwrn5: Make NFC_S3FWRN5 select CRYPTO 2015-10-07 01:41:45 +02:00
Makefile
nci.c NFC: nci: rename nci_prop_ops to nci_driver_ops 2015-10-25 20:28:59 +01:00
nci.h NFC: nci: rename nci_prop_ops to nci_driver_ops 2015-10-25 20:28:59 +01:00
s3fwrn5.h nfc: s3fwrn5: constify s3fwrn5_phy_ops structures 2015-12-20 18:32:39 +01:00