linux-kernel - Re: [PATCH]X86:reboot.c Add some dmi entries to pci_reboot_dmi

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: <20100603105438.7b8f3ee8@lxorguk.ukuu.org.uk>
Date:	Thu, 3 Jun 2010 10:54:38 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Matthew Garrett <mjg59@...f.ucam.org>
Cc:	"Justin P. Mattock" <justinmattock@...il.com>,
	Robert Hancock <hancockrwd@...il.com>, x86@...nel.org,
	tglx@...utronix.de, linux-kernel@...r.kernel.org
Subject: Re: [PATCH]X86:reboot.c Add some dmi entries to
 pci_reboot_dmi_table.

On Thu, 3 Jun 2010 03:18:51 +0100
Matthew Garrett <mjg59@...f.ucam.org> wrote:

> On Wed, Jun 02, 2010 at 07:15:36PM -0700, Justin P. Mattock wrote:
> > as soon as I change:
> >
> > int main() {
> > 	iopl(3);
> > 	outb(6, 0xcf9);
> > 	usleep(100);
> > 	outb(6, 0xcf9);
> > 	return 0;
> > }
> > (the above gave a command prompt
> > with numerous tries)
> 
> Ok, so it's not that straghtforward. Sigh. There's various hacky 
> workarounds we could do here, but Windows doesn't seem to do them so I 
> lean towards suspecting that there's something wrong with our keyboard 
> controller reboot mechanism. I'll try doing some more tracing.

At least some PCs you need to issue the reboot outb calls on the boot
processor so the userspace tests won't be reliable.
--
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/