From: Max Reitz <mreitz@redhat.com>
To: "sochin.jiang" <sochin.jiang@huawei.com>, kwolf@redhat.com
Cc: qemu-block@nongnu.org, qemu-devel@nongnu.org,
eric.fangyi@huawei.com, subo7@huawei.com, xieyingtai@huawei.com,
lina.lulina@huawei.com, zhangshuai13@huawei.com,
lizhengui@huawei.com
Subject: Re: [Qemu-devel] [PATCH] mirror: fix the inconsistent AioContext problem in the backing BDSs during mirroring.
Date: Thu, 29 Jun 2017 00:33:47 +0200 [thread overview]
Message-ID: <d2c26bda-b166-cc2b-8596-ad48783e7e7c@redhat.com> (raw)
In-Reply-To: <1498475064-39816-1-git-send-email-sochin.jiang@huawei.com>
[-- Attachment #1: Type: text/plain, Size: 1876 bytes --]
On 2017-06-26 13:04, sochin.jiang wrote:
> From: "sochin.jiang" <sochin.jiang@huawei.com>
>
> mirror_complete opens the backings, BDSs of the new open backings should have a
> same AioContext with the top when using iothreads, fix the code to guarantee this,
> also avoiding unexpected qemu exit(assert fails in bdrv_attach_child).
Thanks! The functional change looks good to me. I'll see to add an
iotest to cover this case.
Some notes: There shouldn't be any spaces at the front of these lines,
and every line should be limited to 72 characters.
Also, the commit message should not end in a full stop (and it's good to
keep it short).
I've reworded a bit of the commit message (and shortened the title*) and
applied it to my block branch:
https://github.com/XanClic/qemu/commits/block
Max
[1] I've shortened it to "mirror: Fix inconsistent backing AioContext
for after mirroring". I usually try to fit the title into 50 characters
(because that's what the default vim highlighting is proposing...), so
for reference, I would have made it something like "block: Align backing
BDS's AioContext with overlay" -- if it had been my patch. Since it was
yours, I'm fine with commit titles longer than 50 characters (although
they really should not exceed 72).
> Signed-off-by: sochin.jiang <sochin.jiang@huawei.com>
> ---
> block.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/block.c b/block.c
> index 6943962..b312fe6 100644
> --- a/block.c
> +++ b/block.c
> @@ -2185,6 +2185,7 @@ int bdrv_open_backing_file(BlockDriverState *bs, QDict *parent_options,
> ret = -EINVAL;
> goto free_exit;
> }
> + bdrv_set_aio_context(backing_hd, bdrv_get_aio_context(bs));
>
> /* Hook up the backing file link; drop our reference, bs owns the
> * backing_hd reference now */
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 498 bytes --]
next prev parent reply other threads:[~2017-06-28 22:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-26 11:04 [Qemu-devel] [PATCH] mirror: fix the inconsistent AioContext problem in the backing BDSs during mirroring sochin.jiang
2017-06-28 22:33 ` Max Reitz [this message]
2017-06-29 1:12 ` sochin.jiang
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=d2c26bda-b166-cc2b-8596-ad48783e7e7c@redhat.com \
--to=mreitz@redhat.com \
--cc=eric.fangyi@huawei.com \
--cc=kwolf@redhat.com \
--cc=lina.lulina@huawei.com \
--cc=lizhengui@huawei.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=sochin.jiang@huawei.com \
--cc=subo7@huawei.com \
--cc=xieyingtai@huawei.com \
--cc=zhangshuai13@huawei.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).