On 9/27/2012 8:25 AM, Herbert Xu wrote:
On Wed, Sep 19, 2012 at 09:53:37PM +0300, Horia Geanta wrote:
Hi Herbert,
I know these patches come late and might not be included in 3.6.
But two of them are already sitting in cryptodev tree for some time.
(Don't know where my head was :/).
I'm hesitant to put these patches in at this stage. For the
That's understandable.
problems fixed by them do we have simpler fixes for 3.6? For
example, by reverting changesets that introduced the issue if
Reverting
e46e9a crypto: testmgr - add aead cbc aes hmac sha1,256,512 test vectors
(added in 3.6-rc2) would also do fine.
Of course, it would be added back in during 3.7 merge window, with the
other talitos-specific patches currently sitting in cryptodev.
What I'm trying to say here is that allowing the patch to go in 3.6
without all the other is incorrect. Sorry for not posting all of them as
a patchset.
Again, this patch (e46e9a) is not the culprit, it merely exposes the
deficiencies in the talitos driver.
AFAICT, these cases (zero assoc data, noncontiguous iv and assoc data)
have never been handled correctly in the driver.
it's a regression, or disabling the buggy functionality?
Don't think so, it's core functionality.
Thanks,
--
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
