From: "Michael S. Tsirkin" <mst@redhat.com>
To: Isaku Yamahata <yamahata@valinux.co.jp>
Cc: Jan Kiszka <jan.kiszka@siemens.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v2] pci: Common overflow prevention
Date: Fri, 29 Jul 2011 08:03:01 +0300 [thread overview]
Message-ID: <20110729050301.GA9057@redhat.com> (raw)
In-Reply-To: <20110729010143.GI14976@valinux.co.jp>
On Fri, Jul 29, 2011 at 10:01:43AM +0900, Isaku Yamahata wrote:
> On Thu, Jul 28, 2011 at 11:40:21AM +0300, Michael S. Tsirkin wrote:
> > I don't see a problem with this, but could you please clarify when does
> > this happen? I think this is only possible for a pci device
> > behind an express root. If so, this belongs in pcie_host.c
> >
> > I'd also like this info to be recorded in the commit log.
>
> >From 1dd598fd35d4e988dc51487829ed66208ca89021 Mon Sep 17 00:00:00 2001
> Message-Id: <1dd598fd35d4e988dc51487829ed66208ca89021.1311901239.git.yamahata@valinux.co.jp>
> From: Isaku Yamahata <yamahata@valinux.co.jp>
> Date: Fri, 29 Jul 2011 09:52:45 +0900
> Subject: [PATCH] pcie_host: limit check of pcie_mmcfg_data_write/read
>
> This patch adds the check where the offset in the configuration space
> is in its configuration size.
>
> MMCFG area allows access of pcie configuration space to be in
> offset [0, 4K).
> At the same time, conventional pci devices whose configuration space size
> is 256 bytes can be behind pcie-to-pci bridge.
> The access whose offset is [256, 4K) should have no effect
> on the conventional pci device
> Add the limit check and ignore such accesses.
>
> Signed-off-by: Isaku Yamahata <yamahata@valinux.co.jp>
I tweaked the commit log and applied this.
Thanks!
prev parent reply other threads:[~2011-07-29 5:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-21 16:50 [Qemu-devel] [PATCH] pci: Common overflow prevention Jan Kiszka
2011-07-22 5:32 ` Michael S. Tsirkin
2011-07-22 9:05 ` [Qemu-devel] [PATCH v2] " Jan Kiszka
2011-07-25 15:12 ` Michael S. Tsirkin
2011-07-25 15:17 ` Michael S. Tsirkin
2011-07-25 15:18 ` Jan Kiszka
2011-07-28 7:23 ` Isaku Yamahata
2011-07-28 8:40 ` Michael S. Tsirkin
2011-07-28 12:50 ` Isaku Yamahata
2011-07-29 1:01 ` Isaku Yamahata
2011-07-29 5:03 ` Michael S. Tsirkin [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=20110729050301.GA9057@redhat.com \
--to=mst@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=qemu-devel@nongnu.org \
--cc=yamahata@valinux.co.jp \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.