From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753426AbdDKGfL (ORCPT ); Tue, 11 Apr 2017 02:35:11 -0400 Received: from conssluserg-01.nifty.com ([210.131.2.80]:52298 "EHLO conssluserg-01.nifty.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752488AbdDKGfI (ORCPT ); Tue, 11 Apr 2017 02:35:08 -0400 DKIM-Filter: OpenDKIM Filter v2.10.3 conssluserg-01.nifty.com v3B6Yj6o028162 X-Nifty-SrcIP: [209.85.161.181] MIME-Version: 1.0 In-Reply-To: <20170411051228.GA10951@gondor.apana.org.au> References: <20170411102119.102f4675@canb.auug.org.au> <20170411024215.GA10664@gondor.apana.org.au> <20170411150250.49996951@canb.auug.org.au> <20170411051228.GA10951@gondor.apana.org.au> From: Masahiro Yamada Date: Tue, 11 Apr 2017 15:34:43 +0900 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: linux-next: manual merge of the crypto tree with the kbuild tree To: Herbert Xu Cc: Stephen Rothwell , Linux-Next Mailing List , Linux Kernel Mailing List , Nicolas Dichtel Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Herbert, 2017-04-11 14:12 GMT+09:00 Herbert Xu : > On Tue, Apr 11, 2017 at 03:02:50PM +1000, Stephen Rothwell wrote: >> >> 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. > > Actually the kbuild patch just needs to be reverted. We should > not export CRYPTO_MAX_ALG_NAME at all. Each user-space interface > that uses it already has its own limit and should not refer to the > in-kernel value. CRYPTO_MAX_ALG_NAME is referenced from include/uapi/linux/cryptouser.h If you exporting CRYPTO_MAX_ALG_NAME is wrong, please move cryptouser.h out of the include/uapi directory. -- Best Regards Masahiro Yamada