qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: qemu-pr-helper -v suppresses errors, isn't that weird?
Date: Thu, 18 Jun 2020 14:15:21 +0200	[thread overview]
Message-ID: <4a56a2cb-0025-cefc-68a0-37a14641b7b1@redhat.com> (raw)
In-Reply-To: <87imfpszvr.fsf@dusky.pond.sub.org>

On 18/06/20 07:32, Markus Armbruster wrote:
> prh_co_entry() reports reports errors reading requests / writing
> responses only when @verbose (command line -v); relevant code appended
> for you convenience.
> 
> Sure these are *errors*?  The program recovers and continues, and this
> is deemed normal enough to inform the user only when he specifically
> asks for it.  Yet when we inform, we format it as an error.  Should we
> tune it down to warnings?

They are errors, but they're errors in the client rather than in
qemu-pr-helper.c itself.

Paolo

> 
> static void coroutine_fn prh_co_entry(void *opaque)
> {
>     [...]
>     while (atomic_read(&state) == RUNNING) {
>         [...]
>         sz = prh_read_request(client, &req, &resp, &local_err);
>         if (sz < 0) {
>             break;
>         }
>         [...]
>         if (prh_write_response(client, &req, &resp, &local_err) < 0) {
>             break;
>         }
>     }
>     if (local_err) {
>         if (verbose == 0) {
>             error_free(local_err);
>         } else {
>             error_report_err(local_err);
>         }
>     }
> 
> out:
>     qio_channel_detach_aio_context(QIO_CHANNEL(client->ioc));
>     object_unref(OBJECT(client->ioc));
>     g_free(client);
> }
> 



  reply	other threads:[~2020-06-18 12:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-18  5:32 qemu-pr-helper -v suppresses errors, isn't that weird? Markus Armbruster
2020-06-18 12:15 ` Paolo Bonzini [this message]
2020-06-22  8:28   ` Markus Armbruster

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=4a56a2cb-0025-cefc-68a0-37a14641b7b1@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=armbru@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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).