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: <960B77DF2E6D974DBE24FD066EAEE8DAD90886@azsmsx422.amr.corp.intel.com>
Date:	Tue, 8 Jul 2008 12:34:55 -0700
From:	"Brown, Len" <len.brown@...el.com>
To:	"Arjan van de Ven" <arjan@...ux.intel.com>,
	"Pavel Machek" <pavel@...e.cz>
Cc:	"Thomas Renninger" <trenn@...e.de>, "Len Brown" <lenb@...nel.org>,
	<linux-acpi@...r.kernel.org>,
	"Moore, Robert" <robert.moore@...el.com>,
	"Lin, Ming M" <ming.m.lin@...el.com>,
	"Bjorn Helgaas" <bjorn.helgaas@...com>,
	"Huang Cheng" <cheng.huang@...el.com>,
	<firmwarekit-discuss@...host.org>,
	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>
Subject: RE: Check for BIOS bugs - Original Subject: Re: [PATCH 23/70] ACPICA: Workaround for reversed _PRT entries from BIOS

 

>>>> Some BIOSs erroneously reverse the _PRT SourceName and the
>>>> SourceIndex.  Detect and repair this problem. MS ACPI also allows
>>>> and repairs this problem, thus ACPICA must also.
>>> It would be great to have an interface to report this as a 
>BIOS defect.
>>>
>>> Something like:
>>>
>>> FIRMWARE_BUG_ON(FIRM_WARN, "erroneously reversed the _PRT 
>source_name", ACPI_ 
>>> Bug);
>>>
>>> FIRMWARE_BUG_ON(severity, description, component);
>> 
>> Yes, please.

I'm not excited about maintaining
maintaining linux-as-a-firmware-diagnostic --
particularly when...

1. it clutters the code for normail machines
2. finding the bug is pointless, because even
   if you fix one machine, you are guaranteed to
   not fix all machines and thus must maintain
   the workaround anyway.

>> I'd also like HARDWARE_BUG_ON(), with similar usage.
>> 
>> With all the preload-linux-on-foo project, we have some 
>> chance to make
>> BIOS vendors fix their stuff if we can easily diagnose errors in
>> there.

These customers should be running 
http://linuxfirmwarekit.org/

We do maintain some degree of "high-road ACPI spec checking"
with the "acpi=strict" boot option.  If we do more of this,
I think it should stay under that option.

thanks,
-Len
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ