qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Max Reitz <mreitz@redhat.com>
To: Eric Blake <eblake@redhat.com>, qemu-devel@nongnu.org
Cc: kwolf@redhat.com, libvir-list@redhat.com, pkrempa@redhat.com,
	qemu-block@nongnu.org, kchamart@redhat.com
Subject: Re: [PATCH v6 01/10] qemu-img: Flush stdout before before potential stderr messages
Date: Mon, 13 Jul 2020 11:22:17 +0200	[thread overview]
Message-ID: <f7e74b02-140e-4aa1-0b1d-ae58d97c0efa@redhat.com> (raw)
In-Reply-To: <20200706203954.341758-2-eblake@redhat.com>


[-- Attachment #1.1: Type: text/plain, Size: 972 bytes --]

On 06.07.20 22:39, Eric Blake wrote:
> During 'qemu-img create ... 2>&1', if --quiet is not in force, we can
> end up with buffered I/O in stdout that was produced before failure,
> but which appears in output after failure.  This is confusing; the fix
> is to flush stdout prior to attempting anything that might produce an
> error message.  Several iotests demonstrate the resulting ordering
> change now that the merged outputs now reflect chronology.  (An even
> better fix would be to avoid printf from within block.c altogether,
> but that's much more invasive...)
> 
> Signed-off-by: Eric Blake <eblake@redhat.com>
> ---
>  block.c                    | 1 +
>  tests/qemu-iotests/049.out | 8 ++++----
>  tests/qemu-iotests/054.out | 2 +-
>  tests/qemu-iotests/079.out | 2 +-
>  tests/qemu-iotests/112.out | 4 ++--
>  tests/qemu-iotests/259.out | 2 +-
>  6 files changed, 10 insertions(+), 9 deletions(-)

282 also needs some treatment.

Max


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2020-07-13  9:23 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-06 20:39 [PATCH v6 00/10] Tighten qemu-img rules on missing backing format Eric Blake
2020-07-06 20:39 ` [PATCH v6 01/10] qemu-img: Flush stdout before before potential stderr messages Eric Blake
2020-07-13  9:22   ` Max Reitz [this message]
2020-07-06 20:39 ` [PATCH v6 02/10] block: Finish deprecation of 'qemu-img convert -n -o' Eric Blake
2020-07-06 20:39 ` [PATCH v6 03/10] sheepdog: Add trivial backing_fmt support Eric Blake
2020-07-06 20:39 ` [PATCH v6 04/10] vmdk: " Eric Blake
2020-07-06 20:39 ` [PATCH v6 05/10] qcow: Tolerate backing_fmt= Eric Blake
2020-07-06 20:39 ` [PATCH v6 06/10] block: Error if backing file fails during creation without -u Eric Blake
2020-07-06 20:39 ` [PATCH v6 07/10] qcow2: Deprecate use of qemu-img amend to change backing file Eric Blake
2020-07-06 20:39 ` [PATCH v6 08/10] iotests: Specify explicit backing format where sensible Eric Blake
2020-07-07 16:07   ` Kevin Wolf
2020-07-07 19:57     ` Eric Blake
2020-07-06 20:39 ` [PATCH v6 09/10] block: Add support to warn on backing file change without format Eric Blake
2020-07-06 20:39 ` [PATCH v6 10/10] qemu-img: Deprecate use of -b without -F Eric Blake
2020-07-07 16:08 ` [PATCH v6 00/10] Tighten qemu-img rules on missing backing format Kevin Wolf

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=f7e74b02-140e-4aa1-0b1d-ae58d97c0efa@redhat.com \
    --to=mreitz@redhat.com \
    --cc=eblake@redhat.com \
    --cc=kchamart@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=libvir-list@redhat.com \
    --cc=pkrempa@redhat.com \
    --cc=qemu-block@nongnu.org \
    --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).