linux-kernel - Re: [PATCH] x86, reboot: skip DMI checks if reboot set by user

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: <4F18584F.7060603@zytor.com>
Date:	Thu, 19 Jan 2012 09:52:15 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Michael D Labriola <mlabriol@...b.com>
CC:	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Kushal Koolwal <kushalkoolwal@...il.com>,
	linux-kernel@...r.kernel.org, michael.d.labriola@...il.com,
	Ingo Molnar <mingo@...e.hu>,
	Matthew Garrett <mjg59@...f.ucam.org>, support@...salogic.com,
	Thomas Gleixner <tglx@...utronix.de>, x86@...nel.org
Subject: Re: [PATCH] x86, reboot: skip DMI checks if reboot set by user

On 01/19/2012 09:46 AM, Michael D Labriola wrote:
>
> Random question...  why do we have a reboot_init function that does DMI
> checking with reboot_dmi_table (callbacks are mostly set_bios_reboot, but
> there is a single set_kbd_reboot) and also a pci_reboot_init which does
> the DMI check again using a separate pci_reboot_dmi_table (all callbacks
> are to set_pci_reboot)?
>
> Wouldn't it make more sense to do a single DMI scan using one big table?
>

Yes, and such a patch would be appreciated.

The reason it is as it is dates back to before the 32-64 bit 
unification, as far as I know.

(BIOS reboot is currently not supported on 64 bits, mainly.)

	-hpa

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