linux-kernel - Re: [PATCH v4 02/11] rv: Add license identifiers to monitor files

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] [day] [month] [year] [list]

Message-ID: <1115798d35feb54f0cc714dec3bd7fc5a671adc8.camel@redhat.com>
Date: Wed, 05 Mar 2025 13:34:44 +0100
From: Gabriele Monaco <gmonaco@...hat.com>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: linux-kernel@...r.kernel.org, Masami Hiramatsu <mhiramat@...nel.org>, 
	linux-trace-kernel@...r.kernel.org, Ingo Molnar <mingo@...hat.com>, Peter
 Zijlstra <peterz@...radead.org>, Juri Lelli <juri.lelli@...hat.com>
Subject: Re: [PATCH v4 02/11] rv: Add license identifiers to monitor files

On Tue, 2025-03-04 at 12:18 -0500, Steven Rostedt wrote:
> On Tue, 18 Feb 2025 13:31:07 +0100
> Gabriele Monaco <gmonaco@...hat.com> wrote:
> 
> > Some monitor files like the main header and the Kconfig are missing
> > the
> > license identifier.
> > 
> > Add it to those and make sure the automatic generation script
> > includes
> > the line in newly created monitors.
> > 
> > Signed-off-by: Gabriele Monaco <gmonaco@...hat.com>
> > ---
> >  kernel/trace/rv/monitors/wip/Kconfig            | 2 ++
> >  kernel/trace/rv/monitors/wip/wip.h              | 1 +
> >  kernel/trace/rv/monitors/wwnr/Kconfig           | 2 ++
> >  kernel/trace/rv/monitors/wwnr/wwnr.h            | 1 +
> >  tools/verification/dot2/dot2k.py                | 1 +
> >  tools/verification/dot2/dot2k_templates/Kconfig | 2 ++
> >  6 files changed, 9 insertions(+)
> 
> While I'm waiting for Peter's answer on the scheduler tracepoints,
> I'll
> take these first two patches now, as they are agnostic to the rest of
> the
> changes.
> 
> -- Steve
> 

Great, thank you!

I just found a problem in 3/11: current_restore_rtlock_saved_state
doesn't pass the correct state to the new tracepoint.
I'm going to send a V5 and will leave the first 2 patches out.

Gabriele