linux-kernel - Re: [RFC PATCH 0/2] trace: Move trace data to new section _ftrace

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20200218222615.713d542d@gandalf.local.home>
Date:   Tue, 18 Feb 2020 22:26:15 -0500
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Joe Perches <joe@...ches.com>
Cc:     linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH 0/2] trace: Move trace data to new section
 _ftrace_data

On Tue, 18 Feb 2020 19:09:10 -0800
Joe Perches <joe@...ches.com> wrote:

> I don't care about the section name at all.
> 
> I used that name for consistency with _ftrace_event
> in the same file. 
> Perhaps the _ftrace_event section
> name could be renamed to something
> intelligible too.

Yes, that should probably get changed. That's a leftover when we just
called everything "ftrace", but it should have been changed when I
renamed the file from ftrace.h to trace_event.h.

-- Steve