From: John Snow <jsnow@redhat.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, libvir-list@redhat.com,
vsementsov@virtuozzo.com, qemu-block@nongnu.org,
mreitz@redhat.com
Subject: Re: [Qemu-devel] [libvirt] [PATCH v3] qapi: add dirty-bitmaps to query-named-block-nodes result
Date: Thu, 18 Jul 2019 13:32:27 -0400 [thread overview]
Message-ID: <35d7845e-8262-ca75-d08e-a3d590cf1e2f@redhat.com> (raw)
In-Reply-To: <156344522945.10055.16902416959495283361@c4a48874b076>
On 7/18/19 6:20 AM, no-reply@patchew.org wrote:
> PASS 17 test-bdrv-drain /bdrv-drain/graph-change/drain_all
> =================================================================
> ==10263==ERROR: AddressSanitizer: heap-use-after-free on address 0x61200002c1f0 at pc 0x555fd5bd7cb6 bp 0x7f3e853b8680 sp 0x7f3e853b8678
> WRITE of size 1 at 0x61200002c1f0 thread T5
> ==10262==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
> #0 0x555fd5bd7cb5 in aio_notify /tmp/qemu-test/src/util/async.c:351:9
> #1 0x555fd5bd98eb in qemu_bh_schedule /tmp/qemu-test/src/util/async.c:167:9
> #2 0x555fd5bdcaf0 in aio_co_schedule /tmp/qemu-test/src/util/async.c:464:5
I'm fairly certain that this isn't related to this patch.
next prev parent reply other threads:[~2019-07-18 17:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-17 17:39 [Qemu-devel] [PATCH v3] qapi: add dirty-bitmaps to query-named-block-nodes result John Snow
2019-07-17 17:47 ` John Snow
2019-07-17 19:13 ` Eric Blake
2019-07-17 19:21 ` John Snow
2019-07-17 20:05 ` Eric Blake
2019-07-17 20:32 ` John Snow
2019-07-17 21:12 ` John Snow
2019-07-18 10:20 ` [Qemu-devel] [libvirt] " no-reply
2019-07-18 17:32 ` John Snow [this message]
2019-07-24 4:47 ` [Qemu-devel] " Markus Armbruster
2019-07-24 22:06 ` John Snow
2019-07-25 6:06 ` Markus Armbruster
2019-07-25 16:13 ` 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=35d7845e-8262-ca75-d08e-a3d590cf1e2f@redhat.com \
--to=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=libvir-list@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.com \
/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).