Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1761263Ab3JPT5g (ORCPT ); Wed, 16 Oct 2013 15:57:36 -0400 Received: from cdptpa-outbound-snat.email.rr.com ([107.14.166.226]:3213 "EHLO cdptpa-oedge-vip.email.rr.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1760584Ab3JPT5f (ORCPT ); Wed, 16 Oct 2013 15:57:35 -0400 Date: Wed, 16 Oct 2013 15:57:30 -0400 From: Steven Rostedt To: paulmck@linux.vnet.ibm.com Cc: Frederic Weisbecker , LKML , Ingo Molnar , Thomas Gleixner , "H. Peter Anvin" , Andrew Morton , Peter Zijlstra , "x86@kernel.org" , "Wang, Xiaoming" , "Li, Zhuangzhi" , "Liu, Chuansheng" Subject: Re: [PATCH] x86: Remove WARN_ON(in_nmi()) from vmalloc_fault Message-ID: <20131016155730.7fd55ac5@gandalf.local.home> In-Reply-To: <20131016193632.GH4553@linux.vnet.ibm.com> References: <20131015163906.342d8ffa@gandalf.local.home> <20131016114036.GB12773@localhost.localdomain> <20131016084518.44eaf61a@gandalf.local.home> <20131016130856.GE12773@localhost.localdomain> <20131016193632.GH4553@linux.vnet.ibm.com> X-Mailer: Claws Mail 3.9.2 (GTK+ 2.24.20; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-RR-Connecting-IP: 107.14.168.142:25 X-Cloudmark-Score: 0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 822 Lines: 23 On Wed, 16 Oct 2013 12:36:32 -0700 "Paul E. McKenney" wrote: > > Ah but we have an in_interrupt() check in context_tracking_user_enter() that protects > > us against that. > > Here you are relying on the exception being treated as an interrupt, > correct? I don't think so. It's relying on nmi_enter() also makes in_interrupt() return true. Like I said before. An NMI interrupting userspace should be no different than an interrupt interrupting userspace. They both can trigger vmalloc faults, and we should be able to deal with it. -- Steve -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/