From: Kevin Wolf <kwolf@redhat.com>
To: Anton Kuchin <antonkuchin@yandex-team.ru>
Cc: yc-core@yandex-team.ru, qemu-devel@nongnu.org,
qemu-block@nongnu.org, Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] block: remove bs from lists before closing
Date: Tue, 7 May 2019 10:53:00 +0200 [thread overview]
Message-ID: <20190507085300.GC5808@localhost.localdomain> (raw)
In-Reply-To: <20190507081256.27599-1-antonkuchin@yandex-team.ru>
Am 07.05.2019 um 10:12 hat Anton Kuchin geschrieben:
> Close involves flush that can be performed asynchronously and bs
> must be protected from being referenced before it is deleted.
>
> Signed-off-by: Anton Kuchin <antonkuchin@yandex-team.ru>
Thanks, applied to the block branch.
Kevin
prev parent reply other threads:[~2019-05-07 8:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-07 8:12 [Qemu-devel] [PATCH] block: remove bs from lists before closing Anton Kuchin
2019-05-07 8:53 ` Kevin Wolf [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=20190507085300.GC5808@localhost.localdomain \
--to=kwolf@redhat.com \
--cc=antonkuchin@yandex-team.ru \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=yc-core@yandex-team.ru \
/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).