linux-kernel - Re: [PATCH 1/3] Introduce interface to report BIOS bugs

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: <20080822101910.GH6542@atrey.karlin.mff.cuni.cz>
Date:	Fri, 22 Aug 2008 12:19:10 +0200
From:	Pavel Machek <pavel@...e.cz>
To:	Thomas Renninger <trenn@...e.de>
Cc:	linux-kernel@...r.kernel.org, ak@...ux.intel.com,
	len.brown@...el.com, arjan@...ux.intel.com, bjorn.helgaas@...com,
	linux-acpi@...r.kernel.org,
	Christian Kornacker <ckornacker@...e.de>
Subject: Re: [PATCH 1/3] Introduce interface to report BIOS bugs

Hi!

> 
> This is mostly needed for ACPI systems.
> ACPI introduces an endless amount of possible BIOS
> bugs like wrong values, missing functions, etc.
> The kernel has to sanity check all of them and should
> report BIOS bugs as such to the user.
> 
> ACPI is the main target, of course others, who already declare BIOS bugs,
> also benefit from this, e.g. PCI:
> arch/x86/pci/pcbios.c:
>    printk(KERN_WARNING "bios32_service(0x%lx): returned 0x%x -- BIOS bug!\n",
>    printk (KERN_ERR "PCI: BIOS BUG #%x[%08x] found\n",
> ...
> This one I stumbled over recently (when >4GB BIOS sets up IO mem for this
> device wrongly on some Dell notebooks):
>    ohci_hcd 0000:00:02.0: USB HC takeover failed!  (BIOS/SMM bug)

I like the idea... Plus, it would be cool to have message clearly
state if Linux could work around this problem. 

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
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/