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=-0.9 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS 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 5D38DC17448 for ; Tue, 12 Nov 2019 01:21:06 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 32D6221925 for ; Tue, 12 Nov 2019 01:21:06 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=ellerman.id.au header.i=@ellerman.id.au header.b="MoSZd7gI" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726979AbfKLBVE (ORCPT ); Mon, 11 Nov 2019 20:21:04 -0500 Received: from bilbo.ozlabs.org ([203.11.71.1]:54609 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726906AbfKLBVE (ORCPT ); Mon, 11 Nov 2019 20:21:04 -0500 Received: from authenticated.ozlabs.org (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail.ozlabs.org (Postfix) with ESMTPSA id 47Bqgx1Ywjz9sP4; Tue, 12 Nov 2019 12:21:01 +1100 (AEDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ellerman.id.au; s=201909; t=1573521661; bh=F9ZI7aJXVRSlCItRZVrAQItH8rcNwZbNz7XhEYGd5MM=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=MoSZd7gInPCPqS8Y0iT98x1HK1vNNhVr/zZB4JiXZjLV1BMkNQT13BWWbUIqA0zBO JDFYy4EazB84GH1G6G2PPmoRnt0K9ChPMSxwpRYUbhePPcLg2K+M9sswNV1nyfWvTI Xiid+IBG0a/bOQycR7OvXIxjUmVwYErB+vS3lX5gZDZLOtkVAEdlpk1077UIzTr0z6 GCiinP46ZWqf+B8+TrbDVVVpiaGIaZmTjGi0PuBExuFganVMoBm9VcqB6Xd+K6J74z TaxZH44Ms9pe5myYbyUf7AMTY7fv1Bd6UIx9AqhJkeRwsRLvKASWbtQuCphrm0eYQx 03lK0YzT3KyTg== From: Michael Ellerman To: Lakshmi Ramasubramanian , Nayna Jain , linuxppc-dev@ozlabs.org, linux-efi@vger.kernel.org, linux-integrity@vger.kernel.org Cc: linux-kernel@vger.kernel.org, Benjamin Herrenschmidt , Paul Mackerras , Ard Biesheuvel , Jeremy Kerr , Matthew Garret , Mimi Zohar , Greg Kroah-Hartman , George Wilson , Claudio Carvalho , Elaine Palmer , Eric Ricther , Oliver O'Halloran Subject: Re: [PATCH v9 0/4] powerpc: expose secure variables to the kernel and userspace In-Reply-To: <216572e5-d8c6-f181-3ec0-b4a840f20f46@linux.microsoft.com> References: <1573441836-3632-1-git-send-email-nayna@linux.ibm.com> <216572e5-d8c6-f181-3ec0-b4a840f20f46@linux.microsoft.com> Date: Tue, 12 Nov 2019 12:21:00 +1100 Message-ID: <87sgmt3n5v.fsf@mpe.ellerman.id.au> MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Lakshmi Ramasubramanian writes: > On 11/10/19 7:10 PM, Nayna Jain wrote: > > Hi Nayna, > >> In order to verify the OS kernel on PowerNV systems, secure boot requires >> X.509 certificates trusted by the platform. These are stored in secure >> variables controlled by OPAL, called OPAL secure variables. In order to >> enable users to manage the keys, the secure variables need to be exposed >> to userspace. > Are you planning to split the patches in this patch set into smaller > chunks so that it is easier to code review and also perhaps make it > easier when merging the changes? I don't think splitting them would add any value. They're already split into the firmware specific bits (patch 1), and the sysfs parts (patch 2), which is sufficient for me. cheers