From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.2 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id AE2A2C3A5A2 for ; Mon, 19 Aug 2019 19:38:25 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 8F13622CE8 for ; Mon, 19 Aug 2019 19:38:25 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728537AbfHSTiY (ORCPT ); Mon, 19 Aug 2019 15:38:24 -0400 Received: from mx1.redhat.com ([209.132.183.28]:50528 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728409AbfHSTiY (ORCPT ); Mon, 19 Aug 2019 15:38:24 -0400 Received: from mail-ed1-f69.google.com (mail-ed1-f69.google.com [209.85.208.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 8A679CF20 for ; Mon, 19 Aug 2019 19:38:23 +0000 (UTC) Received: by mail-ed1-f69.google.com with SMTP id z2so2687168ede.2 for ; Mon, 19 Aug 2019 12:38:23 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=epMZYUQThudMmx1f+HohIJV2IyBC2uLXUOpK0jlDnOc=; b=B/UIQ19YXHrALkPS+w/cRE8Vqjys5AzDho2Z99KV4mi8e63qi3YkmEFXRX0ORnAEqX AxOUSqBe/WV0befIw0nU9wRwqrOJWh2DmDXCtf5ag2ZsMDJM9JtET3UB/lR0M5YJJjV2 xfCUKgHTDEsgKOOlCVMZz1GN7eTNG/8Ao/zLCNxjCLf5M+Pon+fGOb0HC1nD4xHMYSb+ Yk25ijubihvf2KTqVUtzm5ldrJ6pXL3JkKbxfAd/zpQ1huFxTlixZMZ3FdXMRJZDWzzR 0yixqFGK2tBSjeIUOkpo+ZGRt6Zh51qRCISqIVmArVvj7e00rLlurti0poBHhZnIpFkN w1Aw== X-Gm-Message-State: APjAAAXNzEg0Sq99MsqjTEGE/5uSldouJdsXbXNAzJktHo7w6hS7Eo5j 2IV/RX6ekDp7MhNeoDyCfreqG4Dopk9rw/MUh73hPGxSvNEfVog1YWd/55w9z+K77DrzqOGuNKp gc+zoLX8Oo35ue0zAJshwDtfE X-Received: by 2002:a17:906:c669:: with SMTP id ew9mr23030295ejb.217.1566243501850; Mon, 19 Aug 2019 12:38:21 -0700 (PDT) X-Google-Smtp-Source: APXvYqx24tddABalUfakS1nD908edAktLRmPH1oGHHvS+Bgm+lkUZqCb7ZIW6DkW8LWrEXzDVgMjoA== X-Received: by 2002:a17:906:c669:: with SMTP id ew9mr23030271ejb.217.1566243501590; Mon, 19 Aug 2019 12:38:21 -0700 (PDT) Received: from shalem.localdomain (84-106-84-65.cable.dynamic.v4.ziggo.nl. [84.106.84.65]) by smtp.gmail.com with ESMTPSA id d10sm1653712ejd.86.2019.08.19.12.38.20 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 19 Aug 2019 12:38:20 -0700 (PDT) Subject: Re: [PATCH v2 0/7] crypto: sha256 - Merge 2 separate C implementations into 1, put into separate library To: Ard Biesheuvel Cc: Herbert Xu , Thomas Gleixner , Ingo Molnar , Borislav Petkov , "H . Peter Anvin" , Heiko Carstens , Vasily Gorbik , Christian Borntraeger , Eric Biggers , Andy Lutomirski , "open list:HARDWARE RANDOM NUMBER GENERATOR CORE" , the arch/x86 maintainers , linux-s390 , Linux Kernel Mailing List References: <20190817142435.8532-1-hdegoede@redhat.com> From: Hans de Goede Message-ID: <26a86843-d610-80fe-6bdc-a8ce4fd43d6b@redhat.com> Date: Mon, 19 Aug 2019 21:38:19 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, On 19-08-19 17:08, Ard Biesheuvel wrote: > On Sat, 17 Aug 2019 at 17:24, Hans de Goede wrote: >> >> Hi All, >> >> Here is v2 of my patch series refactoring the current 2 separate SHA256 >> C implementations into 1 and put it into a separate library. >> >> There are 3 reasons for this: >> >> 1) Remove the code duplication of having 2 separate implementations >> >> 2) Offer a separate library SHA256 implementation which can be used >> without having to call crypto_alloc_shash first. This is especially >> useful for use during early boot when crypto_alloc_shash does not >> work yet. >> >> 3) Having the purgatory code using the same code as the crypto subsys means >> that the purgratory code will be tested by the crypto subsys selftests. >> >> This has been tested on x86, including checking that kecec still works. >> >> This has NOT been tested on s390, if someone with access to s390 can >> test that things still build with this series applied and that >> kexec still works, that would be great. >> >> Changes in v2: >> - Use put_unaligned_be32 to store the hash to allow callers to use an >> unaligned buffer for storing the hash >> - Add a comment to include/crypto/sha256.h explaining that these functions >> now may be used outside of the purgatory too (and that using the crypto >> API instead is preferred) >> - Add sha224 support to the lib/crypto/sha256 library code >> - Make crypto/sha256_generic.c not only use sha256_transform from >> lib/crypto/sha256.c but also switch it to using sha256_init, sha256_update >> and sha256_final from there so that the crypto subsys selftests fully test >> the lib/crypto/sha256.c implementation >> > > This looks fine to me, although I agree with Eric's feedback regarding > further cleanups. Ack, as I already told Eric I'm happy to do a follow up series with the necessary local static function renames so that we can then merge sha256.h into sha.h . > Also, now that we have a C library, I'd like to drop > the dependency of the mips and x86 sha256 algo implementations up > sha256_generic.c, and use the library directly instead (so that > sha256-generic is no longer needed on x86 or mips) I assume this is more of a generic remark and not targeted towards me? Regards, Hans