Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752086AbaKUSYj (ORCPT ); Fri, 21 Nov 2014 13:24:39 -0500 Received: from mail-qa0-f51.google.com ([209.85.216.51]:38658 "EHLO mail-qa0-f51.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751514AbaKUSYg (ORCPT ); Fri, 21 Nov 2014 13:24:36 -0500 MIME-Version: 1.0 In-Reply-To: <20141121123434.279c5613@gandalf.local.home> References: <20141120221122.GA25393@htj.dyndns.org> <20141120230514.GB25393@htj.dyndns.org> <20141120233920.GC25393@htj.dyndns.org> <20141121162742.GB15461@htj.dyndns.org> <20141121170805.GD30603@home.goodmis.org> <20141121123434.279c5613@gandalf.local.home> Date: Fri, 21 Nov 2014 10:24:35 -0800 X-Google-Sender-Auth: 8WyI7v_7HJEGIQwWBKS7eNNTyms Message-ID: Subject: Re: frequent lockups in 3.18rc4 From: Linus Torvalds To: Steven Rostedt Cc: Andy Lutomirski , Tejun Heo , "linux-kernel@vger.kernel.org" , Thomas Gleixner , Arnaldo Carvalho de Melo , Peter Zijlstra , Frederic Weisbecker , Don Zickus , Dave Jones , "the arch/x86 maintainers" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Nov 21, 2014 at 9:34 AM, Steven Rostedt wrote: > > I see. You have issues with the use of current->active_mm instead of > just doing a read_cr3() (and I'm sure other things). Yes. And I have this memory of it actually mattering, where we'd get get the page fault, but see that the (wrong) page table is already populated, and say "ti wasn't a vmalloc fault", and then go down the oops path. Of course, the context switch itself has changed completely over the years, but I think it would still be true with NMI. "active_mm" may point to a different page table than the one the CPU is actually using, and then the whole thing is bogus. Linus -- 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/