linux-kernel - Re: [PATCH] tracing: Export tracing_start() and tracing

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, 7 Jun 2021 09:25:19 +0100
From:   Christoph Hellwig <hch@...radead.org>
To:     Vincent Whitchurch <vincent.whitchurch@...s.com>
Cc:     Steven Rostedt <rostedt@...dmis.org>,
        Ingo Molnar <mingo@...hat.com>, kernel@...s.com,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] tracing: Export tracing_start() and tracing_stop()

On Wed, Jun 02, 2021 at 10:01:18AM +0200, Vincent Whitchurch wrote:
> tracing_stop() is very useful during hands-on debugging for getting the
> trace to stop exactly when the problem is detected.  Export this to
> modules.
> 
> Personally, I haven't yet found the need to use tracing_start() from
> code since I usually start tracing via tracefs, but export that too for
> symmetry since it may have its uses together with tracing_stop().

NAK, no exports for unused symbols.