From: Isaku Yamahata <yamahata@valinux.co.jp>
To: Ken CC <ken.ccao@gmail.com>
Cc: mtosatti@redhat.com, qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] [PATCH 2/2] pci init: Check if devfn exceeding the max devices number supported on bus
Date: Tue, 24 Aug 2010 11:18:11 +0900 [thread overview]
Message-ID: <20100824021811.GH20428@valinux.co.jp> (raw)
In-Reply-To: <20100824014325.GA6033@kt>
On Tue, Aug 24, 2010 at 09:43:25AM +0800, Ken CC wrote:
> On Mon, Aug 23, 2010 at 06:56:56PM +0900, Isaku Yamahata wrote:
> >
> > How did you trigger the bug?
> > I suppose parse_pci_devfn() in qdev-properties should check the error.
> > Although I'm not objecting this patch itself, it's caller's bug.
> > Just assert(devfn < PCIBUS_MAX_DEVICES)?
> >
>
> assign pci addr > 30,
>
> e.g.
> qemu-system-x86_64 -drive \
> file='./fedora.13-x86_64-virtio.qcow2',if=none,id=drv-virtio-d1,media=disk,cache=none,boot=on,format=qcow2 \
> -device virtio-blk-pci,bus=pci.0,addr=0x90,drive=drv-virtio-d1,id=virtio-disk1 \
> ^^^^
> -m 2048 -vnc :11
So parse_pci_devfn() in qdev-properties.c lacks the necessary
check. It checks fn range, but doesn't check slot range.
So please add the slot check into parse_pci_devfn(), and add assert() into
do_pci_register_device().
thanks,
>
>
> assert() is good to me.
> and i think checking in the caller should be done too.
>
> > On Mon, Aug 23, 2010 at 01:56:31PM +0800, Ken CC wrote:
> > >
> > > Check before trying subindexing.
> > >
> > > Signed-off-by: Ken CC <ken.ccao@gmail.com>
> > > ---
> > > hw/pci.c | 4 ++++
> > > 1 files changed, 4 insertions(+), 0 deletions(-)
> > >
> > > diff --git a/hw/pci.c b/hw/pci.c
> > > index a09fbac..f6f00c6 100644
> > > --- a/hw/pci.c
> > > +++ b/hw/pci.c
> > > @@ -675,6 +675,10 @@ static PCIDevice *do_pci_register_device(PCIDevice *pci_dev, PCIBus *bus,
> > > error_report("PCI: no slot/function available for %s, all in use", name);
> > > return NULL;
> > > found: ;
> > > + } else if (devfn > PCIBUS_MAX_DEVICES - 1) {
> > > + error_report("PCI: devfn is out of bus capacity."
> > > + " Only %d devices supported.", PCIBUS_MAX_DEVICES);
> > > + return NULL;
> > > } else if (bus->devices[devfn]) {
> > > error_report("PCI: slot %d function %d not available for %s, in use by %s",
> > > PCI_SLOT(devfn), PCI_FUNC(devfn), name, bus->devices[devfn]->name);
> > >
> > >
> > >
> >
> > --
> > yamahata
>
> --
>
--
yamahata
next prev parent reply other threads:[~2010-08-24 2:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-23 5:46 [Qemu-devel] [PATCH 1/2] PCI: define max devices number on PCIBus as PCIBus_MAX_DEVICES in pci.h Ken CC
2010-08-23 5:53 ` [Qemu-devel] [PATCH] pci init: Check if devfn exceeding the max devices number supported on bus Ken CC
2010-08-23 5:56 ` [Qemu-devel] [PATCH 2/2] " Ken CC
2010-08-23 9:56 ` Isaku Yamahata
2010-08-24 1:43 ` Ken CC
2010-08-24 2:18 ` Isaku Yamahata [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-08-12 9:25 [Qemu-devel] [PATCH] PCI: define max devices number on PCIBus as PCIBus_MAX_DEVICES in pci.h Ken CC
2010-08-12 10:00 ` [Qemu-devel] [PATCH 2/2] pci init: Check if devfn exceeding the max devices number supported on bus Ken CC
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=20100824021811.GH20428@valinux.co.jp \
--to=yamahata@valinux.co.jp \
--cc=ken.ccao@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--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).