From: Will Deacon <will.deacon@arm.com>
To: "G. Campana" <gcampana+kvm@quarkslab.com>
Cc: kvm@vger.kernel.org, andre.przywara@arm.com
Subject: Re: [PATCH 0/7] kvmtool: fix virtio 9p vulnerabilities
Date: Tue, 8 Nov 2016 02:39:54 +0000 [thread overview]
Message-ID: <20161108023954.GY20591@arm.com> (raw)
In-Reply-To: <1476806551-9646-1-git-send-email-gcampana+kvm@quarkslab.com>
On Tue, Oct 18, 2016 at 06:02:31PM +0200, G. Campana wrote:
> This patch series should fix different vulnerabilities found in virtio 9p
> (http://www.spinics.net/lists/kvm/msg130505.html), but it definitely needs some
> testing. By the way, the very same path traversal vulnerability was also found
> in Qemu in August: http://www.openwall.com/lists/oss-security/2016/08/30/1
> and the path traversal fix looks quite similar.
I had a quick look through these and they're mostly ok, modulo the comments
I've made. When you send v2, please write a commit message for each patch,
as I can't merge them without that. You also need to add your Signed-off-by
to each one.
Thanks,
Will
next prev parent reply other threads:[~2016-11-08 2:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 16:02 [PATCH 0/7] kvmtool: fix virtio 9p vulnerabilities G. Campana
2016-11-08 2:39 ` Will Deacon [this message]
2016-11-10 15:26 ` G. Campana
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=20161108023954.GY20591@arm.com \
--to=will.deacon@arm.com \
--cc=andre.przywara@arm.com \
--cc=gcampana+kvm@quarkslab.com \
--cc=kvm@vger.kernel.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).