Received: by 2002:a05:6a10:9e8c:0:0:0:0 with SMTP id y12csp1007pxx; Mon, 26 Oct 2020 01:30:07 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzoxJBi/29JS11eUB12Mv6jWk/8cerctDuAYGIILGrWJ7Ma0hlQdl71x97/6LeHHONuQgyX X-Received: by 2002:a05:6402:1cbb:: with SMTP id cz27mr13974689edb.38.1603701006725; Mon, 26 Oct 2020 01:30:06 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1603701006; cv=none; d=google.com; s=arc-20160816; b=s90hJ4IazvIlqm91EJCkQkF+NPd+HvtpulzbkIL1pPsrYHYLg0ddeRsPa6PyQ5buMU /aErK3I5jwA5MAL+vKy0VF4n5r6kaHb14W3bU4jYGNPJldAY1syorSLeRokQT/Q4n1Up 8C2dogO5q8Y2hx95aGFY1rxv3ILJp53ecEGTMHCYC2PItT/55tOkwY6asxQ+XDQPorMB 1nv+VDgvDUMofhEz+o1nA+230JRIb9TbPRu3f3l7FPDY+/3XHADhlX2FYzGNt74shUl4 +ddvMV4IrNVWNScazjln0dx2yzbNmKogzbtHnR+glToTyRpvu13p5qhnL8h0oYuP+6t8 zgHA== 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=P0NQpbLnU/WdE582I5VOmrY125EZ2zHqmZDIamHKW4o=; b=dTQaTprF6w8iDnxt069MuzT9lHgYzigFcpsngbsHz6e4acFguhnhPXrGpycqlvOExB ITDSUQDIdOnZqxaSenrf3cHIc1F/G0TC7dC/nh1+nT4DzHQP2PFBz13aN4IKjnVz7tbc t9cG7MFY7mYDUnV7wRnRfFUQXyCtg8uIchTWiMXlPMbofAbpAOJYbW9rqmkq490Eo1VE tsCyhQ421RPJUrJE5m68eDHFdgTb7X7Ut/AMRwPggwOgqqgasf2ZsG02QohBnc/H35oO PKRXnxJP0h4V9YCc4nvEs/eSEfqm4JlteGFL8nh2nOiKsPJrd23T6G6VTUl8K3q+/ISh MziA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=rHdzkpMW; 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=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id h34si4293819edd.264.2020.10.26.01.29.43; Mon, 26 Oct 2020 01:30:06 -0700 (PDT) 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=@kernel.org header.s=default header.b=rHdzkpMW; 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=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1771081AbgJZH7U (ORCPT + 99 others); Mon, 26 Oct 2020 03:59:20 -0400 Received: from mail.kernel.org ([198.145.29.99]:59716 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1771080AbgJZH7T (ORCPT ); Mon, 26 Oct 2020 03:59:19 -0400 Received: from mail-ot1-f42.google.com (mail-ot1-f42.google.com [209.85.210.42]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id CD8B1223B0; Mon, 26 Oct 2020 07:59:18 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1603699158; bh=/fGqu8xrhCGoVU5KPsNJLhNRGjQAfSf+VUBWI9Mep8c=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=rHdzkpMWjr0vpfR6LZj2Ys6WLEXpmKcPrV8LKONe55e3nBNbBj5jy2awA04gLaZbV 7E1ypKSvdyv3CeA9ZIW8so7T3yvQ3Ykvco4SVOY/oi7srou7Gg6p1giig/7/fhNdvt ArdCZGl/kCg1bCxsd2q5eJKiqH6hTsEf+umgbanM= Received: by mail-ot1-f42.google.com with SMTP id f37so7194818otf.12; Mon, 26 Oct 2020 00:59:18 -0700 (PDT) X-Gm-Message-State: AOAM531TSE/0R4LXYeOHtixhMqhzp/J3AzTbPjpIjXqGsEudzQjxlrp9 v9ml2g/W1qtWGSdxOBylQMDWCTrbXvTwKL9oM0o= X-Received: by 2002:a05:6830:1f13:: with SMTP id u19mr3277545otg.108.1603699158195; Mon, 26 Oct 2020 00:59:18 -0700 (PDT) MIME-Version: 1.0 References: <20201025143119.1054168-1-nivedita@alum.mit.edu> <20201025143119.1054168-2-nivedita@alum.mit.edu> In-Reply-To: <20201025143119.1054168-2-nivedita@alum.mit.edu> From: Ard Biesheuvel Date: Mon, 26 Oct 2020 08:59:07 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v4 1/6] crypto: lib/sha256 - Use memzero_explicit() for clearing state To: Arvind Sankar Cc: Herbert Xu , "David S. Miller" , "linux-crypto@vger.kernel.org" , Eric Biggers , David Laight , Linux Kernel Mailing List , Eric Biggers Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org On Sun, 25 Oct 2020 at 15:31, Arvind Sankar wrote: > > Without the barrier_data() inside memzero_explicit(), the compiler may > optimize away the state-clearing if it can tell that the state is not > used afterwards. At least in lib/crypto/sha256.c:__sha256_final(), the > function can get inlined into sha256(), in which case the memset is > optimized away. > > Signed-off-by: Arvind Sankar > Reviewed-by: Eric Biggers Acked-by: Ard Biesheuvel > --- > lib/crypto/sha256.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/lib/crypto/sha256.c b/lib/crypto/sha256.c > index 2321f6cb322f..d43bc39ab05e 100644 > --- a/lib/crypto/sha256.c > +++ b/lib/crypto/sha256.c > @@ -265,7 +265,7 @@ static void __sha256_final(struct sha256_state *sctx, u8 *out, int digest_words) > put_unaligned_be32(sctx->state[i], &dst[i]); > > /* Zeroize sensitive information. */ > - memset(sctx, 0, sizeof(*sctx)); > + memzero_explicit(sctx, sizeof(*sctx)); > } > > void sha256_final(struct sha256_state *sctx, u8 *out) > -- > 2.26.2 >