From: Peter Maydell <peter.maydell@linaro.org>
To: Greg Kurz <groug@kaod.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL 0/1] 9p fixes for v3.1.0-rc2
Date: Tue, 20 Nov 2018 13:14:38 +0000 [thread overview]
Message-ID: <CAFEAcA-wU0TB2=kb_WHp=gWpZ3edEQj4umeqO-ExKnN4oM9kvg@mail.gmail.com> (raw)
In-Reply-To: <20181120120326.30879-1-groug@kaod.org>
On 20 November 2018 at 12:03, Greg Kurz <groug@kaod.org> wrote:
> The following changes since commit 3c035a41dca808f096a128fe2b62d849fe638a25:
>
> Merge remote-tracking branch 'remotes/huth-gitlab/tags/pull-request-2018-11-20' into staging (2018-11-20 10:56:57 +0000)
>
> are available in the Git repository at:
>
> https://github.com/gkurz/qemu.git tags/for-upstream
>
> for you to fetch changes up to 5b3c77aa581ebb215125c84b0742119483571e55:
>
> 9p: take write lock on fid path updates (CVE-2018-19364) (2018-11-20 13:00:35 +0100)
>
> ----------------------------------------------------------------
> Fixes yet another use-after-free issue that could be triggered by a
> misbehaving guest. This is a follow-up to commit:
>
> commit 5b76ef50f62079a2389ba28cacaf6cce68b1a0ed
> Author: Greg Kurz <groug@kaod.org>
> Date: Wed Nov 7 01:00:04 2018 +0100
>
> 9p: write lock path in v9fs_co_open2()
>
> ----------------------------------------------------------------
> Greg Kurz (1):
> 9p: take write lock on fid path updates (CVE-2018-19364)
>
Applied, thanks.
-- PMM
prev parent reply other threads:[~2018-11-20 13:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-20 12:03 [Qemu-devel] [PULL 0/1] 9p fixes for v3.1.0-rc2 Greg Kurz
2018-11-20 12:03 ` [Qemu-devel] [PULL 1/1] 9p: take write lock on fid path updates (CVE-2018-19364) Greg Kurz
2018-11-20 13:14 ` 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='CAFEAcA-wU0TB2=kb_WHp=gWpZ3edEQj4umeqO-ExKnN4oM9kvg@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=groug@kaod.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).