On 4/22/19, Sasha Levin sashal@kernel.org wrote:

Hi,

[This is an automated email]

This commit has been processed because it contains a -stable tag. The stable tag indicates that it's relevant for the following trees: all

The bot has tested the following trees: v5.0.9, v4.19.36, v4.14.113, v4.9.170, v4.4.178, v3.18.138.

v5.0.9: Build OK! v4.19.36: Build OK! v4.14.113: Failed to apply! Possible dependencies: fc340115ffb8 ("crypto: crypto4xx - properly set IV after de- and encrypt")

v4.9.170: Failed to apply! Possible dependencies: fc340115ffb8 ("crypto: crypto4xx - properly set IV after de- and encrypt")

v4.4.178: Failed to apply! Possible dependencies: fc340115ffb8 ("crypto: crypto4xx - properly set IV after de- and encrypt")

v3.18.138: Failed to apply! Possible dependencies: fc340115ffb8 ("crypto: crypto4xx - properly set IV after de- and encrypt")

How should we proceed with this patch?

I only added AES-CTR support around a year ago. https://kernel.googlesource.com/pub/scm/linux/kernel/git/stable/linux-stable... (so, this is another dependency)

In my opinion back-porting the patch to 4.14 and older would not do much since the mode is not available there. But, I'm glad that the patches got a bit of attention.

Cheers, Christian