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 3/4] x86: pci: acpi: Fix the range check for IO resources
Date: Thu, 11 Dec 2014 19:48:22 -0000 [thread overview]
Message-ID: <20141211193112.725667793@linutronix.de> (raw)
In-Reply-To: <20141211191853.613107396@linutronix.de>
[-- Attachment #1: x86-pci-check-proper-range.patch --]
[-- Type: text/plain, Size: 2874 bytes --]
The range check in setup_res() checks the IO range against
iomem_resource. That's just wrong.
Move the check into a separate function and use ioport_resource for IO
ranges.
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
---
arch/x86/pci/acpi.c | 51 +++++++++++++++++++++++++++++++++------------------
1 file changed, 33 insertions(+), 18 deletions(-)
Index: tip/arch/x86/pci/acpi.c
===================================================================
--- tip.orig/arch/x86/pci/acpi.c
+++ tip/arch/x86/pci/acpi.c
@@ -240,12 +240,41 @@ static acpi_status count_resource(struct
return AE_OK;
}
+static bool valid_resource_range(struct resource *r, struct device *dev)
+{
+ struct resource *ior;
+ u64 end;
+
+ ior = (r->flags & IORESOURCE_IO) ? &ioport_resource : &iomem_resource;
+
+ /*
+ * Exclude non-addressable range or non-addressable portion of
+ * range. We only check end because ior->start is always 0.
+ */
+ end = r->end;
+ r->end = min(r->end, ior->end);
+ if (r->end <= r->start) {
+ dev_info(dev, "host bridge %s window [%#llx-%#llx] invalid range\n",
+ r->flags & IORESOURCE_IO ? "io" : "mem",
+ (unsigned long long)r->start, end);
+ return false;
+ }
+
+ if (r->end == end)
+ return true;
+
+ dev_info(dev, "host bridge %s window [%#llx-%#llx] truncated to [%#llx-%#llx]\n",
+ r->flags & IORESOURCE_IO ? "io" : "mem",
+ (unsigned long long)r->start, end,
+ (unsigned long long)r->start, (unsigned long long)r->end);
+ return true;
+}
+
static acpi_status setup_resource(struct acpi_resource *acpi_res, void *data)
{
struct pci_root_info *info = data;
u64 translation_offset = 0;
struct resource r;
- u64 orig_end;
memset(&r, 0, sizeof(r));
if (!acpi_dev_resource_memory(acpi_res, &r)) {
@@ -269,31 +298,17 @@ static acpi_status setup_resource(struct
r.end += translation_offset;
}
- if (!is_valid_resource(&r))
+ if (!is_valid_resource(&r) ||
+ !valid_resource_range(&r, &info->bridge->dev))
return AE_OK;
- /* 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);
+ "host bridge window %pR ignored\n", &r);
return AE_OK;
}
next prev parent reply other threads:[~2014-12-11 19:48 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 ` [patch 1/4] x86, pci, acpi: Redo sanity checks for root brigde probing Thomas Gleixner
2014-12-12 11:33 ` 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 ` Thomas Gleixner [this message]
2014-12-12 14:56 ` [patch 3/4] x86: pci: acpi: Fix the range check for IO resources 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.725667793@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