| commit | 64baf3cfea974d2b9e671ccfdbc03e030ea5ebc6 | |
| author | Herbert Xu <herbert@gondor.apana.org.au> | |
| Fri, 2 Sep 2005 00:43:05 +0000 (1 17:43 -0700) | ||
| committer | David S. Miller <davem@davemloft.net> | |
| Fri, 2 Sep 2005 00:43:05 +0000 (1 17:43 -0700) | ||
| tree | 2bae23bf3d7378ba2d60be8aee6b0178d1d9c721 | treesnapshot (tar.gz zip) |
| parent | fb4f10ed50f01b0f953068456bfb6e2885921b01 | commitdiff |
[CRYPTO]: Added CRYPTO_TFM_REQ_MAY_SLEEP flag
The crypto layer currently uses in_atomic() to determine whether it is
allowed to sleep. This is incorrect since spin locks don't always cause
in_atomic() to return true.
Instead of that, this patch returns to an earlier idea of a per-tfm flag
which determines whether sleeping is allowed. Unlike the earlier version,
the default is to not allow sleeping. This ensures that no existing code
can break.
As usual, this flag may either be set through crypto_alloc_tfm(), or
just before a specific crypto operation.
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Signed-off-by: David S. Miller <davem@davemloft.net>
The crypto layer currently uses in_atomic() to determine whether it is
allowed to sleep. This is incorrect since spin locks don't always cause
in_atomic() to return true.
Instead of that, this patch returns to an earlier idea of a per-tfm flag
which determines whether sleeping is allowed. Unlike the earlier version,
the default is to not allow sleeping. This ensures that no existing code
can break.
As usual, this flag may either be set through crypto_alloc_tfm(), or
just before a specific crypto operation.
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Signed-off-by: David S. Miller <davem@davemloft.net>
| crypto/api.c | diffblobblamehistory | |
| crypto/cipher.c | diffblobblamehistory | |
| crypto/internal.h | diffblobblamehistory | |
| include/linux/crypto.h | diffblobblamehistory |