From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932164AbbCEIhV (ORCPT ); Thu, 5 Mar 2015 03:37:21 -0500 Received: from userp1040.oracle.com ([156.151.31.81]:34413 "EHLO userp1040.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753132AbbCEIhU (ORCPT ); Thu, 5 Mar 2015 03:37:20 -0500 Date: Thu, 5 Mar 2015 09:38:49 +0100 From: Quentin Casasnovas To: Oleg Nesterov Cc: Dave Hansen , Quentin Casasnovas , Andy Lutomirski , Borislav Petkov , Ingo Molnar , Linus Torvalds , Pekka Riikonen , Rik van Riel , Suresh Siddha , LKML , "Yu, Fenghua" Subject: Re: Oops with tip/x86/fpu Message-ID: <20150305083849.GP4938@chrystal.uk.oracle.com> References: <54F74F59.5070107@intel.com> <20150304190651.GA5589@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150304190651.GA5589@redhat.com> User-Agent: Mutt/1.5.22 (2013-10-16) X-Source-IP: acsinet22.oracle.com [141.146.126.238] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Mar 04, 2015 at 08:06:51PM +0100, Oleg Nesterov wrote: > On 03/04, Dave Hansen wrote: > > > > I'm running a commit from the tip/x86/fpu branch: ae486033b98. It's on > > a system which I normally boot with 'noxsaves'. When I boot without > > 'noxsaves' it is getting a GPF around the time that init is forked off. > > And I assume that (before this commit) the kernel runs fine if you boot > without 'noxsaves'? > > > > > The full oops is below, but addr2line points to the "alternative_input(" > > line in xrstor_state(). > > > > The one that oopses has this in bootup: > > > > xsave: enabled xstate_bv 0x1f, cntxt size 0x3c0 using compacted form > > > > The one that works says: > > > > xsave: enabled xstate_bv 0x1f, cntxt size 0x440 using standard form > > > Thanks. I'll try to investigate tomorrow. > > Well, the kernel crashes because xrstor_state() is buggy, Quentin already > has a fix. > > But #GP should be explained... > Hopefully the couple of fixes to prevent the #GP should be merged soon, but they only cure the symptoms and not the root cause of this issue, I think. Quentin