[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f8351bc887f8f95063f5e301f78755ef608a76a0.camel@linux.ibm.com>
Date: Wed, 25 Jan 2023 11:45:08 +1100
From: Andrew Donnellan <ajd@...ux.ibm.com>
To: Mimi Zohar <zohar@...ux.ibm.com>, linuxppc-dev@...ts.ozlabs.org,
linux-integrity@...r.kernel.org
Cc: gregkh@...uxfoundation.org, gcwilson@...ux.ibm.com,
linux-kernel@...r.kernel.org, nayna@...ux.ibm.com,
ruscur@...sell.cc, mpe@...erman.id.au, gjoyce@...ux.ibm.com,
sudhakar@...ux.ibm.com, bgray@...ux.ibm.com, erichte@...ux.ibm.com,
joel@....id.au
Subject: Re: [PATCH v4 24/24] integrity/powerpc: Support loading keys from
pseries secvar
On Tue, 2023-01-24 at 10:14 -0500, Mimi Zohar wrote:
> > - /* The following only applies for the edk2-compat backend.
> > */
> > - node = of_find_compatible_node(NULL, NULL, "ibm,edk2-
> > compat-v1");
> > - if (!node)
> > + len = secvar_ops->format(buf, 32);
>
> "powerpc/secvar: Handle format string in the consumer" defines
> opal_secvar_format() for the object format "ibm,secvar-backend".
> Here
> shouldn't it being returning the format for "ibm,edk2-compat-v1"?
opal_secvar_format() doesn't return "ibm,secvar-backend", it searches
for the device tree node named "ibm,secvar-backend", then reads and
returns the contents of the property "format" under that node.
The expected content of the format property is "ibm,edk2-compat-v1".
--
Andrew Donnellan OzLabs, ADL Canberra
ajd@...ux.ibm.com IBM Australia Limited
Powered by blists - more mailing lists