Received: by 2002:ac0:950c:0:0:0:0:0 with SMTP id f12csp3844493imc; Thu, 14 Mar 2019 06:38:23 -0700 (PDT) X-Google-Smtp-Source: APXvYqxv7XzZBgkZNmD/1hfbqPqKck+GgvbBV3d0iDDlCXUz2ufvjEhdM9mKtjYZHzaTCf0dVW81 X-Received: by 2002:a17:902:25ab:: with SMTP id y40mr50854698pla.62.1552570702838; Thu, 14 Mar 2019 06:38:22 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1552570702; cv=none; d=google.com; s=arc-20160816; b=QxT3sdC45v0nqxjQobEMsiShCcMrh6zjAKoQhOuIze05S7Gt2WeHeHpGTlwK6Pn5Vo RVj1WQteE1nT/duTccB4FxMtH5G4AorSFB8gnyuQNP7b+kClizSxcxV1BwCaqYUyz8E3 CqA06OYIzNboA9fUCODXnHq3gfs2dZRqZUz6hs5h4KJKdDC/iSqoiZvlEFavofRp3n9w rPrTojv+jNJXGoh2n3z3zXxnA5Nljba0yQdMX+Fr8QKY4mKvTjRAX5gzMWITw4P/TXwY +al/FdJhio6Y12kYRSasytjnsHf4DtSCKePFwCw+SeULUSjjOC/E7TPBlkdrZXitEulC b0sg== 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=6/6MUnTfTRqOWkD5iJkQty9j9935YRN/Mg1nN1qHiFc=; b=0QXBZj7FOm3QbtlAt1sdLqeNfjpa3ZtxUj4EelEqdH7QP/DzXhtFyP6gWQ6WGG74a3 qEAwnFlU4cyldCoXjEUNM1UwbU5+kMBq336VpuxVkFYroWSY1+6uIkSrtPDAhxhRUOHU cXa3ruJfD5yic//O9U4et8d5DbuRCD1iuHFh4d47URYTK8Fd+S0M/ygy3EbRXaqZGbI7 xt7D8/P2IW+qLbd1xB1yM4wOOzzCxewbCYxCwXFeMrQUReHMlGWyk0LaY2z5D/xXTuy/ yVmt5BsdXxviXiVcfDDTK6uZ/TJefzEL0GAmQq/Ro7w1Fd4WPNqDR378r7t9YX1n0T5x Ksjw== 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 t12si2376281pgv.477.2019.03.14.06.38.07; Thu, 14 Mar 2019 06:38:22 -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 S1727391AbfCNNhB (ORCPT + 99 others); Thu, 14 Mar 2019 09:37:01 -0400 Received: from mail.kernel.org ([198.145.29.99]:37248 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726845AbfCNNhA (ORCPT ); Thu, 14 Mar 2019 09:37:00 -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 731A32085A; Thu, 14 Mar 2019 13:36:59 +0000 (UTC) Date: Thu, 14 Mar 2019 09:36:57 -0400 From: Steven Rostedt To: Joel Fernandes Cc: "Paul E. McKenney" , 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: <20190314093657.2c1a3485@gandalf.local.home> In-Reply-To: <20190314123159.GB101545@google.com> References: <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> <20190313125125.1a1fb2f3@gandalf.local.home> <20190313180730.GU13351@linux.ibm.com> <20190314123159.GB101545@google.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 Thu, 14 Mar 2019 08:31:59 -0400 Joel Fernandes wrote: > Oh thanks for pointing that out. Yes it does work for me. I agree with the > lockdep API addition and others could benefit from it too. I will incorporate > the lockdep API addition into the RCU patch, but let me know if I should > rather split it. I'd recommend splitting it (adding the lockdep_assert in a patch by itself), but make sure that patch Cc's the lockdep maintainers and explains the reason for adding it. Might as well Cc the lockdep maintainers on the entire series too. -- Steve