Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp5729405rwd; Mon, 5 Jun 2023 07:51:00 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ6nzM6j8lZY7+xyWHSAldedwjaMGIWKdl01tR0fgpTuDZs3BP0e48QlHG27nuMOwHEzc0Ov X-Received: by 2002:a05:6a00:410a:b0:65c:eef9:27b6 with SMTP id bu10-20020a056a00410a00b0065ceef927b6mr1924838pfb.3.1685976660342; Mon, 05 Jun 2023 07:51:00 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1685976660; cv=none; d=google.com; s=arc-20160816; b=0Wh3KLA19ukaJuth9oUU4S99eCKN0oRrTDK9sJxZwAe7NuBCYN3im9HdZ4P4Ukft8J HMDLtzt5gnT3Vc+Y2wVqbPzpsXJqdv4gmydfBy8FDzd/V6ov4hDcaqNjPDPqlFfsvPPx 9WUW4H8kKrAPqu6r878qV6A6/KWNlvep/7ALca79wamXBIKU9Hp4eEJTbwBkiQdrwoCr tyeNv9KwxqESbXuzitmGuucllX0fuCJij+328mSyNO/gVrrUqKF9jQF2y7N2qEnB6jtG iamyI7xHJfInjDxKNWYrr32pcEyORgBRBI8e9pbXngEnl8aQxixSRXOuh+bgi0Pp3UQM wleg== 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=GKnTrK6N8fyx8N4wY6ury0F8xx6HRQHrf6vLk5OPOl8=; b=mxsmCi00Y7DHjuIZaAY+eJ0uNJC4wUFOjaLHa8/TzD8FozfWwdvu8mT611qrHnfHXP hTbWxO1GnrwZLlEoj5sT+Y0tfqpvcmnUddbPMA3yRWYXY2bKvxoegVibOwOyexNdX6ph B3KqiXvhH9yeEoLjN1rRr6AkUF84Vgx5s4LtWBhLmKroLLsCiQz2JymqHEiSD2+oOLRm Ytv7/gPOWPWBPTG5NdgQMaLwxXrFeH4ZmIuy3l37Eife/Ijd1c9Ey9hKUMcdAmk/keFl qM0sHhfRxzWhA0EavBHfsRg5oUip4B5/ofMbId2d+B+yaw6bsC+Yji/JZjrXl5pDMdZD JWhg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=esh1Nw0A; 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 t191-20020a6381c8000000b0053fb85dd818si5645012pgd.52.2023.06.05.07.50.33; Mon, 05 Jun 2023 07:51:00 -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=esh1Nw0A; 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 S234614AbjFEOs5 (ORCPT + 99 others); Mon, 5 Jun 2023 10:48:57 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35938 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234622AbjFEOsr (ORCPT ); Mon, 5 Jun 2023 10:48:47 -0400 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 09B38F4 for ; Mon, 5 Jun 2023 07:47:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1685976477; 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=GKnTrK6N8fyx8N4wY6ury0F8xx6HRQHrf6vLk5OPOl8=; b=esh1Nw0AkQPNzS0h/xNmYifylD2K8X5I5CTmuOUYqEKCY3nD7Aogv8LYGBqRPQ56emvkUR TqKtb3lbEZXwCv0SCZ0dqxcBIY2KFRz/E9P3W9rw6BvbIEcNqBXihnEXjqvEkQLkBO20EB 0+e0d6Lkei6s64G1k2LJg4/Z5f3EbBc= 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-314-3qv7PdMlP5-fXF9d25ZGlg-1; Mon, 05 Jun 2023 10:47:52 -0400 X-MC-Unique: 3qv7PdMlP5-fXF9d25ZGlg-1 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.rdu2.redhat.com [10.11.54.3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id DE563101A55C; Mon, 5 Jun 2023 14:47:50 +0000 (UTC) Received: from warthog.procyon.org.uk (unknown [10.42.28.182]) by smtp.corp.redhat.com (Postfix) with ESMTP id 5292A1121314; Mon, 5 Jun 2023 14:47:47 +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: <4d7e38ff5bbc496cb794b50e1c5c83bcd2317e69.camel@huaweicloud.com> References: <4d7e38ff5bbc496cb794b50e1c5c83bcd2317e69.camel@huaweicloud.com> To: Roberto Sassu Cc: dhowells@redhat.com, Linus Torvalds , Andrew Morton , Eric Biggers , Stefan Berger , herbert@gondor.apana.org.au, davem@davemloft.net, zohar@linux.ibm.com, dmitry.kasatkin@gmail.com, paul@paul-moore.com, jmorris@namei.org, serge@hallyn.com, Jarkko Sakkinen , linux-integrity@vger.kernel.org, linux-security-module@vger.kernel.org, keyrings@vger.kernel.org, linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org, stable@vger.kernel.org Subject: Re: [GIT PULL] Asymmetric keys fix for v6.4-rc5 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1727998.1685976466.1@warthog.procyon.org.uk> Date: Mon, 05 Jun 2023 15:47:46 +0100 Message-ID: <1727999.1685976466@warthog.procyon.org.uk> X-Scanned-By: MIMEDefang 3.1 on 10.11.54.3 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, SPF_HELO_NONE,SPF_NONE,T_SCC_BODY_TEXT_LINE autolearn=unavailable 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 Roberto Sassu wrote: > Here is a small fix to make an unconditional copy of the buffer passed > to crypto operations, to take into account the case of the stack not in > the linear mapping area. I wonder if evm_verify_hmac() and other such callers of the signature verification service should be placing the data and crypto material in slab memory rather than it being on the stack. But, for the moment: Acked-by: David Howells