Re: linux-next: manual merge of the crypto tree with the kbuild tree
From: Stephen Rothwell
Date: Tue Apr 11 2017 - 01:03:03 EST
Hi Herbert,
On Tue, 11 Apr 2017 10:42:15 +0800 Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> wrote:
>
> Actually the patch in the kbuild tree should be reverted because
> we have now increased the in-kernel length limit and this must not
> be directly exposed to user-space or it'll break compatibility.
So basically we need CRYPTO_MAX_ALG_NAME to be 64 in the exported
header but 128 in the kernel header? In which case the kbuild patch
needs to be changed not removed. Or the merge resolution needs to be
cleverer.
--
Cheers,
Stephen Rothwell