From: "Michael S. Tsirkin" <mst@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] vhost-user: print original request on error
Date: Tue, 17 Nov 2015 10:28:29 +0200 [thread overview]
Message-ID: <20151117102748-mutt-send-email-mst@redhat.com> (raw)
In-Reply-To: <87lh9x2hc7.fsf@blackfin.pond.sub.org>
On Tue, Nov 17, 2015 at 08:52:24AM +0100, Markus Armbruster wrote:
> "Michael S. Tsirkin" <mst@redhat.com> writes:
>
> > When we get an unexpected response, print out
> > the original request.
> > Helps debug protocol errors tremendously.
> >
> > Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> > ---
> >
> > Changes from v1: add missing .
> >
> > hw/virtio/vhost-user.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/hw/virtio/vhost-user.c b/hw/virtio/vhost-user.c
> > index 3404b81..5bc6c45 100644
> > --- a/hw/virtio/vhost-user.c
> > +++ b/hw/virtio/vhost-user.c
> > @@ -121,8 +121,8 @@ static int vhost_user_read(struct vhost_dev *dev, VhostUserMsg *msg)
> >
> > r = qemu_chr_fe_read_all(chr, p, size);
> > if (r != size) {
> > - error_report("Failed to read msg header. Read %d instead of %d.", r,
> > - size);
> > + error_report("Failed to read msg header. Read %d instead of %d."
> > + " Original request %d.", r, size, msg->request);
> > goto fail;
> > }
>
> Error message style nit: the error message proper (the thing emitted by
> error_report()) should be a phrase, and it should be short and to the
> point. It can be followed by hints. Compare:
>
> qemu-system-x86_64: Failed to read msg header. Read 11 instead of 12. Original request 1.
>
> and
>
> qemu-system-x86_64: Failed to read msg header
> Read 11 instead of 12 for request 1.
>
> I prefer the latter. The error message proper is short and to the
> point. The hint adds information, which happens to be useful mainly to
> developers. Sensible line lengths.
>
> By the way, the error.h API supports this message + hints convention
> since commit 50b7b00.
>
> See also
> Message-ID: <87oaf3jww7.fsf@blackfin.pond.sub.org>
> http://lists.gnu.org/archive/html/qemu-devel/2015-11/msg01662.html
Oh that's nice. There are more cases like this in vhost-user.
Let's rework them all past 2.5?
--
MST
next prev parent reply other threads:[~2015-11-17 8:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-16 12:26 [Qemu-devel] [PATCH v2] vhost-user: print original request on error Michael S. Tsirkin
2015-11-17 7:52 ` Markus Armbruster
2015-11-17 8:28 ` Michael S. Tsirkin [this message]
2015-11-17 10:23 ` 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=20151117102748-mutt-send-email-mst@redhat.com \
--to=mst@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).