From: John Snow <jsnow@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>, qemu-block@nongnu.org
Cc: qemu-devel@nongnu.org, mreitz@redhat.com
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH 0/2] commit: Fix use after free in completion
Date: Fri, 2 Jun 2017 19:28:19 -0400 [thread overview]
Message-ID: <714c3518-599c-ca95-6fb4-ab639e486479@redhat.com> (raw)
In-Reply-To: <1496437930-12654-1-git-send-email-kwolf@redhat.com>
On 06/02/2017 05:12 PM, Kevin Wolf wrote:
> Kevin Wolf (2):
> commit: Fix use after free in completion
> qemu-iotests: Test automatic commit job cancel on hot unplug
>
> block/commit.c | 7 +++++++
> tests/qemu-iotests/040 | 35 +++++++++++++++++++++++++++++++++--
> tests/qemu-iotests/040.out | 4 ++--
> 3 files changed, 42 insertions(+), 4 deletions(-)
>
Reviewed-by: John Snow <jsnow@redhat.com>
prev parent reply other threads:[~2017-06-02 23:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-02 21:12 [Qemu-devel] [PATCH 0/2] commit: Fix use after free in completion Kevin Wolf
2017-06-02 21:12 ` [Qemu-devel] [PATCH 1/2] " Kevin Wolf
2017-06-09 11:45 ` Kevin Wolf
2017-06-02 21:12 ` [Qemu-devel] [PATCH 2/2] qemu-iotests: Test automatic commit job cancel on hot unplug Kevin Wolf
2017-06-02 23:28 ` John Snow [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=714c3518-599c-ca95-6fb4-ab639e486479@redhat.com \
--to=jsnow@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).