On Sat, 20 Aug 2005, Herbert Xu wrote: > Hi: > > Here is the patch that makes the crypto layer use a tfm flag instead of > in_atomic() to determine whether sleeping is allowed. I'll push this > into mm for testing. > > [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 <[EMAIL PROTECTED]>
Acked-by: James Morris <[EMAIL PROTECTED]> -- James Morris <[EMAIL PROTECTED]> - To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
