All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Kevin Wolf <kwolf@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Max Reitz <mreitz@redhat.com>, Qemu-block <qemu-block@nongnu.org>,
	"patches@linaro.org" <patches@linaro.org>
Subject: Re: [Qemu-devel] [PATCH] tests: Disable test-bdrv-drain
Date: Mon, 8 Oct 2018 18:07:52 +0100	[thread overview]
Message-ID: <CAFEAcA80vkufJ=hwr5s5i9xFzE1HxZKbfk7KVux2uEF-T9Gyug@mail.gmail.com> (raw)
In-Reply-To: <20181008164026.GD4604@localhost.localdomain>

On 8 October 2018 at 17:40, Kevin Wolf <kwolf@redhat.com> wrote:
> By the way, can you reproduce this with virtio-blk/scsi and an iothread
> in a real QEMU or is it only the test case that fails? In theory, I
> don't see what would prevent QEMU from hanging at shutdown.

I haven't tested, but I suspect this is less likely to
cause a problem, because in a real QEMU run we'll only
kill these threads and cause the memory corruption at
the end of the run when QEMU is exiting anyway. The problem
in the test case is that we kill threads and corrupt memory,
and then continue to use the same process for the next test
in the set, which then crashes later as a result of the
memory corruption.

thanks
-- PMM

  reply	other threads:[~2018-10-08 17:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-05 14:38 [Qemu-devel] [PATCH] tests: Disable test-bdrv-drain Peter Maydell
2018-10-05 14:41 ` Peter Maydell
2018-10-05 16:17   ` Kevin Wolf
2018-10-05 16:54     ` Peter Maydell
2018-10-05 18:09       ` Kevin Wolf
2018-10-08  9:12         ` Peter Maydell
2018-10-08 15:43           ` Peter Maydell
2018-10-08 16:40             ` Kevin Wolf
2018-10-08 17:07               ` Peter Maydell [this message]
2018-10-08 19:53               ` Eric Blake
2018-10-09  9:48                 ` Kevin Wolf
2018-10-09 11:16               ` Paolo Bonzini
2018-11-02 13:33                 ` Peter Maydell
2018-11-04 22:03                   ` Paolo Bonzini
2018-11-05 10:34                     ` Peter Maydell

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='CAFEAcA80vkufJ=hwr5s5i9xFzE1HxZKbfk7KVux2uEF-T9Gyug@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=patches@linaro.org \
    --cc=pbonzini@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 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.