Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp3713218imm; Mon, 30 Jul 2018 02:00:53 -0700 (PDT) X-Google-Smtp-Source: AAOMgpd5QsGOITFBpXZvPJUYQMvWx9iNFOWhPq+yzQI4zoWCWWphNkkmCM6u/nPuPVnCUrPcfbiL X-Received: by 2002:a63:ab0c:: with SMTP id p12-v6mr15473342pgf.190.1532941253695; Mon, 30 Jul 2018 02:00:53 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1532941253; cv=none; d=google.com; s=arc-20160816; b=n/c9+pvmRE+TpZ/zCQAYR5vYWkhLKqLwSzoUcpdIMDhacrIn75qHO+8hoV0r/oLj/e hh3qViCu0hoF4//8zjmJALG+QtKVabXr4v7IizjXhcpX9IH9/7ThNvdBCLRiopUIUUS8 Ey893POZA8Nn7XizMrTg5RwFF5FR1aa15zRyjZZcXRlgnq2rYJo5SstOXJq/a7YT2Xi1 F7ogAx3CAZox9D10rfOqjfvMv8xyGkSvvQVN0Ogl90Tf7sVcVgC65aOXS8l7iUFkXIFl 6jgC4tnWpLw1K/bTS2QcyTzkOX26nFwem7FrdbhghIIMQICOy9hOo05fdg+qWuaxjPAe JiIg== 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:dkim-signature:arc-authentication-results; bh=Y+X3vxVdsP+CFbA4NZjUWZ+qIthYSfvbpCPqjuFSiMA=; b=o4jk0jMLAw0bqnLM0pQV3wVfB8epVoPTmd8ssOkLRyoc5Pkzt+mPGGyzzkGznbKS9O Wlm2iUEHZN6sF8j+iX8yboP7FRH4QQJl6vLuB39kPgjxJOwvfjmjrL9jqKTyVte3vSIV luxGZTbGm8OlGsYqulXWjF+f4p1L81YLvpIXDObtJX5Ybm8RzhtDLbvpDmRtMNXNypL5 jvtNOj6FCXJYyj77EDXvFKWArTYBDAG24n3cqXq7q1vbh538oPJ1tNEBfk+7lDqzWyb5 k5W9Lo8p9zFGgupB2sPsCPsllBp19an5B52RprY7NqegJ1cNoZTJzZP0yvgLiXuFK6BH ipTQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@infradead.org header.s=bombadil.20170209 header.b=iH1My6uU; 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 c31-v6si10046151pgl.126.2018.07.30.02.00.39; Mon, 30 Jul 2018 02:00:53 -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; dkim=fail header.i=@infradead.org header.s=bombadil.20170209 header.b=iH1My6uU; 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 S1726790AbeG3Kc2 (ORCPT + 99 others); Mon, 30 Jul 2018 06:32:28 -0400 Received: from bombadil.infradead.org ([198.137.202.133]:58520 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726664AbeG3Kc1 (ORCPT ); Mon, 30 Jul 2018 06:32:27 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=bombadil.20170209; h=In-Reply-To:Content-Type:MIME-Version :References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=Y+X3vxVdsP+CFbA4NZjUWZ+qIthYSfvbpCPqjuFSiMA=; b=iH1My6uU3dwpY1MihdtC4EkKH vx2+Wnt6rshbmAl20Qjtgg6WqY8V5i2xEzYj4IdPGwIXfspK+zDLPMZzi/fd86d3927jAU7f5IJA+ ZGMWUTGFn0ITLHm906jHuzDW3HiqVSvkc4e0TzkSi/fBC4T8HBnpcyNHH4+QqSkHWKNJo45RzNtsD mJgi2cUTawSp0qZD79pf0AZJERW4Zc63DhbXmkIc/qPNfv0Cy3LYFjR8L/QLAH0LxZh7OP+eW95nG WlVi2VjElwdNMqwkJjkd9wzCLY+xHUmXbrOh6ErhZGdfCo8MPjFOBikFWREj/Q0FwZq1fPqkRe+mz y8jgaZRuw==; Received: from j217100.upc-j.chello.nl ([24.132.217.100] helo=hirez.programming.kicks-ass.net) by bombadil.infradead.org with esmtpsa (Exim 4.90_1 #2 (Red Hat Linux)) id 1fk40O-0003FI-00; Mon, 30 Jul 2018 08:58:16 +0000 Received: by hirez.programming.kicks-ass.net (Postfix, from userid 1000) id EC5B820268325; Mon, 30 Jul 2018 10:58:13 +0200 (CEST) Date: Mon, 30 Jul 2018 10:58:13 +0200 From: Peter Zijlstra To: Joel Fernandes Cc: linux-kernel@vger.kernel.org, kernel-team@android.com, Boqun Feng , Byungchul Park , Erick Reyes , Ingo Molnar , Julia Cartwright , Masami Hiramatsu , Mathieu Desnoyers , Namhyung Kim , Paul McKenney , Steven Rostedt , Thomas Glexiner , Todd Kjos , Tom Zanussi , Will Deacon Subject: Re: [PATCH v11 3/3] tracing: Centralize preemptirq tracepoints and unify their usage Message-ID: <20180730085813.GB2494@hirez.programming.kicks-ass.net> References: <20180726235044.10195-1-joel@joelfernandes.org> <20180726235044.10195-4-joel@joelfernandes.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180726235044.10195-4-joel@joelfernandes.org> User-Agent: Mutt/1.10.0 (2018-05-17) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jul 26, 2018 at 04:50:44PM -0700, Joel Fernandes wrote: > One note, I have to check for lockdep recursion in the code that calls > the trace events API and bail out if we're in lockdep recursion > protection to prevent something like the following case: a spin_lock is > taken. Then lockdep_acquired is called. That does a raw_local_irq_save > and then sets lockdep_recursion, and then calls __lockdep_acquired. In > this function, a call to get_lock_stats happens which calls > preempt_disable, which calls trace IRQS off somewhere which enters my > tracepoint code and sets the tracing_irq_cpu flag to prevent recursion. > This flag is then never cleared causing lockdep paths to never be > entered and thus causing splats and other bad things. That is now fixed, right?