linux-kernel - Re: [PATCH] ACPI / PNP: Reserve ACPI resources at the fs_initcall

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-prev] [day] [month] [year] [list]

Date:	Thu, 17 Sep 2015 02:44:34 +0200
From:	"Rafael J. Wysocki" <rjw@...ysocki.net>
To:	George McCollister <george.mccollister@...il.com>
Cc:	ACPI Devel Maling List <linux-acpi@...r.kernel.org>,
	Linux PCI <linux-pci@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Bjorn Helgaas <bhelgaas@...gle.com>, g5983969@...vm.com,
	Roland Dreier <roland@...estorage.com>
Subject: Re: [PATCH] ACPI / PNP: Reserve ACPI resources at the fs_initcall_sync stage

On Wednesday, September 16, 2015 04:45:51 PM George McCollister wrote:
> Unfortunately I just got around to trying linux 4.1.6 (which contains
> this commit) on the Versalogic Tiger (VL-EPM-24)
> http://www.versalogic.com/tiger and this commit breaks it, seems to be
> back to the old behavior reported here:
> 
> http://marc.info/?t=143092384600002&r=1&w=2
> 
> Before reversing the commit it shows:
> pci 0000:00:1c.0: BAR 13: assigned [io  0x2000-0x2fff]
> 
> After reversing the commit it shows:
> pci 0000:00:1c.0: BAR 13: assigned [io  0x3000-0x3fff]
> 
> I don't have a solution to propose at this point and haven't tried the
> latest upstream so I'll just be building with this commit reversed
> (which solves the problem) until I have a chance to look into this
> further.

It looks like on your system the ACPI resources really need to be reserved
before the PCI bus is initialized, but we can't do that unconditionally
for everyone without introducing regressions, so the only way to address
that I can see would be to blacklist your system.

Thanks,
Rafael

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