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]

Date:	Thu, 19 Jan 2012 11:17:54 -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 11:14 AM, Michael D Labriola wrote:
>>
>> 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.)
> 
> Well, that does complicate it a bit.  I'll gin something up and see what
> you think.  I guess it will involve having an #ifdef CONFIG_X86_32 block
> inside a single dmi_table structure for the BIOS quirks.
> 
> Actually, set_kbd_reboot is inside the current X86_32 only block, along
> with the one DMI callback that uses it.  Is this correct?
> 

Probably not, although I suspect most of the users of that are 32-bit
only systems.

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.

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