Received: by 2002:ac0:950c:0:0:0:0:0 with SMTP id f12csp3142658imc; Wed, 13 Mar 2019 09:52:15 -0700 (PDT) X-Google-Smtp-Source: APXvYqxjQKXWXl2pLq39s/zM6+NlCzsb5jDjbHh6RDZEUN7QF2HnZp9k9wje6+Qdp0qt/cyfBG0x X-Received: by 2002:a62:e80f:: with SMTP id c15mr44941492pfi.33.1552495935202; Wed, 13 Mar 2019 09:52:15 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1552495935; cv=none; d=google.com; s=arc-20160816; b=g973clEwRWMSkh52na2UcJjmJ0FiXN9065CufN693ENQl3tyBEK7cTZ+DeuTZ08S+2 25bssJ2fRsBNRk8v/2rkgUTRJuWwI9PFATB/fOUBqu29IkuG0VS7j6FzD36qSO/PVHzG 0n+9ox8H65NwHIxCkOA9Tl84thGxPPSKiAX8mSs7GnJQpHjz+AXecG7BHMaZeGMVN/rB MhEzuxtWPRNS9qqc3gpvPZs4CKTd0Z9AWHwHJYUtHiqqf1Q4CJO8b+Gz2NT3XMRtvpT9 63uqqmihY+grl7K7MyodJ98g4P4pP3hNisAE2rugTRI+eZtexp2BfGM9GcFBoYfJdxrJ 38KA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date; bh=UMueyZRLVZOjMzIJIezTn0z9KJ98KKjHx7taJn2/bxI=; b=Ye2Y5QWXt4BwdyNGFdsq/TpMmEkxl0qGCxeib6aXvvkPmu3lP4iE/GlbdjgvLFe7dG 4cQFEF4KS6ufAj1RYllq/MkGQPyntdBtvrz49xhMgcCX5WlLE0cj2I5DqiuF6TWs0SnV KGDb+sVTNUS4KSzhfgXMqf0a07QpXQ1GhHj8VlAzf3TJnJhyBSoCvyJvU6ysWPnIKdPI +76l8UekbyG+PrkA73Gq1aE54RunJcg20WAT91c+K8eAzQgHIwj6MuPcUo/4a0b6GlwE auZvgux4dF70oqdgyqvmrZmZ3AZj2t4BXqIzWeUjG4QtXVM4N9Lb+bb+8bG4DxovFl/Y mU/A== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id h18si3395759pgg.71.2019.03.13.09.51.59; Wed, 13 Mar 2019 09:52:15 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726831AbfCMQv2 (ORCPT + 99 others); Wed, 13 Mar 2019 12:51:28 -0400 Received: from mail.kernel.org ([198.145.29.99]:37542 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726336AbfCMQv2 (ORCPT ); Wed, 13 Mar 2019 12:51:28 -0400 Received: from gandalf.local.home (cpe-66-24-58-225.stny.res.rr.com [66.24.58.225]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id E73C92087C; Wed, 13 Mar 2019 16:51:26 +0000 (UTC) Date: Wed, 13 Mar 2019 12:51:25 -0400 From: Steven Rostedt To: "Paul E. McKenney" Cc: Joel Fernandes , linux-kernel@vger.kernel.org, rcu@vger.kernel.org, jiangshanlai@gmail.com, dipankar@in.ibm.com, mathieu.desnoyers@efficios.com, josh@joshtriplett.org, luto@kernel.org, byungchul.park@lge.com Subject: Re: [PATCH tip/core/rcu 06/19] rcu: Add warning to detect half-interrupts Message-ID: <20190313125125.1a1fb2f3@gandalf.local.home> In-Reply-To: <20190313155155.GN13351@linux.ibm.com> References: <20180829222021.GA29944@linux.vnet.ibm.com> <20180829222047.319-6-paulmck@linux.vnet.ibm.com> <20190311133939.GA29747@google.com> <20190311222903.GR13351@linux.ibm.com> <20190312150514.GB249405@google.com> <20190312152034.GZ13351@linux.ibm.com> <20190313150948.GA84821@google.com> <20190313112726.01d974fc@gandalf.local.home> <20190313155155.GN13351@linux.ibm.com> X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.32; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 13 Mar 2019 08:51:55 -0700 "Paul E. McKenney" wrote: > Does this mean that there is a better approach that Joel's suggestion? > I believe he would end up with something like this: > > WARN_ON_ONCE(IS_ENABLED(CONFIG_PROVE_RCU) && !in_irq()); > > It would be nice if there is something like this: > > lockdep_assert_in_irq_handler(); > > But I haven't seen this. (Not that I have looked particularly hard for > such a thing, mind you!) That would be trivial to implement: #define lockdep_assert_in_irq() do { WARN_ON(debug_locks && !current->hardirq_context); } while (0) -- Steve