From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753332AbdDKFC4 (ORCPT ); Tue, 11 Apr 2017 01:02:56 -0400 Received: from ozlabs.org ([103.22.144.67]:38739 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753060AbdDKFCx (ORCPT ); Tue, 11 Apr 2017 01:02:53 -0400 Date: Tue, 11 Apr 2017 15:02:50 +1000 From: Stephen Rothwell To: Herbert Xu Cc: Masahiro Yamada , Linux-Next Mailing List , Linux Kernel Mailing List , Nicolas Dichtel Subject: Re: linux-next: manual merge of the crypto tree with the kbuild tree Message-ID: <20170411150250.49996951@canb.auug.org.au> In-Reply-To: <20170411024215.GA10664@gondor.apana.org.au> References: <20170411102119.102f4675@canb.auug.org.au> <20170411024215.GA10664@gondor.apana.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Herbert, On Tue, 11 Apr 2017 10:42:15 +0800 Herbert Xu 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