qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: P J P <ppandit@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Greg Kurz <groug@kaod.org>,
	Qemu Developers <qemu-devel@nongnu.org>,
	"Michael S. Tsirkin" <mtsirkin@redhat.com>,
	Felix Wilhelm <fwilhelm@ernw.de>,
	"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PATCH] 9pfs: add check for relative path
Date: Mon, 22 Aug 2016 15:37:08 +0530 (IST)	[thread overview]
Message-ID: <alpine.LFD.2.20.1608221532590.21756@wniryva> (raw)
In-Reply-To: <CAFEAcA9sb=XhfJ0C=DP8+NCJ9JTNmyq8fEfKkqMj=YTd_b0BDA@mail.gmail.com>

  Hello Peter, all

+-- On Mon, 22 Aug 2016, Peter Maydell wrote --+
| Opinions welcome on whether we need to hold 2.7 for this bug.

  I'm going through the VirtFS details to figure out a best fix for this 
issue. Nonetheless, IMO we need not hold 2.7 release for this bug.

Thank you.
--
Prasad J Pandit / Red Hat Product Security Team
47AF CE69 3A90 54AA 9045 1053 DD13 3D32 FE5B 041F

  reply	other threads:[~2016-08-22 10:07 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-11  5:13 [Qemu-devel] [PATCH] 9pfs: add check for relative path P J P
2016-08-11  6:17 ` no-reply
2016-08-11  6:27   ` Fam Zheng
2016-08-18 16:55     ` Greg Kurz
2016-08-11  6:31 ` Aneesh Kumar K.V
2016-08-18 15:19   ` Greg Kurz
2016-08-18 17:06 ` Greg Kurz
2016-08-19 14:55 ` Peter Maydell
2016-08-19 15:14   ` Peter Maydell
2016-08-19 16:37     ` Greg Kurz
2016-08-19 17:03       ` Peter Maydell
2016-08-19 17:30         ` Greg Kurz
2016-08-22  9:23           ` Peter Maydell
2016-08-22 10:07             ` P J P [this message]
2016-08-22 15:02             ` Michael S. Tsirkin
2016-08-22 15:07               ` Peter Maydell
2016-08-22 14:14         ` Michael S. Tsirkin
2016-08-19 16:24   ` Greg Kurz

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=alpine.LFD.2.20.1608221532590.21756@wniryva \
    --to=ppandit@redhat.com \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=fwilhelm@ernw.de \
    --cc=groug@kaod.org \
    --cc=mtsirkin@redhat.com \
    --cc=peter.maydell@linaro.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).