Received: by 2002:a25:824b:0:0:0:0:0 with SMTP id d11csp1140960ybn; Wed, 25 Sep 2019 13:05:18 -0700 (PDT) X-Google-Smtp-Source: APXvYqzWliRN4uqoKXDyzOhruxt8vngHTLfFFL57DjGWsjInreFYxdPmQLhrLaNKxDmRcCSjbDPT X-Received: by 2002:a17:906:f846:: with SMTP id ks6mr1001042ejb.192.1569441917958; Wed, 25 Sep 2019 13:05:17 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1569441917; cv=none; d=google.com; s=arc-20160816; b=I0hZPkYYfrIZ9D6E2yG3D4B7+ki6OeiLWkJsw0Ki2pueOBTfq2DaGP+kafCaL+pONu cxD86YyFVRpONngxBmyv258bGHOjVXh+3em1wqfSx0PrRb1Bz1p6fvlUq5Lagu+I86oY HRTAhhnxaRmGDr9EpMccMkt8Ki0dJTNSV9iYlnsxWMYFNZwOzVepvLWYtg+OeoBD+4pA A8yGSTcOUfo5kTOWCHajZnsjHU/KbuMX+utnxlPP1TO3lo2BDeYk0A3k11LKyIq8T5hz hei3IXgC9VwIpnlyI3J3zdmWKXAJkOuZKFUhGHJ2pTQCwXJnp2IAbTcza70nsFPm4Jgg yBDQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=DbmdKW63jZm2MSzH1MwZ8lv3NWqTXO5tj2Gn/bQ838M=; b=T4nEC6Vged2+jl7cPOMKHNm//tKsYCiEhlNUgPirNAitGy4Q1pYVLaIklagwnWVtGa dK93tYajluYIyYPbxo//7dySqiJIiwUOS3FhSiSlxj23Qde1q6IE52y/NbRINeGBuL13 tz4dt4OjIgGIelGQNcpHVM51tbT7PTmZRq3mEhwMxlzLo75yuiXPRuVZi02U52Tdz2t2 YMhBYGIqVxQvY4AodhQh8vzuFCk3NZB0FRwGV/HY502+5mGs6xds/z/3y+J3TQH/JIvk YqQ3dKOpLQo2nzFF2HXS7bPD4aPFiUEKmhqdf2zG48s3iDUY8l6LFI76FMSHfeyb8ZWX oP1Q== 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 f21si30440eda.216.2019.09.25.13.04.52; Wed, 25 Sep 2019 13:05:17 -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 S2389767AbfIWQlD (ORCPT + 99 others); Mon, 23 Sep 2019 12:41:03 -0400 Received: from Galois.linutronix.de ([193.142.43.55]:59137 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2387922AbfIWQlD (ORCPT ); Mon, 23 Sep 2019 12:41:03 -0400 Received: from bigeasy by Galois.linutronix.de with local (Exim 4.80) (envelope-from ) id 1iCROW-0001T3-67; Mon, 23 Sep 2019 18:41:00 +0200 Date: Mon, 23 Sep 2019 18:41:00 +0200 From: Sebastian Andrzej Siewior To: Scott Wood Cc: linux-rt-users@vger.kernel.org, linux-kernel@vger.kernel.org, "Paul E . McKenney" , Joel Fernandes , Thomas Gleixner , Steven Rostedt , Peter Zijlstra , Juri Lelli , Clark Williams Subject: Re: [PATCH RT v3 1/5] rcu: Acquire RCU lock when disabling BHs Message-ID: <20190923164059.5hvqttxvh7lxxzas@linutronix.de> References: <20190911165729.11178-1-swood@redhat.com> <20190911165729.11178-2-swood@redhat.com> <20190917074456.yj7t3wdwuhn3zcng@linutronix.de> <63b430ca2f067e61bef1c387fad782ab4a2c1ed3.camel@redhat.com> <20190917144252.v34ina4z2ydchoit@linutronix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20180716 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2019-09-17 11:12:48 [-0500], Scott Wood wrote: > > rcu_read_lock() does: > > > __rcu_read_lock(); > > > __acquire(RCU); > > > rcu_lock_acquire(&rcu_lock_map); > > > RCU_LOCKDEP_WARN(!rcu_is_watching(), > > > "rcu_read_lock() used illegally while idle"); > > > > __acquire() is removed removed by cpp. > > That RCU_LOCKDEP_WARN is doing the same thing as above and redundant. > > Am I right to assume that you consider > > rcu_lock_acquire(&rcu_bh_lock_map); > > > > redundant because the only user of that is also checking for > > rcu_lock_map? > Yes. I'm going to drop that hunk. It makes the patch smaller and result more obvious. If the additional lock annotation (rcu_bh_lock_map) is too much then we can still remove it later entirely (for RT) but for now I would like to keep the changes simple and small. > -Scott Sebastian