From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id E775C2A9C0 for ; Wed, 17 May 2023 23:25:31 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 11C3FC433D2; Wed, 17 May 2023 23:25:29 +0000 (UTC) Date: Wed, 17 May 2023 19:25:28 -0400 From: Steven Rostedt To: Linus Torvalds Cc: Beau Belgrave , Alexei Starovoitov , Masami Hiramatsu , LKML , linux-trace-kernel@vger.kernel.org, Alexei Starovoitov , Daniel Borkmann , Andrii Nakryiko , bpf , David Vernet , dthaler@microsoft.com, brauner@kernel.org, hch@infradead.org Subject: Re: [PATCH] tracing/user_events: Run BPF program if attached Message-ID: <20230517192528.043adc7a@gandalf.local.home> In-Reply-To: References: <20230516222919.79bba667@rorschach.local.home> <20230517172243.GA152@W11-BEAU-MD.localdomain> <20230517190750.GA366@W11-BEAU-MD.localdomain> <20230517230054.GA195@W11-BEAU-MD.localdomain> X-Mailer: Claws Mail 3.17.8 (GTK+ 2.24.33; x86_64-pc-linux-gnu) Precedence: bulk X-Mailing-List: bpf@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Wed, 17 May 2023 16:14:43 -0700 Linus Torvalds wrote: > On Wed, May 17, 2023 at 4:01=E2=80=AFPM Beau Belgrave wrote: > > > > Do you mind giving me your Signed-off-by for these? =20 >=20 > Assuming you have some test-cases that you've run them through, then yes: Beau, Can you update the tools/testing/selftests/user_events/ to make sure that it triggers the lockdep splat without these updates (assuming that it does trigger without these patches). Then add these patches to make sure the splat goes away. This will confirm that the patches do what is expected of them. I usually run the selftests for tracing and for your user events with lockdep and prove locking enabled. But it may have triggered on something else disabling it when I ran my tests, in which case I sometimes disable that and forget to re-enable it. -- Steve