From: Fam Zheng <famz@redhat.com>
To: pbonzini@redhat.com
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL v3 00/23] Docker and block patches
Date: Wed, 14 Jun 2017 19:04:01 +0800 [thread overview]
Message-ID: <20170614110401.GA3610@lemon.lan> (raw)
In-Reply-To: <CAFEAcA-myF7ZP19hcfJpJ2j8BBkvFyJofecp7v39FJJ10DO10w@mail.gmail.com>
On Mon, 06/12 19:26, Peter Maydell wrote:
> On 8 June 2017 at 12:56, Fam Zheng <famz@redhat.com> wrote:
> > The following changes since commit 64175afc695c0672876fbbfc31b299c86d562cb4:
> >
> > arm_gicv3: Fix ICC_BPR1 reset value when EL3 not implemented (2017-06-07 17:21:44 +0100)
> >
> > are available in the git repository at:
> >
> > git://github.com/famz/qemu.git tags/docker-and-block-pull-request
> >
> > for you to fetch changes up to 383226d7f90e83fd2b4ea5fbedf67bd9d3173221:
> >
> > block: make accounting thread-safe (2017-06-08 19:09:23 +0800)
> >
> > ----------------------------------------------------------------
> >
> > v3: Update Paolo's series to fix make check on OSX.
> >
> > ----------------------------------------------------------------
>
> This still fails on OSX:
>
> GTESTER tests/test-blockjob
> qemu: qemu_mutex_lock: Invalid argument
>
> The backtrace is different from last time:
>
> * thread #1: tid = 0x7f066a, 0x00007fffc611ad42
> libsystem_kernel.dylib`__pthread_kill + 10, queue =
> 'com.apple.main-thread', stop reason = signal SIGABRT
> * frame #0: 0x00007fffc611ad42 libsystem_kernel.dylib`__pthread_kill + 10
> frame #1: 0x00007fffc6208457 libsystem_pthread.dylib`pthread_kill + 90
> frame #2: 0x00007fffc6080420 libsystem_c.dylib`abort + 129
> frame #3: 0x00000001000c1265
> test-blockjob`error_exit(err=<unavailable>, msg=<unavailable>) + 53 at
> qemu-thread-posix.c:36
> frame #4: 0x00000001000c1327
> test-blockjob`qemu_mutex_lock(mutex=<unavailable>) + 151 at
> qemu-thread-posix.c:63
> frame #5: 0x000000010005eef7
> test-blockjob`bdrv_do_release_matching_dirty_bitmap [inlined]
> bdrv_dirty_bitmaps_lock(bs=0x0000000101806000) + 39 at
> dirty-bitmap.c:58
> frame #6: 0x000000010005eee7
> test-blockjob`bdrv_do_release_matching_dirty_bitmap(bs=0x0000000101806000,
> bitmap=0x0000000000000000, only_named=true) + 23 at dirty-bitmap.c:349
> frame #7: 0x000000010000962d test-blockjob`bdrv_delete [inlined]
> bdrv_close(bs=0x0000000101806000) + 32 at block.c:3042
> frame #8: 0x000000010000960d
> test-blockjob`bdrv_delete(bs=0x0000000101806000) + 61 at block.c:3229
> frame #9: 0x0000000100043da2
> test-blockjob`blk_remove_bs(blk=0x0000000100d0a7d0) + 98 at
> block-backend.c:607
> frame #10: 0x0000000100001318 test-blockjob`test_job_ids [inlined]
> destroy_blk(blk=0x0000000100d0a7d0) + 29 at test-blockjob.c:83
> frame #11: 0x00000001000012fb test-blockjob`test_job_ids + 411 at
> test-blockjob.c:140
> frame #12: 0x000000010070d91d
> libglib-2.0.0.dylib`g_test_run_suite_internal + 626
> frame #13: 0x000000010070dae1
> libglib-2.0.0.dylib`g_test_run_suite_internal + 1078
> frame #14: 0x000000010070d198 libglib-2.0.0.dylib`g_test_run_suite + 266
> frame #15: 0x0000000100001148
> test-blockjob`main(argc=<unavailable>, argv=<unavailable>) + 88 at
> test-blockjob.c:152
> frame #16: 0x00007fffc5fec235 libdyld.dylib`start + 1
> frame #17: 0x00007fffc5fec235 libdyld.dylib`start + 1
Paolo: missing "qemu_mutex_init(&bs->dirty_bitmap_mutex)" in bdrv_new()?
(Any idea what is the easiest way to add a (VM|container|baremetal) OSX build
env to patchew?)
Fam
next prev parent reply other threads:[~2017-06-14 11:04 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-08 11:56 [Qemu-devel] [PULL v3 00/23] Docker and block patches Fam Zheng
2017-06-08 11:56 ` [Qemu-devel] [PULL v3 01/23] docker: Run tests with current user Fam Zheng
2017-06-08 11:56 ` [Qemu-devel] [PULL v3 02/23] docker: Add bzip2 and hostname to fedora image Fam Zheng
2017-06-08 11:56 ` [Qemu-devel] [PULL v3 03/23] docker: Add libaio " Fam Zheng
2017-06-08 11:56 ` [Qemu-devel] [PULL v3 04/23] docker: Add flex and bison to centos6 image Fam Zheng
2017-06-08 11:56 ` [Qemu-devel] [PULL v3 05/23] block: access copy_on_read with atomic ops Fam Zheng
2017-06-08 11:56 ` [Qemu-devel] [PULL v3 06/23] block: access quiesce_counter " Fam Zheng
2017-06-08 11:56 ` [Qemu-devel] [PULL v3 07/23] block: access io_limits_disabled " Fam Zheng
2017-06-08 11:56 ` [Qemu-devel] [PULL v3 08/23] block: access serialising_in_flight " Fam Zheng
2017-06-08 11:56 ` [Qemu-devel] [PULL v3 09/23] block: access wakeup " Fam Zheng
2017-06-08 11:56 ` [Qemu-devel] [PULL v3 10/23] block: access io_plugged " Fam Zheng
2017-06-08 11:56 ` [Qemu-devel] [PULL v3 11/23] throttle-groups: only start one coroutine from drained_begin Fam Zheng
2017-06-08 11:56 ` [Qemu-devel] [PULL v3 12/23] throttle-groups: do not use qemu_co_enter_next Fam Zheng
2017-06-08 11:56 ` [Qemu-devel] [PULL v3 13/23] throttle-groups: protect throttled requests with a CoMutex Fam Zheng
2017-06-08 11:56 ` [Qemu-devel] [PULL v3 14/23] util: add stats64 module Fam Zheng
2017-06-08 11:56 ` [Qemu-devel] [PULL v3 15/23] block: use Stat64 for wr_highest_offset Fam Zheng
2017-06-08 11:56 ` [Qemu-devel] [PULL v3 16/23] block: access write_gen with atomics Fam Zheng
2017-06-08 11:56 ` [Qemu-devel] [PULL v3 17/23] block: protect tracked_requests and flush_queue with reqs_lock Fam Zheng
2017-06-08 11:56 ` [Qemu-devel] [PULL v3 18/23] block: introduce dirty_bitmap_mutex Fam Zheng
2017-06-16 0:12 ` Fam Zheng
2017-06-08 11:56 ` [Qemu-devel] [PULL v3 19/23] migration/block: reset dirty bitmap before reading Fam Zheng
2017-06-08 11:56 ` [Qemu-devel] [PULL v3 20/23] block: protect modification of dirty bitmaps with a mutex Fam Zheng
2017-06-08 11:56 ` [Qemu-devel] [PULL v3 21/23] block: introduce block_account_one_io Fam Zheng
2017-06-08 11:56 ` [Qemu-devel] [PULL v3 22/23] block: split BlockAcctStats creation and setup Fam Zheng
2017-06-08 11:56 ` [Qemu-devel] [PULL v3 23/23] block: make accounting thread-safe Fam Zheng
2017-06-12 18:26 ` [Qemu-devel] [PULL v3 00/23] Docker and block patches Peter Maydell
2017-06-14 11:04 ` Fam Zheng [this message]
2017-06-14 11:22 ` Paolo Bonzini
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=20170614110401.GA3610@lemon.lan \
--to=famz@redhat.com \
--cc=pbonzini@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).