Hi Nikos, On 06/24/2014 11:42 AM, Nikos Mavrogiannopoulos wrote: > On Tue, Jun 24, 2014 at 6:29 PM, Joel Fernandes <jo...@ti.com> wrote: > >>>>> I'm using OpenSSL 1.0.1g with cryptodev-linux v1.6 loaded, when I run >>>>> the following: >>>> Do you use the cryptodev.c from the openssl project or the one >>>> included in cryptodev-linux? The shipped cryptodev.c in openssl had >>>> some bugs that are fixed in the cryptodev-linux version. >>> Hi Nikos, >>> I am using extras/eng_cryptodev.c from cryptodev-linux (copied to >>> OpenSSL and recompiled). >> Just adding, I always was using the eng_cryptodev.c from >> cryptodev-linux. Even with that, 50% of the scp and 100% of wget from an >> https server fails with just cryptodev-linux module loaded. openssl >> speed tests don't show any issues. The scp behavior specially is >> intermittent. > > So you have recompiled openssl as I understand. Did you run make check > after compiling openssl? If it does fail it may be an issue in your > accelerator and in that case you should use cryptodev-linux from git
Accelerators have been disabled and only cryptodev-linux is loaded to find these issues (with SW crypto options enabled in the kernel). > and try restricting the issue to the particular subsystem (e.g., > hash/cipher), and if possible figure the actual calls that failed. Sure, I'll try this. The problem with tracing to the actual calls that failed is that this is a corruption issue, not a call failure. The end result is some data got corrupted. I'll try using only cipher or sha somehow, or viceversa. Meanwhile, it does seem that this is fairly an obvious failure scenario and was hoping that you or someone else on the mailing list ran into the same thing when using scp, wget or libssl from userspace with cryptodev-linux loaded. Thanks for your help so far, Rebards, -Joel _______________________________________________ Cryptodev-linux-devel mailing list Cryptodev-linux-devel@gna.org https://mail.gna.org/listinfo/cryptodev-linux-devel
