From: Thomas Gleixner <tglx@linutronix.de>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Jiang Liu <jiang.liu@linux.intel.com>,
x86@kernel.org, Bjorn Helgaas <bhelgaas@google.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Borislav Petkov <bp@alien8.de>, Yinghai Lu <yinghai@kernel.org>
Subject: [patch 1/4] x86, pci, acpi: Redo sanity checks for root brigde probing
Date: Thu, 11 Dec 2014 19:48:18 -0000 [thread overview]
Message-ID: <20141211193112.547808552@linutronix.de> (raw)
In-Reply-To: <20141211191853.613107396@linutronix.de>
[-- Attachment #1: fix_x86_pci_acpi.patch --]
[-- Type: text/plain, Size: 4745 bytes --]
From: Yinghai Lu <yinghai@kernel.org>
commit e22ce93870de ("x86, PCI, ACPI: Kill private function
resource_to_addr() in arch/x86/pci/acpi.c") dropped the sanity checks
for resources initialized via acpi_dev_resource_memory().
It further dropped a check for address_length = 0 for the resources
which are initialized via acpi_dev_resource_address_space().
For translated addresses the range check operates on the non
translated end address. Assign orig_end after adding the translation
offset.
This causes that invalid resources are not dropped and the range check
for translated addresses fails.
[ tglx: Rewrote changelog.
Added the address_length check to the x86 code and not into
acpi_dev_resource_address_space(). While the acpi function should
check this, we want to have a proper check which sets the
IORESOURCE_DISABLED bit as it does for IO resources.
Removed the pointless memset of addr. acpi_resource_to_address64()
either fails or fills it completely ]
Fixes: commit e22ce93870de ("x86, PCI, ACPI: Kill private function resource_to_addr() in arch/x86/pci/acpi.c").
Signed-off-by: Yinghai Lu <yinghai@kernel.org>
Link: http://lkml.kernel.org/r/CAE9FiQWaL1Qu1eP-fQV784ucy+r-65AZ95VyiUrefn0dNtfLDw@mail.gmail.com
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
---
arch/x86/pci/acpi.c | 63 ++++++++++++++++++++++++++--------------------------
1 file changed, 32 insertions(+), 31 deletions(-)
Index: tip/arch/x86/pci/acpi.c
===================================================================
--- tip.orig/arch/x86/pci/acpi.c
+++ tip/arch/x86/pci/acpi.c
@@ -221,10 +221,9 @@ static void teardown_mcfg_map(struct pci
static acpi_status count_resource(struct acpi_resource *acpi_res, void *data)
{
struct pci_root_info *info = data;
- struct resource r = {
- .flags = 0
- };
+ struct resource r;
+ memset(&r, 0, sizeof(r));
if (!acpi_dev_resource_memory(acpi_res, &r) &&
!acpi_dev_resource_address_space(acpi_res, &r))
return AE_OK;
@@ -239,14 +238,13 @@ static acpi_status setup_resource(struct
{
struct pci_root_info *info = data;
u64 translation_offset = 0;
- struct resource r = {
- .flags = 0
- };
+ struct resource r;
+ u64 orig_end;
+ memset(&r, 0, sizeof(r));
if (acpi_dev_resource_memory(acpi_res, &r)) {
- r.flags &= IORESOURCE_MEM | IORESOURCE_IO;
+ r.flags &= IORESOURCE_MEM;
} else if (acpi_dev_resource_address_space(acpi_res, &r)) {
- u64 orig_end;
struct acpi_resource_address64 addr;
r.flags &= IORESOURCE_MEM | IORESOURCE_IO;
@@ -256,40 +254,43 @@ static acpi_status setup_resource(struct
if (ACPI_FAILURE(acpi_resource_to_address64(acpi_res, &addr)))
return AE_OK;
+ if (!addr.address_length)
+ return AE_OK;
+
if (addr.resource_type == ACPI_MEMORY_RANGE &&
addr.info.mem.caching == ACPI_PREFETCHABLE_MEMORY)
r.flags |= IORESOURCE_PREFETCH;
translation_offset = addr.translation_offset;
- orig_end = r.end;
r.start += translation_offset;
r.end += translation_offset;
-
- /* Exclude non-addressable range or non-addressable portion of range */
- r.end = min(r.end, iomem_resource.end);
- if (r.end <= r.start) {
- dev_info(&info->bridge->dev,
- "host bridge window [%#llx-%#llx] (ignored, not CPU addressable)\n",
- (unsigned long long)r.start, orig_end);
- return AE_OK;
- } else if (orig_end != r.end) {
- dev_info(&info->bridge->dev,
- "host bridge window [%#llx-%#llx] ([%#llx-%#llx] ignored, not CPU addressable)\n",
- (unsigned long long)r.start, orig_end,
- (unsigned long long)r.end + 1, orig_end);
- }
+ } else {
+ return AE_OK;
}
- if (r.flags && resource_size(&r)) {
- r.name = info->name;
- info->res[info->res_num] = r;
- info->res_offset[info->res_num] = translation_offset;
- info->res_num++;
- if (!pci_use_crs)
- dev_printk(KERN_DEBUG, &info->bridge->dev,
- "host bridge window %pR (ignored)\n", &r);
+ /* Exclude non-addressable range or non-addressable portion of range */
+ orig_end = r.end;
+ r.end = min(r.end, iomem_resource.end);
+ if (r.end <= r.start) {
+ dev_info(&info->bridge->dev,
+ "host bridge window [%#llx-%#llx] (ignored, not CPU addressable)\n",
+ (unsigned long long)r.start, orig_end);
+ return AE_OK;
+ } else if (orig_end != r.end) {
+ dev_info(&info->bridge->dev,
+ "host bridge window [%#llx-%#llx] ([%#llx-%#llx] ignored, not CPU addressable)\n",
+ (unsigned long long)r.start, orig_end,
+ (unsigned long long)r.end + 1, orig_end);
}
+ r.name = info->name;
+ info->res[info->res_num] = r;
+ info->res_offset[info->res_num] = translation_offset;
+ info->res_num++;
+ if (!pci_use_crs)
+ dev_printk(KERN_DEBUG, &info->bridge->dev,
+ "host bridge window %pR (ignored)\n", &r);
+
return AE_OK;
}
next prev parent reply other threads:[~2014-12-11 19:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-11 19:48 [patch 0/4] x86: Fix the ACPI resource handling and range checking Thomas Gleixner
2014-12-11 19:48 ` Thomas Gleixner [this message]
2014-12-12 11:33 ` [patch 1/4] x86, pci, acpi: Redo sanity checks for root brigde probing Borislav Petkov
2014-12-11 19:48 ` [patch 2/4] x86: pci: acpi: Respect ioresource flags Thomas Gleixner
2014-12-12 13:39 ` Borislav Petkov
2014-12-11 19:48 ` [patch 3/4] x86: pci: acpi: Fix the range check for IO resources Thomas Gleixner
2014-12-12 14:56 ` Borislav Petkov
2014-12-11 19:48 ` [patch 4/4] acpi: ioapic: Respect the resource flags Thomas Gleixner
2014-12-12 2:44 ` Yinghai Lu
2014-12-12 7:53 ` Thomas Gleixner
2014-12-12 8:24 ` Yinghai Lu
2014-12-12 8:46 ` Jiang Liu
2014-12-12 11:43 ` Thomas Gleixner
2014-12-17 5:44 ` Jiang Liu
2014-12-17 8:55 ` Thomas Gleixner
2014-12-12 11:39 ` Thomas Gleixner
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=20141211193112.547808552@linutronix.de \
--to=tglx@linutronix.de \
--cc=bhelgaas@google.com \
--cc=bp@alien8.de \
--cc=jiang.liu@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=x86@kernel.org \
--cc=yinghai@kernel.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
Powered by JetHome