Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Tue, 28 Mar 2023 18:26:00 -0400
From:   Steven Rostedt <rostedt@goodmis.org>
To:     "Paul E. McKenney" <paulmck@kernel.org>
Cc:     torvalds@linux-foundation.org, mingo@kernel.org,
        linux-kernel@vger.kernel.org, douglas.raillard@arm.com,
        tglx@linutronix.de, rcu@vger.kernel.org, kernel-team@fb.com
Subject: Re: [GIT PULL] Fix rcu_torture_read ftrace event
Message-ID: <20230328182600.32e672ed@gandalf.local.home>
In-Reply-To: <9f32a8e2-7fc3-427b-b1e2-238fe81ce97e@paulmck-laptop>
References: <9f32a8e2-7fc3-427b-b1e2-238fe81ce97e@paulmck-laptop>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Precedence: bulk

On Tue, 28 Mar 2023 10:48:14 -0700
"Paul E. McKenney" <paulmck@kernel.org> wrote:

> ----------------------------------------------------------------
> Urgent RCU pull request for v6.3
> 
> This commit brings the rcu_torture_read event trace into line with
> the new trace tools by replacing this event trace's __field() with the
> corresponding __array().  Without this commit, the new trace tools will
> fail when presented wtih an rcu_torture_read event trace, which is a
> regression from the viewpoint of trace tools users.
> 
> https://lore.kernel.org/all/20230320133650.5388a05e@gandalf.local.home/

Thanks! I'll base my change on top of v6.3-rc5 as that will include this
pull request.

 https://patchwork.kernel.org/project/linux-trace-kernel/patch/20230309221302.642e82d9@gandalf.local.home/

Which the kernel robot flagged as causing a build error due to this RCU
issue ;-)

-- Steve