Received: by 2002:a05:6a10:af89:0:0:0:0 with SMTP id iu9csp1451238pxb; Wed, 12 Jan 2022 15:18:36 -0800 (PST) X-Google-Smtp-Source: ABdhPJwXmXM6RLIQEZ4Hg9EMHlIMw+hT3qLg12x81jOGBHDnaaPpYy7ofQBOkUaxj7E3DernVwiY X-Received: by 2002:a17:90b:4d92:: with SMTP id oj18mr11583754pjb.226.1642029516533; Wed, 12 Jan 2022 15:18:36 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1642029516; cv=none; d=google.com; s=arc-20160816; b=mEn281BvglLCJFt77FLhkwKhUIUIw1POwBsd8lHpEmoqCdLp15+BolTAZn2sQeqOZU 3BtBeKyLRZVKVPz4UALFWUgpXt8mmI2pPnkx4b6bQMx3j2r2XygOww8uJ/bI7ZVKP55V LX9Mr7UaUbqCmDG0//Ty+6yzPubtpO9gjJHNdYE5f83iHAwcX1qiS00AoZ9mODwmlCtx 2VSeVcv8eu8G5MjybH46rV62uZo6KpW9o1K2vmGqlFhLdweAjPjMZBQfhS6nuNxBCJbw YYRZC+MmHsRmvm1/UY4BIFJ6WiaT2rwbRqVMOGELqw6fpoydtM8lzpl1vnb+8Xr28VDF Yt9Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=S++CHjPnmj13xcyW+yG6vfaZJ23Y5c8pQWNSstvjWzU=; b=T9L07sNe3v4hRZ6DD3FZ4gectDHqT8K02et80Bt1tMp/J7NJOLjoh22znVbThyxPiU Z0m1YiT7sRi+ydK0gL/9evIwo3LpQ2KWOYum5gZ6j7VXxbl3t7XU0Snm/Ux8Y6LkIVp1 xOBF0T720iQ8iQFPTUFxfQoV4wOVwUWwcTHtN1Yfs2OYaWnOrkYYMLcy5SWVhavWFNby 47+7zFiPUiWNzjHUEnxu6XFTyHDTnS7lFEPPLXt0P4UJpVQpHy48LpZ7W/bXeSH9Jx5q vZpHdtiX1sywrdWNoSs9bG3Vn51nfbmA6ZvGFWiiwXDLhvIvlzln+QNcy+q1vr8pyVaY yS3g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@zx2c4.com header.s=20210105 header.b=bfLbbHNq; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=zx2c4.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id n6si1352247plh.23.2022.01.12.15.18.24; Wed, 12 Jan 2022 15:18:36 -0800 (PST) Received-SPF: pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@zx2c4.com header.s=20210105 header.b=bfLbbHNq; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=zx2c4.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1347498AbiALOVG (ORCPT + 99 others); Wed, 12 Jan 2022 09:21:06 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45472 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S242457AbiALOVF (ORCPT ); Wed, 12 Jan 2022 09:21:05 -0500 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 1BB11C06173F; Wed, 12 Jan 2022 06:21:05 -0800 (PST) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id ACFFF616D7; Wed, 12 Jan 2022 14:21:04 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id B6698C36AEC; Wed, 12 Jan 2022 14:21:03 +0000 (UTC) Authentication-Results: smtp.kernel.org; dkim=pass (1024-bit key) header.d=zx2c4.com header.i=@zx2c4.com header.b="bfLbbHNq" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zx2c4.com; s=20210105; t=1641997261; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=S++CHjPnmj13xcyW+yG6vfaZJ23Y5c8pQWNSstvjWzU=; b=bfLbbHNqWevpKeE/A3I7hbUUMYqxqCJwkqknU7locWlkCBYeZUOabT6wCBE9yVLlMwby7v vOcHrPFTkYQevJoy33eURx1h/qwtz9vAWQH+BNEtogKJjMw+KBT1njVhZEJoVzKtOIj94K okZ8U90knigowm5TP6h6jz+QIFVBh7g= Received: by mail.zx2c4.com (ZX2C4 Mail Server) with ESMTPSA id 85583dfe (TLSv1.3:AEAD-AES256-GCM-SHA384:256:NO); Wed, 12 Jan 2022 14:21:01 +0000 (UTC) Received: by mail-yb1-f177.google.com with SMTP id n68so6795011ybg.6; Wed, 12 Jan 2022 06:21:00 -0800 (PST) X-Gm-Message-State: AOAM530LIJxIVi5xcYP0dbq7XQm5rBUQ0LG6+jyxa13umMbmO/oo9nQd +SVy7XiemE74ZI7nCEFEv5ytV9Iuz1RDF7hnRyw= X-Received: by 2002:a25:f90d:: with SMTP id q13mr13322228ybe.32.1641997259604; Wed, 12 Jan 2022 06:20:59 -0800 (PST) MIME-Version: 1.0 References: <20220112140137.728162-1-jforbes@fedoraproject.org> In-Reply-To: From: "Jason A. Donenfeld" Date: Wed, 12 Jan 2022 15:20:48 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v2] lib/crypto: add prompts back to crypto libraries To: Justin Forbes Cc: Ard Biesheuvel , Herbert Xu , "David S. Miller" , Greg Kroah-Hartman , Linux Crypto Mailing List , LKML , Linux Kbuild mailing list Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org On Wed, Jan 12, 2022 at 3:19 PM Justin Forbes wrote: > > On Wed, Jan 12, 2022 at 8:15 AM Jason A. Donenfeld wrote: > > > > On Wed, Jan 12, 2022 at 3:13 PM Ard Biesheuvel wrote: > > > > > > On Wed, 12 Jan 2022 at 15:12, Jason A. Donenfeld wrote: > > > > > > > > On Wed, Jan 12, 2022 at 3:08 PM Ard Biesheuvel wrote: > > > > > > > > > > On Wed, 12 Jan 2022 at 15:08, Jason A. Donenfeld wrote: > > > > > > > > > > > > On Wed, Jan 12, 2022 at 3:06 PM Ard Biesheuvel wrote: > > > > > > > > > > > > > > On Wed, 12 Jan 2022 at 15:05, Jason A. Donenfeld wrote: > > > > > > > > > > > > > > > > This commit also needs this snippet: > > > > > > > > > > > > > > > > > > > > > > Why? > > > > > > > > > > > > So that the menu of crypto library options is inside of the library > > > > > > menu. Otherwise this will appear inside of the _root_ menu, which > > > > > > isn't what we want. > > > > > > > > > > Why not? I think that's fine. > > > > > > > > It's really not appropriate there. Look: > > > > > > > > - Justin vanilla: https://i.imgur.com/14UBpML.png > > > > - Justin + Jason: https://i.imgur.com/lDfZnma.png > > > > > > > > We really don't want another top level menu. We're not that important. > > > > Rather, crypto libraries are but one ordinary subset of ordinary > > > > libraries, just like how the build system does it too. > > > > > > I disagree. The root menu is a jumble of things already, and having > > > this one at the root is really not a problem. > > > > Should CRC routines also go into a submenu and be put at the root? > > What about other library functions? Library functions belong in the > > library submenu. We don't need our own top level submenu for this. The > > whole point of lib/crypto/ is that they're just boring library > > functions. Libraries! So, part of the libraries menu. > > Specifically in this menu, users were expecting to see it in the > Cryptographic API menu. I think having it in the main menu just below > this entry is much more appropriate than being buried under another > menu. Particularly if the goal is to get rid of the menu again all > together once we can audit the full set of deps on crypto libraries. The thing is, even once we get rid of the labels, part of detangling everything is going to involve moving the sourcing of those symbols into lib/Kconfig anyway. No use delaying the inevitable.