From: Jeff Cody <jcody@redhat.com>
To: qemu-devel@nongnu.org
Cc: qemu-block@nongnu.org, mreitz@redhat.com, stefanha@redhat.com,
famz@redhat.com, pbonzini@redhat.com, kwolf@redhat.com
Subject: Re: [Qemu-devel] [PATCH v3 for-2.11 0/4] Fix segfault in blockjob race condition
Date: Tue, 21 Nov 2017 11:59:56 -0500 [thread overview]
Message-ID: <20171121165956.GN5399@localhost.localdomain> (raw)
In-Reply-To: <cover.1511278397.git.jcody@redhat.com>
On Tue, Nov 21, 2017 at 10:38:49AM -0500, Jeff Cody wrote:
> Changes from v2 -> v3:
> -----------------------
>
> Patch 1: Updated commit message to include why immediate cancel is
> ok to remove (Thanks Paolo)
>
> Dropped useless hunk (Thanks Stefan)
>
>
> Patch 2: Use correct atomic primitives, and document implicit
> assumptions (Thanks Stefan, Paolo)
>
> Fix spelling in commit message (Thanks Eric)
>
> Patch 3/4: Unchanged.
>
>
> Changes from v1 -> v2:
> -----------------------
>
> Patch 1: Updated docs in blockjob_int.h (Thanks Stefan)
>
> Patch 2/3: Squashed, and used const char * to hold the __func__ name of
> the original scheduler (Thanks Paolo)
>
> Patch 4: Unchanged.
>
> Patch 5: Dropped qcow format for the test, it was so slow the test times
> out, and it doesn't add any new dimension to the test.
>
>
> # git-backport-diff -r qemu/master.. -u github/bz1508708
>
> 001/4:[0003] [FC] 'blockjob: do not allow coroutine double entry or entry-after-completion'
> 002/4:[down] 'coroutine: abort if we try to schedule or enter a pending coroutine'
> 003/4:[----] [--] 'qemu-iotests: add option in common.qemu for mismatch only'
> 004/4:[0002] [FC] 'qemu-iotest: add test for blockjob coroutine race condition'
>
>
> This series fixes a race condition segfault when using iothreads with
> blockjobs.
>
> The qemu iotest in this series is a reproducer, as is the reproducer
> script attached in this bug report:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1508708
>
> There are two additional patches to try and catch this sort of scenario
> with an abort, before a segfault or memory corruption occurs.
>
>
> Jeff Cody (4):
> blockjob: do not allow coroutine double entry or
> entry-after-completion
> coroutine: abort if we try to schedule or enter a pending coroutine
> qemu-iotests: add option in common.qemu for mismatch only
> qemu-iotest: add test for blockjob coroutine race condition
>
> blockjob.c | 7 ++-
> include/block/blockjob_int.h | 3 +-
> include/qemu/coroutine_int.h | 6 +++
> tests/qemu-iotests/200 | 99 ++++++++++++++++++++++++++++++++++++++++++
> tests/qemu-iotests/200.out | 14 ++++++
> tests/qemu-iotests/common.qemu | 8 +++-
> tests/qemu-iotests/group | 1 +
> util/async.c | 13 ++++++
> util/qemu-coroutine-sleep.c | 12 +++++
> util/qemu-coroutine.c | 13 ++++++
> 10 files changed, 172 insertions(+), 4 deletions(-)
> create mode 100755 tests/qemu-iotests/200
> create mode 100644 tests/qemu-iotests/200.out
>
> --
> 2.9.5
>
Thanks,
Made the change suggested by Stefan and Paolo.
Applied to my block branch:
git://github.com/codyprime/qemu-kvm-jtc block
-Jeff
prev parent reply other threads:[~2017-11-21 17:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-21 15:38 [Qemu-devel] [PATCH v3 for-2.11 0/4] Fix segfault in blockjob race condition Jeff Cody
2017-11-21 15:38 ` [Qemu-devel] [PATCH v3 for-2.11 1/4] blockjob: do not allow coroutine double entry or entry-after-completion Jeff Cody
2017-11-21 15:38 ` [Qemu-devel] [PATCH v3 for-2.11 2/4] coroutine: abort if we try to schedule or enter a pending coroutine Jeff Cody
2017-11-21 16:39 ` Stefan Hajnoczi
2017-11-21 15:38 ` [Qemu-devel] [PATCH v3 for-2.11 3/4] qemu-iotests: add option in common.qemu for mismatch only Jeff Cody
2017-11-21 15:38 ` [Qemu-devel] [PATCH v3 for-2.11 4/4] qemu-iotest: add test for blockjob coroutine race condition Jeff Cody
2017-11-21 16:41 ` [Qemu-devel] [PATCH v3 for-2.11 0/4] Fix segfault in blockjob " Stefan Hajnoczi
2017-11-21 16:59 ` Jeff Cody [this message]
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=20171121165956.GN5399@localhost.localdomain \
--to=jcody@redhat.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).