Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp4340106ybl; Mon, 26 Aug 2019 09:01:09 -0700 (PDT) X-Google-Smtp-Source: APXvYqzl3wol/5FJBF8gIMcb0q1h6GQbmi8kVGEfH39JDvI9zD/YjAsiy1dzxSL8X6wzO4xpoa66 X-Received: by 2002:a62:6489:: with SMTP id y131mr11774693pfb.124.1566835269745; Mon, 26 Aug 2019 09:01:09 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1566835269; cv=none; d=google.com; s=arc-20160816; b=ux2bOVT06oMLsbHBJzeFLRGc5NH801HorU4jGmIdE9f2Cubvt6j9FwmE0m+Tr2OS/Q qkbEIAcRRrb2ZxQJqrFKpjKB//Z5auY31sNrMRvRvYacf75z7fWbT3skY81IaYgw7HKe hz8ZOojPmRg1IrWfaGBIdi31XUKz58aMSRnkAiEwOfKvznRuXDmp7YsZ/pCpv5k8PREk Wojcb8osT7QsY7A9WR1BAZ4JRfnFVnxwG6zKsx9p6TC7De9eMifIi45zEZzmnDOb/nP7 5ZWglJR/e4KSlW8YufLYbyoj++Wwrfb7q06rcpLQx1MbXTf3W/KVqHGuG+kLH9u822SX vv9A== 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=PvCylMFN0bWCySerEJL8M7JQ30jM2B+pxkQQQdP5jxQ=; b=B5wU365JffEA0xJi4g8PSoQx/AsgOQQszJDAyoj5Qg37mQ5iUfBIUyfUYHk8lxgZuA 8S59pcd1W+ThRQ7ARjLwwndaVZVPZT9zJ3gtTyTMK3JWhX0asNRFDa9pqPu8UTJaburx 1X+V1bB3l/uLk/Q4jrBIBJqPpXo6o15h87NbpzULJ1HEagVXvb0yYYiNek9JN1wvccN/ QR+osqvLVp6XkmpmUmQ5hrTFmZ1WUIu4f0OemH/xBFr4soqjOzFEBBqzDkw5EtsQ0RxL 9oNG915DZi8hWlMa0Mg6NmcOPr50l1vaffn5S2WQHRp769yfp7k3TgLYcQ3ymTG2V2hn Y01Q== 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 34si10193578plz.18.2019.08.26.09.00.54; Mon, 26 Aug 2019 09:01:09 -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 S1732082AbfHZP7q (ORCPT + 99 others); Mon, 26 Aug 2019 11:59:46 -0400 Received: from Galois.linutronix.de ([193.142.43.55]:40577 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730995AbfHZP7q (ORCPT ); Mon, 26 Aug 2019 11:59:46 -0400 Received: from bigeasy by Galois.linutronix.de with local (Exim 4.80) (envelope-from ) id 1i2HPD-0000A2-DH; Mon, 26 Aug 2019 17:59:43 +0200 Date: Mon, 26 Aug 2019 17:59:43 +0200 From: Sebastian Andrzej Siewior To: Scott Wood Cc: Joel Fernandes , "Paul E. McKenney" , linux-rt-users@vger.kernel.org, linux-kernel@vger.kernel.org, Thomas Gleixner , Peter Zijlstra , Juri Lelli , Clark Williams Subject: Re: [PATCH RT v2 1/3] rcu: Acquire RCU lock when disabling BHs Message-ID: <20190826155943.zvghokdn3iu2sipx@linutronix.de> References: <20190821231906.4224-1-swood@redhat.com> <20190821231906.4224-2-swood@redhat.com> <20190821233358.GU28441@linux.ibm.com> <20190822133955.GA29841@google.com> <20190823161740.xhntflxs3vlf3xnu@linutronix.de> <40dd3a7e37ed9b3d03c50221dafc7aa137827ce8.camel@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <40dd3a7e37ed9b3d03c50221dafc7aa137827ce8.camel@redhat.com> 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-08-23 14:46:39 [-0500], Scott Wood wrote: > > > Before consolidation, RT mapped rcu_read_lock_bh_held() to > > > rcu_read_lock_bh() and called rcu_read_lock() from > > > rcu_read_lock_bh(). This > > > somehow got lost when rebasing on top of 5.0. > > > > so now rcu_read_lock_bh_held() is untouched and in_softirq() reports 1. > > So the problem is that we never hold RCU but report 1 like we do? > > Yes. I understand the part where "rcu_read_lock() becomes part of local_bh_disable()". But why do you modify rcu_read_lock_bh_held() and rcu_read_lock_bh()? Couldn't they remain as-is? > -Scott Sebastian