linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Will Deacon <will.deacon@arm.com>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: linux-pci@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>
Subject: Re: [PATCH 5/6] drivers: pci: host: common: fix pci_remap_iospace() failure path
Date: Mon, 22 Aug 2016 14:21:24 +0100	[thread overview]
Message-ID: <20160822132124.GG14680@arm.com> (raw)
In-Reply-To: <1471279854-11916-6-git-send-email-lorenzo.pieralisi@arm.com>

On Mon, Aug 15, 2016 at 05:50:45PM +0100, Lorenzo Pieralisi wrote:
> On ARM/ARM64 architectures, PCI IO ports are emulated through memory
> mapped IO, by reserving a chunk of virtual address space starting at
> PCI_IOBASE and by mapping the PCI host bridges memory address space
> driving PCI IO cycles to it.
> 
> PCI host bridge drivers that enable downstream PCI IO cycles map the
> host bridge memory address responding to PCI IO cycles to the fixed
> virtual address space through the pci_remap_iospace() API.
> 
> This means that if the pci_remap_iospace() function fails, the
> corresponding host bridge PCI IO resource must be considered invalid, in
> that there is no way for the kernel to actually drive PCI IO
> transactions if the memory addresses responding to PCI
> IO cycles cannot be mapped into the CPU virtual address space.
> 
> The PCI common host bridge driver does not remove the PCI IO
> resource from the host bridge resource windows if the
> pci_remap_iospace() call fails; this is an actual bug in that the
> PCI host bridge would consider the PCI IO resource valid (and possibly
> assign it to downstream devices) even if the kernel was not able
> to map the PCI host bridge memory address driving IO cycle to the
> CPU virtual address space (ie pci_remap_iospace() failures).
> 
> Fix the PCI host bridge driver pci_remap_iospace() failure path, by
> destroying the PCI host bridge PCI IO resources retrieved through
> firmware when the pci_remap_iospace() function call fails, therefore
> preventing the kernel from adding the respective PCI IO resource to the
> list of PCI host bridge valid resources, fixing the issue.
> 
> Signed-off-by: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
> Fixes: 4e64dbe226e7 ("PCI: generic: Expose pci_host_common_probe() for
> use by other drivers")
> Cc: Bjorn Helgaas <bhelgaas@google.com>
> Cc: Will Deacon <will.deacon@arm.com>
> ---
>  drivers/pci/host/pci-host-common.c | 8 +++++---
>  1 file changed, 5 insertions(+), 3 deletions(-)

Looks good to me:

Acked-by: Will Deacon <will.deacon@arm.com>

Will

  reply	other threads:[~2016-08-22 13:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-15 16:50 [PATCH 0/6] PCI: fix pci_remap_iospace() failure paths Lorenzo Pieralisi
2016-08-15 16:50 ` [PATCH 1/6] drivers: pci: host: aardvark: fix pci_remap_iospace() failure path Lorenzo Pieralisi
2016-08-15 16:50 ` [PATCH 2/6] drivers: pci: host: designware: " Lorenzo Pieralisi
2016-08-15 16:50 ` [PATCH 3/6] drivers: pci: host: versatile: " Lorenzo Pieralisi
2016-08-15 16:50 ` [PATCH 4/6] drivers: pci: host: rcar: " Lorenzo Pieralisi
2016-08-15 16:50 ` [PATCH 5/6] drivers: pci: host: common: " Lorenzo Pieralisi
2016-08-22 13:21   ` Will Deacon [this message]
2016-08-15 16:50 ` [PATCH 6/6] drivers: pci: host: tegra: " Lorenzo Pieralisi
2016-09-06 17:43 ` [PATCH 0/6] PCI: fix pci_remap_iospace() failure paths 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=20160822132124.GG14680@arm.com \
    --to=will.deacon@arm.com \
    --cc=bhelgaas@google.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.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).