qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Victor Toso <victortoso@redhat.com>
To: John Snow <jsnow@redhat.com>
Cc: Eric Blake <eblake@redhat.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	Markus Armbruster <armbru@redhat.com>
Subject: Re: [PATCH 03/14] qapi: fix example of BLOCK_IO_ERROR event
Date: Fri, 25 Mar 2022 21:52:00 +0100	[thread overview]
Message-ID: <20220325205200.cvaufycz4qvviuuf@tapioca> (raw)
In-Reply-To: <CAFn=p-ZAc3xB49KEYf2LOvUKFNVWq3C8EU-vbVpc9QdgAuMqqA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2000 bytes --]

Hi,

On Thu, Mar 24, 2022 at 04:47:30PM -0400, John Snow wrote:
> On Thu, Mar 24, 2022 at 1:50 PM Victor Toso <victortoso@redhat.com> wrote:
> >
> > Reason is not optional.
> >
> > Signed-off-by: Victor Toso <victortoso@redhat.com>
> > ---
> >  qapi/block-core.json | 3 ++-
> >  1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/qapi/block-core.json b/qapi/block-core.json
> > index 585a9e020e..5b6c069dd9 100644
> > --- a/qapi/block-core.json
> > +++ b/qapi/block-core.json
> > @@ -5059,7 +5059,8 @@
> >  #      "data": { "device": "ide0-hd1",
> >  #                "node-name": "#block212",
> >  #                "operation": "write",
> > -#                "action": "stop" },
> > +#                "action": "stop",
> > +#                "reason": "Driver requires too large request alignment" },
> >  #      "timestamp": { "seconds": 1265044230, "microseconds": 450486 } }
> >  #
> >  ##
> > --
> > 2.35.1
> >
> 
> We discourage people using the reason programmatically, but
> there will indeed be one. Where'd you pull the message out
> from?

I was looking into the block related errors and pick a string. It
wasn't a real error that I had.

> I see this:
> 
> static void send_qmp_error_event(BlockBackend *blk,
>                                  BlockErrorAction action,
>                                  bool is_read, int error)
> {
>     IoOperationType optype;
>     BlockDriverState *bs = blk_bs(blk);
> 
>     optype = is_read ? IO_OPERATION_TYPE_READ : IO_OPERATION_TYPE_WRITE;
>     qapi_event_send_block_io_error(blk_name(blk), !!bs,
>                                    bs ? bdrv_get_node_name(bs) : NULL, optype,
>                                    action, blk_iostatus_is_enabled(blk),
>                                    error == ENOSPC, strerror(error));
> }
> 
> 
> so it should be one of the "standard" strerror messages, right?

Yep. I'll pick that one and use 'No space left on device'

Cheers,

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2022-03-25 20:53 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-24 17:50 [PATCH 00/14] Fix some qapi examples and a TODO section Victor Toso
2022-03-24 17:50 ` [PATCH 01/14] qapi: BlockExportRemoveMode: move comments to TODO Victor Toso
2022-03-24 20:34   ` John Snow
2022-03-25 20:35     ` Victor Toso
2022-03-25 12:33   ` Markus Armbruster
2022-03-25 15:11     ` John Snow
2022-03-25 20:47       ` Victor Toso
2022-03-28  7:46         ` "Future directions" vs. "TODO" in doc comments (was: [PATCH 01/14] qapi: BlockExportRemoveMode: move comments to TODO) Markus Armbruster
2022-03-29 16:31           ` John Snow
2022-03-24 17:50 ` [PATCH 02/14] qapi: fix example of BLOCK_IMAGE_CORRUPTED event Victor Toso
2022-03-24 19:15   ` John Snow
2022-03-24 20:40     ` John Snow
2022-03-25 12:43       ` Markus Armbruster
2022-03-25 20:59         ` Victor Toso
2022-03-25 21:40           ` John Snow
2022-03-24 17:50 ` [PATCH 03/14] qapi: fix example of BLOCK_IO_ERROR event Victor Toso
2022-03-24 20:47   ` John Snow
2022-03-25 20:52     ` Victor Toso [this message]
2022-03-24 17:50 ` [PATCH 04/14] qapi: fix example of BLOCK_JOB_PENDING event Victor Toso
2022-03-24 20:49   ` John Snow
2022-03-25 12:48   ` Markus Armbruster
2022-03-24 17:50 ` [PATCH 05/14] qapi: fix example of DUMP_COMPLETED event Victor Toso
2022-03-24 20:53   ` John Snow
2022-03-25 12:53     ` Markus Armbruster
2022-03-25 21:02       ` Victor Toso
2022-03-24 17:50 ` [PATCH 06/14] qapi: fix example of MEMORY_DEVICE_SIZE_CHANGE event Victor Toso
2022-03-24 20:57   ` John Snow
2022-03-25 13:00     ` Markus Armbruster
2022-03-25 21:03     ` Victor Toso
2022-03-24 17:50 ` [PATCH 07/14] qapi: fix example of UNPLUG_PRIMARY event Victor Toso
2022-03-24 21:01   ` John Snow
2022-03-24 17:50 ` [PATCH 08/14] qapi: fix example of FAILOVER_NEGOTIATED event Victor Toso
2022-03-24 21:05   ` John Snow
2022-03-24 17:50 ` [PATCH 09/14] qapi: run-state examples: add missing member Victor Toso
2022-03-24 21:12   ` John Snow
2022-03-24 17:50 ` [PATCH 10/14] qapi: run-state examples: add missing timestamp Victor Toso
2022-03-24 21:16   ` John Snow
2022-03-24 17:50 ` [PATCH 11/14] qapi: fix example of MEMORY_FAILURE Victor Toso
2022-03-24 21:28   ` John Snow
2022-03-24 17:50 ` [PATCH 12/14] qapi: ui examples: add missing websocket member Victor Toso
2022-03-24 21:22   ` John Snow
2022-03-24 17:50 ` [PATCH 13/14] qapi: fix example of ACPI_DEVICE_OST event Victor Toso
2022-03-24 21:31   ` John Snow
2022-03-24 17:50 ` [PATCH 14/14] qapi: fix example of dump-guest-memory Victor Toso
2022-03-24 21:31   ` John Snow
2022-03-24 21:33 ` [PATCH 00/14] Fix some qapi examples and a TODO section John Snow

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=20220325205200.cvaufycz4qvviuuf@tapioca \
    --to=victortoso@redhat.com \
    --cc=armbru@redhat.com \
    --cc=eblake@redhat.com \
    --cc=jsnow@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).