From: Fam Zheng <famz@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu-devel@nongnu.org, Kevin Wolf <kwolf@redhat.com>,
qemu-block@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>,
Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH v3 00/16] block: Protect AIO context change with perm API
Date: Wed, 31 May 2017 18:46:04 +0800 [thread overview]
Message-ID: <20170531104604.GD6170@lemon.lan> (raw)
In-Reply-To: <20170531094531.GD15666@stefanha-x1.localdomain>
On Wed, 05/31 10:45, Stefan Hajnoczi wrote:
> On Wed, May 24, 2017 at 10:52:19AM +0800, Fam Zheng wrote:
> > v3: Move blk_set_aio_context to the front of mirror_start_job to avoid
> > accessing target without acquiring its aio context. [Stefan]
> > Use error_free_or_abort in test code. [Stefan]
>
> Please include my Reviewed-bys from the previous revision. That way
> they will be included in the commit log and I don't need to look back at
> previous revisions when you send the next revision.
Yes, sorry for forgetting that.
Fam
prev parent reply other threads:[~2017-05-31 10:46 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-24 2:52 [Qemu-devel] [PATCH v3 00/16] block: Protect AIO context change with perm API Fam Zheng
2017-05-24 2:52 ` [Qemu-devel] [PATCH v3 01/16] block: Define BLK_PERM_AIO_CONTEXT_CHANGE Fam Zheng
2017-05-24 2:52 ` [Qemu-devel] [PATCH v3 02/16] block-backend: Add blk_request_perm Fam Zheng
2017-05-31 9:41 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2017-05-24 2:52 ` [Qemu-devel] [PATCH v3 03/16] blockjob: Add BLK_PERM_AIO_CONTEXT_CHANGE shared perm on bs Fam Zheng
2017-05-24 2:52 ` [Qemu-devel] [PATCH v3 04/16] blockjob: Allow aio context change on intermediate nodes Fam Zheng
2017-05-24 2:52 ` [Qemu-devel] [PATCH v3 05/16] block: Propagate BLK_PERM_AIO_CONTEXT_CHANGE down the graph Fam Zheng
2017-05-24 2:52 ` [Qemu-devel] [PATCH v3 06/16] backup: Request BLK_PERM_AIO_CONTEXT_CHANGE on target Fam Zheng
2017-06-07 12:13 ` Fam Zheng
2017-05-24 2:52 ` [Qemu-devel] [PATCH v3 07/16] backup: Do initial aio context move of target via BB interface Fam Zheng
2017-05-24 2:52 ` [Qemu-devel] [PATCH v3 08/16] mirror: Request aio context change permission on target Fam Zheng
2017-05-24 2:52 ` [Qemu-devel] [PATCH v3 09/16] commit: Allow aio context change on s->base Fam Zheng
2017-05-24 2:52 ` [Qemu-devel] [PATCH v3 10/16] mirror: Do initial aio context move of target via BB interface Fam Zheng
2017-05-31 9:43 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2017-05-24 2:52 ` [Qemu-devel] [PATCH v3 11/16] virtio-scsi: Request BLK_PERM_AIO_CONTEXT_CHANGE for dataplane Fam Zheng
2017-06-07 8:11 ` Fam Zheng
2017-05-24 2:52 ` [Qemu-devel] [PATCH v3 12/16] virtio-blk: " Fam Zheng
2017-05-24 2:52 ` [Qemu-devel] [PATCH v3 13/16] blk: fix aio context loss on media change Fam Zheng
2017-05-24 2:52 ` [Qemu-devel] [PATCH v3 14/16] nbd: Allow BLK_PERM_AIO_CONTEXT_CHANGE on BB Fam Zheng
2017-05-24 2:52 ` [Qemu-devel] [PATCH v3 15/16] block: Add perm assertion on blk_set_aio_context Fam Zheng
2017-05-24 2:52 ` [Qemu-devel] [PATCH v3 16/16] tests: Add test case for BLK_PERM_AIO_CONTEXT_CHANGE Fam Zheng
2017-05-31 9:45 ` [Qemu-devel] [Qemu-block] [PATCH v3 00/16] block: Protect AIO context change with perm API Stefan Hajnoczi
2017-05-31 10:46 ` Fam Zheng [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=20170531104604.GD6170@lemon.lan \
--to=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--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 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.