From: Gregory Price <gourry@gourry.net>
To: Ilias Apalodimas <ilias.apalodimas@linaro.org>
Cc: linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org,
ardb@kernel.org, leitao@debian.org, usamaarif642@gmail.com,
sathyanarayanan.kuppuswamy@linux.intel.com
Subject: Re: [PATCH 3/6] libstub,tpm: provide indication of failure when getting event log
Date: Fri, 13 Sep 2024 19:06:45 -0400 [thread overview]
Message-ID: <ZuTFhb8IF_EC70Wy@PC2K9PVX.TheFacebook.com> (raw)
In-Reply-To: <CAC_iWjKFmHUV4EzhfJ_OAHOZhrAzH35O8QMzVK_Zs2aTG5h+1Q@mail.gmail.com>
On Fri, Sep 13, 2024 at 04:10:08PM +0300, Ilias Apalodimas wrote:
> On Fri, 13 Sept 2024 at 15:58, Gregory Price <gourry@gourry.net> wrote:
> >
> > > > - if (status != EFI_SUCCESS || !log_location)
> > > > + if (status != EFI_SUCCESS || !log_location) {
> > > > + efi_err("TPM unable to provide Event Log\n");
> > >
> > > s/provide/retrieve/ and yes the print is going to be useful. Do you
> > > know if the EventLog is mandatory. Reading at the spec GetEventlog
> > > only has 2 return values, which implies you can't return "Not
> > > supported", but it's not explicitly stated anywhere
> > >
> >
> > I believe it is mandatory from my reading of the spec - but the
> > "Final Event Log" was only added in 2.0. We report an error when
> > 2.0 is reported but the final event log is not supported, so i figure
> > we should probably report when the event log fails as well.
>
> Yea I am fine with that, I was just wondering if we should do _err or
> _warn. I am fine with the error
>
> /Ilias
Per Ard's notes on patch 6 i'm going to drop this. These prints apparently
don't actually end up anywhere.
~Gregory
next prev parent reply other threads:[~2024-09-13 23:07 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-06 20:27 [PATCH 0/6] libstub,tpm: fix small bugs and improve error reporting Gregory Price
2024-09-06 20:27 ` [PATCH 1/6] tpm: fix signed/unsigned bug when checking event logs Gregory Price
2024-09-06 20:27 ` [PATCH 2/6] tpm: do not ignore memblock_reserve return value Gregory Price
2024-09-13 7:02 ` Ilias Apalodimas
2024-09-13 12:58 ` Gregory Price
2024-09-06 20:27 ` [PATCH 3/6] libstub,tpm: provide indication of failure when getting event log Gregory Price
2024-09-13 6:59 ` Ilias Apalodimas
2024-09-13 12:57 ` Gregory Price
2024-09-13 13:10 ` Ilias Apalodimas
2024-09-13 23:06 ` Gregory Price [this message]
2024-09-06 20:27 ` [PATCH 4/6] tpm: sanity check the log version before using it Gregory Price
2024-09-13 6:40 ` Ilias Apalodimas
2024-09-13 12:56 ` Gregory Price
2024-09-13 13:39 ` Ilias Apalodimas
2024-09-13 13:44 ` Ard Biesheuvel
2024-09-13 13:47 ` Ard Biesheuvel
2024-09-13 14:03 ` Gregory Price
2024-09-06 20:27 ` [PATCH 5/6] tpm: fix unsigned/signed mismatch errors related to __calc_tpm2_event_size Gregory Price
2024-09-06 20:27 ` [PATCH 6/6] libstub,tpm: do not ignore failure case when reading final event log Gregory Price
2024-09-13 15:25 ` Ard Biesheuvel
2024-09-13 15:29 ` Gregory Price
2024-09-13 15:59 ` Ard Biesheuvel
2024-09-13 17:36 ` Gregory Price
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZuTFhb8IF_EC70Wy@PC2K9PVX.TheFacebook.com \
--to=gourry@gourry.net \
--cc=ardb@kernel.org \
--cc=ilias.apalodimas@linaro.org \
--cc=leitao@debian.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=usamaarif642@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox