[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250403145334.04ac4511@gandalf.local.home>
Date: Thu, 3 Apr 2025 14:53:34 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
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 Thu, 3 Apr 2025 19:56:19 +0200
Sebastian Andrzej Siewior <bigeasy@...utronix.de> wrote:
> 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.
It's not, but I know that Andrii works a bit with the networking code.
-- Steve
Powered by blists - more mailing lists