linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: David Engraf <david.engraf@sysgo.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	Wei Yang <weiyang@linux.vnet.ibm.com>,
	linux-pci@vger.kernel.org
Subject: Re: Exception due to PCI: Use pci_is_root_bus() to check for root bus
Date: Wed, 6 Apr 2016 08:35:02 -0500	[thread overview]
Message-ID: <20160406133502.GB4976@localhost> (raw)
In-Reply-To: <5704F85B.4080501@sysgo.com>

Hi David,

On Wed, Apr 06, 2016 at 01:51:55PM +0200, David Engraf wrote:
> Hi,
> 
> I have an exception in __pci_bus_size_bridges() when pci_is_root_bus
> returns false but bus->self == NULL. My driver registers a virtual
> bus, like virtfn_add_bus(). pci_add_new_bus() is called with a
> parent but without a pci_dev. Thus bus->parent is set but bus->self
> is NULL. When __pci_bus_size_bridges() is called I get an exception
> at:
> 
> switch (bus->self->class >> 8)
> 
> The previous version of the code, checking for bus->self != NULL
> worked for me. I think an additional check is required to make sure
> we're not accessing a NULL pointer.

When you say "previous version of the code," do you mean a previous
version of Linux worked correctly but a newer version does not?  What
versions are they?  Did you identify a commit that changed the
behavior?  I assume you're talking about an out-of-tree driver that
registers a virtual bus?  Can you point us to the code?  Can you share
the dmesg log, including the backtrace?

Bjorn

  reply	other threads:[~2016-04-06 13:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-06 11:51 Exception due to PCI: Use pci_is_root_bus() to check for root bus David Engraf
2016-04-06 13:35 ` Bjorn Helgaas [this message]
2016-04-06 14:01   ` David Engraf
2016-04-25 13:04     ` [PATCH] " David Engraf
2016-04-25 16:59       ` Bjorn Helgaas
2016-05-11  7:04         ` David Engraf
2016-05-11 14:53           ` Bjorn Helgaas

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=20160406133502.GB4976@localhost \
    --to=helgaas@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=david.engraf@sysgo.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=weiyang@linux.vnet.ibm.com \
    /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).