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

Message-ID: <20210608092431.2cad44e0@oasis.local.home>
Date:   Tue, 8 Jun 2021 09:24:31 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Vincent Whitchurch <vincent.whitchurch@...s.com>
Cc:     Christoph Hellwig <hch@...radead.org>,
        Ingo Molnar <mingo@...hat.com>, kernel <kernel@...s.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] tracing: Export tracing_start() and tracing_stop()

On Tue, 8 Jun 2021 14:59:27 +0200
Vincent Whitchurch <vincent.whitchurch@...s.com> wrote:

> Right, thanks, that's certainly much simpler.  I'd only used
> tracing_stop() before and never noticed that tracing_on can't be used to
> restart tracing, probably because the kind of problems I used it for
> usually resulted in the system needing a restart anyway to be usable.

You must have been using this from the beginning, because
tracing_stop() was first, but people complained that it was slow and
you couldn't turn it back on. Thus "tracing_off()" was added, and
documented as the "thing to use" (if you looked at the comments around
them). But that was years (decade?) ago.

-- Steve