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]

Date:	Wed, 9 Apr 2014 11:45:15 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Stefan Bader <stefan.bader@...onical.com>
Cc:	Toralf Förster <toralf.foerster@....de>,
	Michele Ballabio <barra_cuda@...amail.com>,
	linux-kernel@...r.kernel.org, fweisbec@...il.com, mingo@...nel.org,
	Steven Rostedt <rostedt@...dmis.org>,
	David Cohen <david.a.cohen@...ux.intel.com>,
	Paolo Bonzini <pbonzini@...hat.com>,
	Borislav Petkov <bp@...en8.de>
Subject: Re: Bisected KVM hang on x86-32 between v3.12 and v3.13

On Wed, Apr 09, 2014 at 11:14:38AM +0200, Stefan Bader wrote:
> On 08.04.2014 14:21, Peter Zijlstra wrote:
> > On Mon, Apr 07, 2014 at 08:56:58PM +0200, Peter Zijlstra wrote:
> >> 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+
> > 
> > OK.. so could someone test the below patch to see if that makes things
> > work for .13 and .14?
> 
> Hi Peter,
> 
> sorry I only had time to try 3.13 but that looks good. I was able to get kvm up
> and running for a longer than usual (without the patch) amount of time without
> seeing any softlockups.

Great, I suppose I should go write a changelog and talk to Greg about
how to get this into .13 and .14 stable.
--
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/