Hi Nikos, Just for reference, I've found a possible workaround for this problem. I could not reproduce the issue after I disabled in openssl eng_cryptodev.c all the algorithms and digests that were not available in the kernel. Probably, it can be just as simple to recompile the kernel with support for all the algorithms that cryptodev can offload, but I have not tested this.
> 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? [] This is visible only on the x86 but may give us a hint to the problem. Best regards, Cristian S. _______________________________________________ Cryptodev-linux-devel mailing list Cryptodev-linux-devel@gna.org https://mail.gna.org/listinfo/cryptodev-linux-devel
