On Thu, May 03, 2007 at 04:08:29PM +0200, Martin Schiller (mschiller@xxxxxx) wrote: > > Hm, driver does not perform encryption in-place at all. > > Since we did not hear from AMD quite for a while, could you please > > remove src==dst check in geode_aes_crypt() and run tests again. If it > > is software protection against hardware bug, I doubt such hardware > > should be used at all... > > > > Removing the src==dst check solves the freeze problem, but the > encryption/decryption results are wrong: > > Encryption: > Should be: 69c4e0d86a7b0430d8cdb78070b4c55a > But is: c8a331ff8edd3db175e1545dbefb760b > > Decryption: > Should be: 00112233445566778899aabbccddeeff > But is: 69c4e0d86a7b0430d8cdb78070b4c55a (same as input) That means that hardware does not work when source and destination addresses are the same, roughly saying it will not work with majority cases of ipsec and dm-crypt. As a workaround one needs to allocate a buffer and copy there data and then encrypt/decrypt from buffer into destination. > Regards, > Martin > -- Evgeniy Polyakov - 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
