On Wed, Dec 4, 2013 at 5:59 PM, Cristian Stoica <cristian.sto...@freescale.com> wrote: >> That's pretty strange as the issue is a crash on crypto_alloc_ahash() >> which only includes the hash name parameter. If you protect the >> cryptodev_cipher_init and cryptodev_hash_init with a mutex does it help? > [] > I've guarded both cryptodev_cipher_init and cryptodev_hash_init and the crash > remains with either of &ses_new->sem and &fcr->sem. > I could try something else if you have more insight. I don't see a reason why > crypto_larval_kill would get an empty list.
It could be an unrelated issue then that just happens to be uncovered at that point. Could you explain a bit the backtrace? Why does crypto_destroy_session is before the crypto_create_session? Could there be some unsafe interaction between them? regards, Nikos _______________________________________________ Cryptodev-linux-devel mailing list Cryptodev-linux-devel@gna.org https://mail.gna.org/listinfo/cryptodev-linux-devel
