From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752651AbdIVWSl (ORCPT ); Fri, 22 Sep 2017 18:18:41 -0400 Received: from mail.kernel.org ([198.145.29.99]:52682 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752529AbdIVWSj (ORCPT ); Fri, 22 Sep 2017 18:18:39 -0400 DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org AC8FA214F0 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=goodmis.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=rostedt@goodmis.org Message-Id: <20170922221543.900812109@goodmis.org> User-Agent: quilt/0.63-1 Date: Fri, 22 Sep 2017 18:15:43 -0400 From: Steven Rostedt To: linux-kernel@vger.kernel.org Cc: ngo Molnar , Andrew Morton , "Paul E. McKenney" Subject: [PATCH 0/4] rcu/tracing/extable: Fix stack dump when RCU is not watching Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org I'm currently running this through my test suite, but wanted to get review or acks, so that I can send this right off to Linus before rc2. I need these to base my new work on. Basically if a stack trace happens (say from a WARN()) when RCU is not watching (like going to or coming from idle, or bringing down or up a CPU), the stack trace can cause RCU issues because it requires RCU to be watching. We use rcu_nmi_enter() for this case, as these cases behave similar to an NMI (can happen pretty much anywhere). Paul E. McKenney (1): rcu: Allow for page faults in NMI handlers Steven Rostedt (VMware) (3): extable: Consolidate *kernel_text_address() functions extable: Enable RCU if it is not watching in kernel_text_address() tracing: Remove RCU work arounds from stack tracer ---- kernel/extable.c | 45 +++++++++++++++++++++++++++++++-------------- kernel/rcu/tree.c | 10 ++++++++++ kernel/trace/trace_stack.c | 15 --------------- 3 files changed, 41 insertions(+), 29 deletions(-)