linux-kernel - Re: Bisected KVM hang on x86-32 between v3.12 and v3.13

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: <20140407185658.GK11096@twins.programming.kicks-ass.net>
Date:	Mon, 7 Apr 2014 20:56:58 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Toralf Förster <toralf.foerster@....de>
Cc:	Michele Ballabio <barra_cuda@...amail.com>,
	linux-kernel@...r.kernel.org, fweisbec@...il.com, mingo@...nel.org,
	Steven Rostedt <rostedt@...dmis.org>
Subject: Re: Bisected KVM hang on x86-32 between v3.12 and v3.13

On Mon, Apr 07, 2014 at 08:16:24PM +0200, Toralf Förster wrote:

> v3.14-10353-g2b3a8fd works fine AFAICS
> (BTW the fix is stable material, right ?)

I'm fairly sure its not; its a rather invasive series; see:

2432e1364bbe x86: Nuke the supervisor_stack field in i386 thread_info
b807902a88c4 x86: Nuke GET_THREAD_INFO_WITH_ESP() macro for i386
0788aa6a23cb x86: Prepare removal of previous_esp from i386 thread_info structure
198d208df437 x86: Keep thread_info on thread stack in x86_32

Let me see if there's anything 'simpler' we can stuff in .13+
--
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/