All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: Stefan Berger <stefanb@linux.vnet.ibm.com>
Cc: marcandre.lureau@redhat.com, philmd@redhat.com,
	qemu-devel@nongnu.org, Stefan Berger <stefanb@linux.ibm.com>
Subject: Re: [PATCH] tpm_emulator: Report an error if chardev is missing
Date: Fri, 24 Jul 2020 16:00:49 +0200	[thread overview]
Message-ID: <874kpx9fn2.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <20200724133011.2488055-1-stefanb@linux.vnet.ibm.com> (Stefan Berger's message of "Fri, 24 Jul 2020 09:30:11 -0400")

Stefan Berger <stefanb@linux.vnet.ibm.com> writes:

> This patch fixes the odd error reporting when trying to send a file
> descriptor to the TPM emulator if one has not passed a valid chardev.
>
> $ x86_64-softmmu/qemu-system-x86_64 -tpmdev emulator,id=tpm0
> qemu-system-x86_64: -tpmdev emulator,id=tpm0: tpm-emulator: Failed to send CMD_SET_DATAFD: Success
> qemu-system-x86_64: -tpmdev emulator,id=tpm0: tpm-emulator: Could not cleanly shutdown the TPM: Success
>
> This is the new error report:
>
> $ x86_64-softmmu/qemu-system-x86_64 -tpmdev emulator,id=tpm0
> qemu-system-x86_64: -tpmdev emulator,id=tpm0: tpm-emulator: missing chardev
                                                ~~~~~~~~~~~~~~

The "tpm-emulator: " part looks superfluous.

Hmm, many error messages in this file have it.  Feel free to keep it
now for consistency, and clean it up later.

We usually report missing option parameters like "parameter 'chardev' is
missing".  Please consider sticking to that.

>
> This change does not hide the display of supported TPM types if a non-existent type is passed:
>
> $ x86_64-softmmu/qemu-system-x86_64 -tpmdev nonexistent,id=tpm0
> qemu-system-x86_64: -tpmdev nonexistent,id=tpm0: Parameter 'type' expects a TPM backend type
> Supported TPM types (choose only one):
>  passthrough   Passthrough TPM backend driver
>     emulator   TPM emulator backend driver
>
> Signed-off-by: Stefan Berger <stefanb@linux.ibm.com>
> ---
>  backends/tpm/tpm_emulator.c | 8 ++++++++
>  1 file changed, 8 insertions(+)
>
> diff --git a/backends/tpm/tpm_emulator.c b/backends/tpm/tpm_emulator.c
> index 9605339f93..55cbc9c60e 100644
> --- a/backends/tpm/tpm_emulator.c
> +++ b/backends/tpm/tpm_emulator.c
> @@ -568,6 +568,9 @@ static int tpm_emulator_handle_device_opts(TPMEmulator *tpm_emu, QemuOpts *opts)
>          }
>  
>          tpm_emu->options->chardev = g_strdup(value);
> +    } else {
> +        error_report("tpm-emulator: missing chardev");
> +        goto err;
>      }
>  
>      if (tpm_emulator_prepare_data_fd(tpm_emu) < 0) {

This is minimally invasive.

I'd prefer

       Error *err = NULL;
       const char *value;
       Chardev *dev;

       value = qemu_opt_get(opts, "chardev");
       if (!value) {
           error_report("tpm-emulator: missing chardev");
           goto err;
       }

       dev = qemu_chr_find(value);
       if (!dev) {
           error_report("tpm-emulator: tpm chardev '%s' not found.", value);
           goto err;
       }

Your choice.

> @@ -925,6 +928,11 @@ static void tpm_emulator_shutdown(TPMEmulator *tpm_emu)
>  {
>      ptm_res res;
>  
> +    if (!tpm_emu->options->chardev) {
> +        /* was never properly initialized */
> +        return;
> +    }
> +

Is this still reachable?  If yes, how?

If not, drop the hunk and have my
Reviewed-by: Markus Armbruster <armbru@redhat.com>

>      if (tpm_emulator_ctrlcmd(tpm_emu, CMD_SHUTDOWN, &res, 0, sizeof(res)) < 0) {
>          error_report("tpm-emulator: Could not cleanly shutdown the TPM: %s",
>                       strerror(errno));



  parent reply	other threads:[~2020-07-24 14:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-24 13:30 [PATCH] tpm_emulator: Report an error if chardev is missing Stefan Berger
2020-07-24 13:58 ` Marc-André Lureau
2020-07-24 14:00 ` Markus Armbruster [this message]
2020-07-24 14:11   ` 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=874kpx9fn2.fsf@dusky.pond.sub.org \
    --to=armbru@redhat.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.