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]

Date:	Wed, 2 Jun 2010 13:08:27 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Matthew Garrett <mjg59@...f.ucam.org>
Cc:	"Justin P. Mattock" <justinmattock@...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 Tue, 1 Jun 2010 22:48:20 +0100
Matthew Garrett <mjg59@...f.ucam.org> wrote:

> On Tue, Jun 01, 2010 at 02:43:12PM -0700, Justin P. Mattock wrote:
> > On 06/01/2010 02:29 PM, Matthew Garrett wrote:
> >> So, just to be clear, you run this as root and it immediately returns
> >> you to the prompt? This seems unlikely.
> >
> > yep.. with the above code
> > I (save to a file) then
> > non-root gcc reboot.c -o reboot
> > then su
> > ./reboot
> > just bake to the command prompt
> 
> Are you running some sort of security policy that might block hardware 
> access?

	Try

	if (iopl(...))
		perror

... (or strace it running as root)
--
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/