|
|
|
Re: crypto_ahash_setkey | |
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] | |
On Wed, Nov 23, 2011 at 12:07 PM, Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> wrote: > On Wed, Nov 23, 2011 at 11:08:29AM +0200, Kasatkin, Dmitry wrote: >> >> Yes. I know that.... >> Work queue also uses WQ_NON_REENTRANT, so it should not be any races, >> and it should be possible to call crypto_ahash_setkey() without any problems. >> Ok... I found it out.. There is no magic here. For some reason work_task is called on different CPUs simultaneously. What is the purpose of WQ_NON_REENTRANT flag then? - Dmitry >> This problem happens on 64 bit kernel. >> It does not happen on my QEMU 32 bit kernel, >> >> I will do some more tests... > > Which particular hmac(sha1) implementation are you using? > > Cheers, > -- > Email: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> > Home Page: http://gondor.apana.org.au/~herbert/ > PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt > -- To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html