linux-kernel - Re: [PATCH 23/23] x86, PCI: add pcibios_root

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

Message-Id: <4F587E9702000078000770BA@nat28.tlf.novell.com>
Date:	Thu, 08 Mar 2012 08:40:39 +0000
From:	"Jan Beulich" <JBeulich@...e.com>
To:	"Bjorn Helgaas" <bhelgaas@...gle.com>,
	"Yinghai Lu" <yinghai@...nel.org>
Cc:	"Bjorn Helgaas" <bjorn.helgaas@...il.com>, "x86" <x86@...nel.org>,
	"Mauro Carvalho Chehab" <mchehab@...hat.com>,
	<linux-kernel@...r.kernel.org>, <linux-pci@...r.kernel.org>,
	"Jesse Barnes" <jbarnes@...tuousgeek.org>
Subject: Re: [PATCH 23/23] x86, PCI: add pcibios_root_rescan

>>> On 08.03.12 at 05:27, Bjorn Helgaas <bhelgaas@...gle.com> wrote:
> Personally, I think we should put a stake in the ground and say "For
> machines newer than 2013, Linux will not blindly probe for PCI
> devices.  If you want EDAC functionality, make sure your BIOS exposes
> the appropriate PCI host bridges."  If OEMs do care about EDAC, it's a
> simple BIOS change to do this.
> 
> I certainly don't think we need to add hotplug or bus rescan
> functionality to cover this case.  This sort of stuff makes
> maintenance MUCH harder because we have to worry about all these
> corner cases.

I'm certainly fine with such a position, as long as this is made visible as
a policy and the other hack in the i7core edac driver to find non-
exposed devices gets removed as well. It was really the existing hack
(which worked only on a certain subset of systems) that made me try
find a more generic solution.

Jan

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