linux-kernel - Re: [x86, smap] general protection fault: fff2 [#1] PREEMPT DEBUG

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] [day] [month] [year] [list]

Message-ID: <534DE589.5020408@linux.intel.com>
Date:	Tue, 15 Apr 2014 19:06:01 -0700
From:	"H. Peter Anvin" <hpa@...ux.intel.com>
To:	Fengguang Wu <fengguang.wu@...el.com>,
	Jet Chen <jet.chen@...el.com>
CC:	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [x86, smap]  general protection fault: fff2 [#1] PREEMPT DEBUG_PAGEALLOC

On 04/11/2014 07:17 AM, Fengguang Wu wrote:
> Sorry, but I suspect this commit may well be innocent and merely
> _discloses_ an existing bug.
> 
> Because dmesgs for the parent commit all(*) stop here, long before being able
> to emit the "reboot: machine restart" and the general protection fault.
> 
> (*) "all" means all the machines that run qemu "-cpu Haswell,+smep,+smap".
> 
> [  562.353714] Failed to execute /init (error -14)
> [  562.400008] Starting init: /sbin/init exists but couldn't execute it (error -14)
> [  562.400008] Starting init: /etc/init exists but couldn't execute it (error -13)
> [  562.422116] Starting init: /bin/sh exists but couldn't execute it (error -14)
> [  562.450049] Kernel panic - not syncing: No working init found.  Try passing init= option to kernel. See Linux Documentation/init.txt for guidance.
> [  562.450049] CPU: 0 PID: 1 Comm: init Not tainted 3.14.0-rc1-00171-g03bbd59 #1
> [  562.450049]  0000000000000000 ffff880012035ec0 ffffffff81380af6 ffff880012035f38
> [  562.450049]  ffffffff8137e608 ffffffff00000008 ffff880012035f48 ffff880012035ee8
> [  562.450049]  0000000000000000 ffffffff81067fcf 0000000000000001 0000000000000000
> [  562.450049] Call Trace:
> [  562.450049]  [<ffffffff81380af6>] dump_stack+0x19/0x1b
> [  562.450049]  [<ffffffff8137e608>] panic+0xcb/0x1ca
> [  562.450049]  [<ffffffff81067fcf>] ? console_unlock+0x319/0x336
> [  562.450049]  [<ffffffff8137778d>] ? rest_init+0xc1/0xc1
> [  562.450049]  [<ffffffff8137785e>] kernel_init+0xd1/0xd5
> [  562.450049]  [<ffffffff81386d3a>] ret_from_fork+0x7a/0xb0
> [  562.450049]  [<ffffffff8137778d>] ? rest_init+0xc1/0xc1
> [  562.450049] Kernel Offset: 0x0 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffff9fffffff)
> 

That makes sense, because without that patch any SMAP-based machine
would be known broken.

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