linux-kernel - Re: [PATCH] tracing: fix dynevent test requirements

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]

Date:   Mon, 17 Oct 2022 10:30:00 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Mark Rutland <mark.rutland@....com>
Cc:     linux-kernel@...r.kernel.org, mhiramat@...nel.org,
        Shuah Khan <skhan@...uxfoundation.org>,
        Shuah Khan <shuah@...nel.org>
Subject: Re: [PATCH] tracing: fix dynevent test requirements

On Mon, 17 Oct 2022 10:07:41 +0100
Mark Rutland <mark.rutland@....com> wrote:

> Currently a couple of dynevent tests will always report UNSUPPORTED and
> not run, even when support is actually present.
> 
> In commit:
> 
>   95c104c378dc7d4c ("tracing: Auto generate event name when creating a group of events")
> 
> The README text for synthetic events was changed from:
> 
>   "e[:[<group>/]<event>] <attached-group>.<attached-event> [<args>]\n"
> 
> To:

This was already fixed here:

 https://lore.kernel.org/all/20221010074207.714077-1-svens@linux.ibm.com/

Shuah, can you take Sven's patch through your tree?

Thanks,

-- Steve