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] 9pfs fixes for 2.10 20170810
Date: Thu, 10 Aug 2017 18:46:46 +0100 [thread overview]
Message-ID: <CAFEAcA8WE21t_SW9JhS=niuMJsei+NENdyUq4MeYdcCMHY=MwA@mail.gmail.com> (raw)
In-Reply-To: <1502380961-16398-1-git-send-email-groug@kaod.org>
On 10 August 2017 at 17:02, Greg Kurz <groug@kaod.org> wrote:
> The following changes since commit b38df311c174c98ef8cce7dec9f46603b083018e:
>
> Merge remote-tracking branch 'remotes/dgibson/tags/ppc-for-2.10-20170809' into staging (2017-08-10 11:12:36 +0100)
>
> are available in the git repository at:
>
> https://github.com/gkurz/qemu.git tags/for-upstream
>
> for you to fetch changes up to 4751fd5328dfcd4fe2f9055728a72a0e3ae56512:
>
> 9pfs: local: fix fchmodat_nofollow() limitations (2017-08-10 14:36:11 +0200)
>
> ----------------------------------------------------------------
> Just a single fix for an annoying regression introduced in 2.9 when fixing
> CVE-2016-9602.
>
> ----------------------------------------------------------------
> Greg Kurz (1):
> 9pfs: local: fix fchmodat_nofollow() limitations
>
> hw/9pfs/9p-local.c | 42 +++++++++++++++++++++++++++++++++++-------
> hw/9pfs/9p-util.h | 24 +++++++++++++++---------
> 2 files changed, 50 insertions(+), 16 deletions(-)
> --
Applied, thanks.
-- PMM
prev parent reply other threads:[~2017-08-10 17:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-10 16:02 [Qemu-devel] [PULL] 9pfs fixes for 2.10 20170810 Greg Kurz
2017-08-10 16:02 ` [Qemu-devel] [PULL] 9pfs: local: fix fchmodat_nofollow() limitations Greg Kurz
2017-08-10 18:17 ` Greg Kurz
2017-08-10 17:46 ` 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='CAFEAcA8WE21t_SW9JhS=niuMJsei+NENdyUq4MeYdcCMHY=MwA@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).