From: Peter Maydell <peter.maydell@linaro.org>
To: Max Reitz <mreitz@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Qemu-block <qemu-block@nongnu.org>
Subject: Re: [PULL 0/1] Block patch for 6.0-rc3
Date: Tue, 13 Apr 2021 22:11:40 +0100 [thread overview]
Message-ID: <CAFEAcA8L7Ob4GQrQ9Dwyxw1qNNbTGsrPkhPho8PnsbHBFEwZpg@mail.gmail.com> (raw)
In-Reply-To: <20210413133903.545695-1-mreitz@redhat.com>
On Tue, 13 Apr 2021 at 14:39, Max Reitz <mreitz@redhat.com> wrote:
>
> The following changes since commit dce628a97fde2594f99d738883a157f05aa0a14f:
>
> Merge remote-tracking branch 'remotes/dg-gitlab/tags/ppc-for-6.0-20210412' into staging (2021-04-13 13:05:07 +0100)
>
> are available in the Git repository at:
>
> https://github.com/XanClic/qemu.git tags/pull-block-2021-04-13
>
> for you to fetch changes up to 0267101af64292c9a84fd9319a763ddfbce9ddc7:
>
> block/nbd: fix possible use after free of s->connect_thread (2021-04-13 15:35:12 +0200)
>
> (This is the patch for which Vladimir has sent a pull request yesterday.)
>
> ----------------------------------------------------------------
> Block patches for 6.0-rc3:
> - Use-after-free fix for block/nbd.c
>
> ----------------------------------------------------------------
> Vladimir Sementsov-Ogievskiy (1):
> block/nbd: fix possible use after free of s->connect_thread
Applied, thanks.
Please update the changelog at https://wiki.qemu.org/ChangeLog/6.0
for any user-visible changes.
-- PMM
prev parent reply other threads:[~2021-04-13 21:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-13 13:39 [PULL 0/1] Block patch for 6.0-rc3 Max Reitz
2021-04-13 13:39 ` [PULL 1/1] block/nbd: fix possible use after free of s->connect_thread Max Reitz
2021-04-13 21:11 ` Peter Maydell [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=CAFEAcA8L7Ob4GQrQ9Dwyxw1qNNbTGsrPkhPho8PnsbHBFEwZpg@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.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).