qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Markus Armbruster <armbru@redhat.com>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v2 0/2] Two buffer overruns in device assignment
Date: Mon, 24 Feb 2014 10:49:10 -0700	[thread overview]
Message-ID: <1393264150.9111.119.camel@ul30vt.home> (raw)
In-Reply-To: <CAFEAcA_sqf_CwsOpkLYk0M9A_Kn9_Uv9-8g72Q8DScjSKWc6_A@mail.gmail.com>

On Mon, 2014-02-24 at 17:40 +0000, Peter Maydell wrote:
> On 24 February 2014 17:39, Alex Williamson <alex.williamson@redhat.com> wrote:
> > On Mon, 2014-02-24 at 14:51 +0100, Markus Armbruster wrote:
> >> v2:
> >> * Treat readlink() filling buffer as error (Alex)
> >> * Use sizeof() rather than PATH_MAX (Peter)
> >> * PATCH 2/2 unchanged
> >>
> >> Markus Armbruster (2):
> >>   vfio: Fix overrun after readlink() fills buffer completely
> >>   pci-assign: Fix potential read beyond buffer on -EBUSY
> >>
> >>  hw/i386/kvm/pci-assign.c | 1 +
> >>  hw/misc/vfio.c           | 6 +++---
> >>  2 files changed, 4 insertions(+), 3 deletions(-)
> >
> > For both:
> >
> > Acked-by: Alex Williamson <alex.williamson@redhat.com>
> >
> > Peter, if you want to grab these directly, feel free, otherwise I can
> > shepherd them in through vfio.  Thanks,
> 
> Via vfio would be easiest for me.

Ok

      reply	other threads:[~2014-02-24 17:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-24 13:51 [Qemu-devel] [PATCH v2 0/2] Two buffer overruns in device assignment Markus Armbruster
2014-02-24 13:51 ` [Qemu-devel] [PATCH v2 1/2] vfio: Fix overrun after readlink() fills buffer completely Markus Armbruster
2014-02-24 13:51 ` [Qemu-devel] [PATCH v2 2/2] pci-assign: Fix potential read beyond buffer on -EBUSY Markus Armbruster
2014-02-24 17:39 ` [Qemu-devel] [PATCH v2 0/2] Two buffer overruns in device assignment Alex Williamson
2014-02-24 17:40   ` Peter Maydell
2014-02-24 17:49     ` Alex Williamson [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=1393264150.9111.119.camel@ul30vt.home \
    --to=alex.williamson@redhat.com \
    --cc=armbru@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).