linux-kernel - [PATCH v1 0/3] [RFC] resource, PCI: work around pci=use

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 11 Mar 2010 17:01:03 -0700
From:	Bjorn Helgaas <bjorn.helgaas@...com>
To:	Jesse Barnes <jbarnes@...tuousgeek.org>
Cc:	linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org,
	"Rafael J. Wysocki" <rjw@...k.pl>,
	Yanko Kaneti <yaneti@...lera.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Thomas Renninger <trenn@...e.de>, maciej.rutecki@...il.com
Subject: [PATCH v1 0/3] [RFC] resource, PCI: work around pci=use_crs conflicts

These patches are to fix this pci=use_crs regression:

    http://bugzilla.kernel.org/show_bug.cgi?id=15480

The problem is that BIOS reported a PCI host bridge window that overlaps
system RAM.  This workaround trims the window to avoid the overlap, which
requires information about the conflicting resource.

Yanko, I reworked these a bit, so if you have a chance to retest them
and collect another dmesg log, I'd appreciate it.

I'm still hoping for someone to find out how Windows deals with this, but
haven't gotten any data yet.

---

Bjorn Helgaas (3):
      resources: add interfaces that return conflict information
      x86/PCI: trim _CRS windows when they conflict with previous reservations
      PCI: for address space collisions, show conflicting resource


 arch/x86/pci/acpi.c     |   48 ++++++++++++++++++++++++++++++++++-------------
 drivers/pci/setup-res.c |   14 ++++++++------
 include/linux/ioport.h  |    2 ++
 kernel/resource.c       |   44 ++++++++++++++++++++++++++++++++++++-------
 4 files changed, 82 insertions(+), 26 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/