From: Stefan Hajnoczi <stefanha@redhat.com>
To: Max Reitz <mreitz@redhat.com>
Cc: qemu-block@nongnu.org, qemu-devel@nongnu.org,
Kevin Wolf <kwolf@redhat.com>, Fam Zheng <famz@redhat.com>,
Eric Blake <eblake@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 for-2.11] block: Make bdrv_next() keep strong references
Date: Mon, 13 Nov 2017 14:30:09 +0000 [thread overview]
Message-ID: <20171113143009.GD27765@stefanha-x1.localdomain> (raw)
In-Reply-To: <20171110172545.32609-1-mreitz@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1935 bytes --]
On Fri, Nov 10, 2017 at 06:25:45PM +0100, Max Reitz wrote:
> On one hand, it is a good idea for bdrv_next() to return a strong
> reference because ideally nearly every pointer should be refcounted.
> This fixes intermittent failure of iotest 194.
>
> On the other, it is absolutely necessary for bdrv_next() itself to keep
> a strong reference to both the BB (in its first phase) and the BDS (at
> least in the second phase) because when called the next time, it will
> dereference those objects to get a link to the next one. Therefore, it
> needs these objects to stay around until then. Just storing the pointer
> to the next in the iterator is not really viable because that pointer
> might become invalid as well.
>
> Both arguments taken together means we should probably just invoke
> bdrv_ref() and blk_ref() in bdrv_next(). This means we have to assert
> that bdrv_next() is always called from the main loop, but that was
> probably necessary already before this patch and judging from the
> callers, it also looks to actually be the case.
>
> Keeping these strong references means however that callers need to give
> them up if they decide to abort the iteration early. They can do so
> through the new bdrv_next_cleanup() function.
>
> Suggested-by: Kevin Wolf <kwolf@redhat.com>
> Signed-off-by: Max Reitz <mreitz@redhat.com>
> ---
> v2: Instead of keeping the strong reference in bdrv_drain_all_*() only,
> have them for all callers of bdrv_next() [Fam, Kevin]
> (Completely different patch now, so no git-backport-diff included
> here)
> ---
> include/block/block.h | 1 +
> block.c | 3 +++
> block/block-backend.c | 48 ++++++++++++++++++++++++++++++++++++++++++++++--
> block/snapshot.c | 6 ++++++
> migration/block.c | 1 +
> 5 files changed, 57 insertions(+), 2 deletions(-)
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next prev parent reply other threads:[~2017-11-13 14:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-10 17:25 [Qemu-devel] [PATCH v2 for-2.11] block: Make bdrv_next() keep strong references Max Reitz
2017-11-11 0:08 ` Paolo Bonzini
2017-11-13 16:18 ` Max Reitz
2017-11-13 14:30 ` Stefan Hajnoczi [this message]
2017-11-17 16:08 ` Max Reitz
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=20171113143009.GD27765@stefanha-x1.localdomain \
--to=stefanha@redhat.com \
--cc=eblake@redhat.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--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).