From: David Gibson <david@gibson.dropbear.id.au>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: marcandre.lureau@redhat.com,
Stefan Berger <stefanb@linux.ibm.com>,
qemu-ppc@nongnu.org, qemu-devel@nongnu.org,
Stefan Berger <stefanb@linux.vnet.ibm.com>
Subject: Re: [PATCH v2 1/2] tpm: tpm_spapr: Exit on TPM backend failures
Date: Tue, 7 Jul 2020 18:19:16 +1000 [thread overview]
Message-ID: <20200707081916.GA18595@umbus.fritz.box> (raw)
In-Reply-To: <aa63c5f3-308e-59e1-11ff-0e0d923658e8@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1563 bytes --]
On Tue, Jul 07, 2020 at 06:20:49AM +0200, Philippe Mathieu-Daudé wrote:
> Hi Stefan,
>
> On 7/7/20 6:05 AM, Stefan Berger wrote:
> > Exit on TPM backend failures in the same way as the TPM CRB and TIS device
> > models do.
>
> Maybe the other models are not the best examples ;)
>
> >
> > Signed-off-by: Stefan Berger <stefanb@linux.ibm.com>
> > ---
> > hw/tpm/tpm_spapr.c | 5 ++++-
> > 1 file changed, 4 insertions(+), 1 deletion(-)
> >
> > diff --git a/hw/tpm/tpm_spapr.c b/hw/tpm/tpm_spapr.c
> > index cb4dfd1e6a..8288ab0a15 100644
> > --- a/hw/tpm/tpm_spapr.c
> > +++ b/hw/tpm/tpm_spapr.c
> > @@ -306,7 +306,10 @@ static void tpm_spapr_reset(SpaprVioDevice *dev)
> > TPM_SPAPR_BUFFER_MAX);
> >
> > tpm_backend_reset(s->be_driver);
> > - tpm_spapr_do_startup_tpm(s, s->be_buffer_size);
> > +
> > + if (tpm_spapr_do_startup_tpm(s, s->be_buffer_size) < 0) {
>
> I don't see error reported, how users can know the cause of the exit?
>
> > + exit(1);
>
> What about using this instead?
>
> qemu_system_shutdown_request(SHUTDOWN_CAUSE_HOST_ERROR);
Hrm. I'm not entirely convinced that's what we want. But we
definitely need some sort of error reported.
>
> > + }
> > }
> >
> > static enum TPMVersion tpm_spapr_get_version(TPMIf *ti)
> >
>
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-07-07 8:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-07 4:05 [PATCH v2 0/2] tpm: Some fixes Stefan Berger
2020-07-07 4:05 ` [PATCH v2 1/2] tpm: tpm_spapr: Exit on TPM backend failures Stefan Berger
2020-07-07 4:20 ` Philippe Mathieu-Daudé
2020-07-07 8:19 ` David Gibson [this message]
2020-07-07 12:52 ` Stefan Berger
2020-07-07 13:24 ` Philippe Mathieu-Daudé
2020-07-07 4:05 ` [PATCH v2 2/2] tests: Skip over pcrUpdateCounter byte in result comparison Stefan Berger
2020-07-07 8:19 ` David Gibson
2020-07-07 17:43 ` Stefan Berger
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=20200707081916.GA18595@umbus.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=marcandre.lureau@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=stefanb@linux.ibm.com \
--cc=stefanb@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).