From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750872AbdKYEJk (ORCPT ); Fri, 24 Nov 2017 23:09:40 -0500 Received: from mga07.intel.com ([134.134.136.100]:10927 "EHLO mga07.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750729AbdKYEJj (ORCPT ); Fri, 24 Nov 2017 23:09:39 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.44,450,1505804400"; d="scan'208";a="11761537" Subject: Re: [crash] PANIC: double fault, error_code: 0x0 To: Ingo Molnar , linux-kernel@vger.kernel.org, Andy Lutomirski References: <20171124172411.19476-1-mingo@kernel.org> <20171124202237.oytdkqq25s3ak2ul@gmail.com> Cc: Andy Lutomirski , Thomas Gleixner , "H . Peter Anvin" , Peter Zijlstra , Borislav Petkov , Linus Torvalds From: Dave Hansen Message-ID: <94d21124-6193-6bb3-3f81-e2005ab7e7d2@linux.intel.com> Date: Fri, 24 Nov 2017 20:09:37 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: <20171124202237.oytdkqq25s3ak2ul@gmail.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 11/24/2017 12:22 PM, Ingo Molnar wrote: > [ 8.831002] RIP: 0010:page_fault+0x11/0x60 > [ 8.831002] RSP: 0000:ffffffffff0e7fc8 EFLAGS: 00010046 > [ 8.831002] RAX: 00000000819d4d77 RBX: 0000000000000001 RCX: ffffffff819d4d77 > [ 8.831002] RDX: 0000000000000003 RSI: 0000000000000010 RDI: ffffffffff0e8078 > [ 8.831002] RBP: 0000000000000000 R08: 00007ffd7f1aa530 R09: 00007f9407f98400 > [ 8.831002] R10: 0000000000000007 R11: 0000000000000000 R12: 00007ffd7f1aa680 > [ 8.831002] R13: 00007f9407f91f80 R14: 0000000000000007 R15: 0000000000000000 > [ 8.831002] ? native_iret+0x7/0x7 > [ 8.831002] WARNING: can't dereference iret registers at ffffffffff0e8048 for ip page_fault+0x11/0x60 > [ 8.831002] > [ 8.831002] > [ 8.831002] ? __do_page_fault+0x4c0/0x4c0 > [ 8.831002] ? page_fault+0x2c/0x60 > [ 8.831002] ? native_iret+0x7/0x7 > [ 8.831002] ? __do_page_fault+0x4c0/0x4c0 > [ 8.831002] ? page_fault+0x2c/0x60 > [ 8.831002] ? __entry_text_end+0x1/0x1 > [ 8.831002] Just a stab in the dark from looking at this for a few seconds... Doesn't this stack trace mean we started C-code page fault handing on the sysenter stack? Seems like we missed a switch to the process stack.