Received: by 2002:a25:824b:0:0:0:0:0 with SMTP id d11csp1140340ybn; Wed, 25 Sep 2019 13:04:48 -0700 (PDT) X-Google-Smtp-Source: APXvYqzyR00oXg50SEYomJD4YAgSwmkOI/GT0DaI8I5BfZsNP8gzF0R/Th3uipibrCYzlwhEokHM X-Received: by 2002:a17:906:2f10:: with SMTP id v16mr909941eji.247.1569441888855; Wed, 25 Sep 2019 13:04:48 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1569441888; cv=none; d=google.com; s=arc-20160816; b=vz4ONyUt9tfTb0GiIJ4CwXlAgiZQVgggzNLo8jQTvrvXzZjtQbr8RYv3Rnxx+wv1Qx nV9W7Q7zHP6UxrwXs+jm505xdXCVYAwKnSxtFyWX2Mtkc/ev5ibwPKJTOlxmue6uctyS 7r5qJdbnEadoj9iBWzUiZlScNXrNkEEdfNxFIQvUdDKW9SkBf8HvTDbmglJW+S9L7Q/N y87p3SFC0ZbTPQLp5lO1kW5rUJhV11ib4OKP40J0dSHiTURquz/aEHjvdaTNM9pf0CG0 q5N+d/GoJ2kKhdLk4CjIOTdDiek4CMbWw6M9ba16PhCIwp5dhzLI5IMJ0T6M1FUPmZVf FTeA== 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=ssGNXBdNhrgQmoVfZWaqx1FWAsPEYJp0mLUbIUIfXyw=; b=HQ3+N4LhXXzO6mIoMAdM6s0gNPJNJyDrFNEKuhdbD5Qfaltffaj2lLMVtdu0bY4YfO AKEKeyTKh/bP60B6Nodsw5cXDEqhck3oLKi2KQFV5rGTv9J6CxoyfunS9+en39KwcuQ3 6DszIw97YB0xs2j6kjicZfVDgoO024OLxqknFdKkDOizzaWHyvHNLzilS6U4YgHrlbI0 NqQB2qve5Pvur+qJ4oQesZoVjC5xkXeQRRLjzuzXP7d1SnNMjK+9zA45VF3qzYvHriEH scRIuo6OqtNeM7F35WOiot4VmKSgZB/4el1mv8j0ifV/CtVpvTZRaVDHSfX3Rb2zw8us e4eQ== 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 h3si24726edh.372.2019.09.25.13.04.20; Wed, 25 Sep 2019 13:04:48 -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 S2389292AbfIWQZJ (ORCPT + 99 others); Mon, 23 Sep 2019 12:25:09 -0400 Received: from Galois.linutronix.de ([193.142.43.55]:59085 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2387922AbfIWQZI (ORCPT ); Mon, 23 Sep 2019 12:25:08 -0400 Received: from bigeasy by Galois.linutronix.de with local (Exim 4.80) (envelope-from ) id 1iCR96-0001Bb-0f; Mon, 23 Sep 2019 18:25:04 +0200 Date: Mon, 23 Sep 2019 18:25:03 +0200 From: Sebastian Andrzej Siewior To: Scott Wood Cc: Joel Fernandes , linux-rt-users@vger.kernel.org, linux-kernel@vger.kernel.org, "Paul E . McKenney" , Thomas Gleixner , Steven Rostedt , Peter Zijlstra , Juri Lelli , Clark Williams Subject: Re: [PATCH RT v3 5/5] rcutorture: Avoid problematic critical section nesting on RT Message-ID: <20190923162503.unezmzawx5vylkbh@linutronix.de> References: <20190911165729.11178-1-swood@redhat.com> <20190911165729.11178-6-swood@redhat.com> <20190912221706.GC150506@google.com> <500cabaa80f250b974409ee4a4fca59bf2e24564.camel@redhat.com> <20190917100728.wnhdvmbbzzxolef4@linutronix.de> <26dbecfee2c02456ddfda3647df1bcd56d9cc520.camel@redhat.com> <20190917145035.l6egzthsdzp7aipe@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:32:11 [-0500], Scott Wood wrote: > Nice! Are the "false positives" real issues from components that are > currently blacklisted on RT, or something different? So first a little bit of infrastructure like commit d5096aa65acd0 ("sched: Mark hrtimers to expire in hard interrupt context") is required so lockdep can see it all properly without RT enabled. Then we need patches to avoid lockdep complaining about things that are not complained about in RT because the lock is converted to raw_spinlock_t or something different is applied so we don't have the warning. > -Scott Sebastian