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;
Date:   Fri, 10 Aug 2018 12:32:46 -0400
From:   Steven Rostedt <rostedt@goodmis.org>
To:     Joel Fernandes <joel@joelfernandes.org>
Cc:     linux-kernel@vger.kernel.org, kernel-team@android.com,
        Boqun Feng <boqun.feng@gmail.com>,
        Byungchul Park <byungchul.park@lge.com>,
        Ingo Molnar <mingo@redhat.com>,
        Masami Hiramatsu <mhiramat@kernel.org>,
        Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
        Namhyung Kim <namhyung@kernel.org>,
        Paul McKenney <paulmck@linux.vnet.ibm.com>,
        Peter Zijlstra <peterz@infradead.org>,
        Thomas Glexiner <tglx@linutronix.de>,
        Tom Zanussi <tom.zanussi@linux.intel.com>
Subject: Re: [PATCH v12 2/3] tracepoint: Make rcuidle tracepoint callers use
 SRCU
Message-ID: <20180810123246.1174ba66@gandalf.local.home>
In-Reply-To: <20180810113554.1df28050@gandalf.local.home>
References: <20180730222423.196630-1-joel@joelfernandes.org>
        <20180730222423.196630-3-joel@joelfernandes.org>
        <20180810113554.1df28050@gandalf.local.home>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Fri, 10 Aug 2018 11:35:54 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:

> Investigating it, it's that when we register more than one event, the
> tracepoint code calls "release_probes" when adding new tracepoints (as
> it updated the tracepoint array), and this is done very early in boot
> up, causing this warning.
> 
> I'm still looking at ways to fix this. Any ideas would help.

I just posted a patch:

 http://lkml.kernel.org/r/20180810123042.51ceddb9@gandalf.local.home

It appears to fix the issue. I'm going to start testing it in my suite.
Does anyone have any concerns about it, or a better solution?

Thanks!

-- Steve