linux-kernel - Re: [PATCH tip/perf] uprobes: avoid false lockdep splat in uprobe timer callback

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20250403175619.2QB0oWe_@linutronix.de>
Date: Thu, 3 Apr 2025 19:56:19 +0200
From: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Andrii Nakryiko <andrii@...nel.org>, linux-trace-kernel@...r.kernel.org,
	peterz@...radead.org, mingo@...nel.org, bpf@...r.kernel.org,
	linux-kernel@...r.kernel.org, kernel-team@...a.com, oleg@...hat.com,
	mhiramat@...nel.org, ast@...nel.org
Subject: Re: [PATCH tip/perf] uprobes: avoid false lockdep splat in uprobe
 timer callback

On 2025-04-03 13:53:31 [-0400], Steven Rostedt wrote:
> On Thu, 3 Apr 2025 19:49:17 +0200
> Sebastian Andrzej Siewior <bigeasy@...utronix.de> wrote:
> 
> > > +	/* See free_ret_instance() for notes on seqcount use.  
> > 
> > This is not a proper multi line comment.
> 
> It's only proper in the networking code, but not the rest of the kernel.

I wasn't aware that uprobe is following networking standards here.

> -- Steve

Sebastian