linux-kernel - [Debug 0/2] Fix regressions caused by commit 593669c2ac0f

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:	Tue,  3 Mar 2015 12:25:39 +0800
From:	Jiang Liu <jiang.liu@...ux.intel.com>
To:	"Rafael J . Wysocki" <rjw@...ysocki.net>,
	Thomas Voegtle <tv@...96.de>, Hudd <hedede.l@...il.com>,
	Prakash Punnoor <prakash@...noor.de>,
	Francois Romieu <romieu@...zoreil.com>,
	Dave Airlie <airlied@...il.com>,
	Marcel Holtmann <marcel@...tmann.org>
Cc:	Jiang Liu <jiang.liu@...ux.intel.com>,
	Bjorn Helgaas <bhelgaas@...gle.com>,
	LKML <linux-kernel@...r.kernel.org>, linux-pci@...r.kernel.org,
	linux-acpi@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
	Lv Zheng <lv.zheng@...el.com>
Subject: [Debug 0/2] Fix regressions caused by commit 593669c2ac0f

Commit 593669c2ac0f (x86/PCI/ACPI: Use common ACPI resource interfaces
to simplify implementation) causes regression to several platforms,
which is caused by stricter checks in new ACPI resource parsing code
and BIOSes report incorrect ACPI resource descriptors.  So try to relax
the check to avoid regressions.

Jiang Liu (2):
  x86/PCI/ACPI: Ignore resources consumed by host bridge itself
  x86/PCI/ACPI: Relax ACPI resource descriptor checks to work around
    BIOS bugs

 arch/x86/pci/acpi.c     |   11 ++++++++---
 drivers/acpi/resource.c |    4 +++-
 2 files changed, 11 insertions(+), 4 deletions(-)

-- 
1.7.10.4

--
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/