Received: by 2002:a05:6358:53a8:b0:117:f937:c515 with SMTP id z40csp313124rwe; Fri, 14 Apr 2023 03:18:33 -0700 (PDT) X-Google-Smtp-Source: AKy350bn31mkSe5geTnL+zazNecf/SqwnTqv2cQ7UXZtuzb9b8zlZwUkRUUMaV5edXe+6cFU5tCv X-Received: by 2002:a05:6a21:339a:b0:cb:af96:9436 with SMTP id yy26-20020a056a21339a00b000cbaf969436mr1808673pzb.0.1681467513607; Fri, 14 Apr 2023 03:18:33 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1681467513; cv=none; d=google.com; s=arc-20160816; b=ORpWUJfxCYCHhmpka7z0KSfVuwhbCenCC/i8ky6RoseLn3sFD2D+U4B3uJPdeJ1Fph MjXnS+1yHEGWBJsJue7+QNpGyIjegS4HdEPkq8TR1gUg01xS4Zli03375lAsg9HhlQwH Y/yTD12wcpUrnOIbXnba3CnyVFIXb7ETmE+gECrznboxqpV9cc818F/SrPtYFFwNOxz0 Ky36Xnzl1y6cTi01ovf1v9e6K9T6D8e+TR0WZgjx6l2hzGsg67rPln4lyht7Bnu850P4 k4fY7GPMTXju0a3JMM4qOiatRxI+XjUpATtl0Pu1/ht9cgV08wZ0PUl4x9fbnQmMARPh oSfw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:message-id:date:content-id:mime-version:subject :cc:to:references:in-reply-to:from:organization:dkim-signature; bh=HGlU0PvOV1zf33jFs6Isk0h8BFNeNak/ejipOrEy1sk=; b=MAZzyjsbS5HEJvxApgXM4g9ci6M6pWraDpVT6tGsdoXaFnix136ORhCge/I9DNQtpc IvIzdVJXicaePo/RRUUIC2CQnGdlnergzMEBK1dyZ6xSorJfDO6HyFqjZUXuP9usnzXK fhvHyseH2qzK6ulOACmkSJhfu+fj50oQ/glSIvcI9r5e+4uVtxF1Zk6PXEyEASn58DH/ WZMdN9IcbPk4bfQI5WydhcByeGWmOBtn0jvE+OqMklxnTNbvifZ9VJdVAw6p+ltl0okU UMHV8NyPBZq3geg4kBwzE0X/LgJH5sN08ZAt8Tp+w0ZnvyLqY14xIaLGEb4Op03teBdp wePA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=BpyinE9L; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id v135-20020a63618d000000b0051b6edd4ec4si1606590pgb.99.2023.04.14.03.18.14; Fri, 14 Apr 2023 03:18:33 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=BpyinE9L; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229632AbjDNKSC (ORCPT + 99 others); Fri, 14 Apr 2023 06:18:02 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54546 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229734AbjDNKSC (ORCPT ); Fri, 14 Apr 2023 06:18:02 -0400 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C9D4990 for ; Fri, 14 Apr 2023 03:17:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1681467436; 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=HGlU0PvOV1zf33jFs6Isk0h8BFNeNak/ejipOrEy1sk=; b=BpyinE9LU5QpFZ6u3I30F5MBsHXCbX9IUx+uxNS9IIZf0QARmTULz4WBRggS4p32v1KpJ7 sY0cSZPVPyl5J5wB+DneidXgDTATpFUQO1le1Pf2BhbMqe79/bW4CMi8YSfWBe4N5gSA2C 4vbUZvNUwyVdaYJMpnu8AwazSNguLK8= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-589-n6LkH29JOM-7W2ZSpQRXPA-1; Fri, 14 Apr 2023 06:17:12 -0400 X-MC-Unique: n6LkH29JOM-7W2ZSpQRXPA-1 Received: from smtp.corp.redhat.com (int-mx09.intmail.prod.int.rdu2.redhat.com [10.11.54.9]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 9011A811E7C; Fri, 14 Apr 2023 10:17:11 +0000 (UTC) Received: from warthog.procyon.org.uk (unknown [10.33.36.5]) by smtp.corp.redhat.com (Postfix) with ESMTP id A7327492C14; Fri, 14 Apr 2023 10:17:10 +0000 (UTC) Organization: Red Hat UK Ltd. Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SI4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 3798903 From: David Howells In-Reply-To: References: <48886D84-1A04-4B07-A666-BB56684E759F@oracle.com> <380323.1681314997@warthog.procyon.org.uk> <1078650.1681394138@warthog.procyon.org.uk> <1235770.1681462057@warthog.procyon.org.uk> To: Herbert Xu Cc: dhowells@redhat.com, Chuck Lever III , Scott Mayhew , Ard Biesheuvel , Jeff Layton , Linux NFS Mailing List , "linux-crypto@vger.kernel.org" Subject: Re: Did the in-kernel Camellia or CMAC crypto implementation break? MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1239034.1681467430.1@warthog.procyon.org.uk> Date: Fri, 14 Apr 2023 11:17:10 +0100 Message-ID: <1239035.1681467430@warthog.procyon.org.uk> X-Scanned-By: MIMEDefang 3.1 on 10.11.54.9 X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_NONE,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org Herbert Xu wrote: > > Actually, I was wondering about that. I see that all the testing data > > seems to be statically loaded in testmgr.[ch], even if the algorithms to > > be tested are resident in modules that aren't loaded yet (so it's kind of > > test "on demand"). I guess it can't be split up amongst the algorithm > > modules as some of the tests require stuff from multiple modules (eg. aes > > + cbs + cts). > > Yes I've been meaning to split this up so they're colocated with > the generic implementation. Might be easier if I wait to see how you do that. > Unless this code has at least two users it's probably not worth > it (but there are exceptions, e.g. we did a one-user algorithm > for dm-crypt). There would be just two users at the moment: sunrpc/nfs and rxrpc/afs. I don't know if cifs or ceph could make use of it. David