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]
Date:	Tue, 08 Jul 2008 08:40:21 -0700
From:	Arjan van de Ven <arjan@...ux.intel.com>
To:	Pavel Machek <pavel@...e.cz>
CC:	Thomas Renninger <trenn@...e.de>, Len Brown <lenb@...nel.org>,
	linux-acpi@...r.kernel.org, Bob Moore <robert.moore@...el.com>,
	Lin Ming <ming.m.lin@...el.com>,
	Len Brown <len.brown@...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

Pavel Machek wrote:
> Hi!
> 
>>> 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'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.

also we can tie this to kerneloops.org to make a list of top known firmware/hardware bugs, seperate from the kernel code bugs
> 

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