linux-kernel - Re: [PATCH v2 1/4] ftrace: Implement fs notification for preempt/irqsoff tracers

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: <20190506140030.GA234965@google.com>
Date:   Mon, 6 May 2019 10:00:30 -0400
From:   Joel Fernandes <joel@...lfernandes.org>
To:     Viktor Rosendahl <viktor.rosendahl@...il.com>
Cc:     Steven Rostedt <rostedt@...dmis.org>,
        Ingo Molnar <mingo@...hat.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 1/4] ftrace: Implement fs notification for
 preempt/irqsoff tracers

On Mon, May 06, 2019 at 01:54:04AM +0200, Viktor Rosendahl wrote:
> On 5/6/19 1:01 AM, Steven Rostedt wrote:
[snip]
> > Hmm, what about adding a notifier to tracing_max_latency instead? And
> > do it not as a config option, but have it always enabled. It would send a
> > notification when it changes, and that only happens when there's a new
> > max latency. Would that work for you?

That sounds like a much better approach. thanks,

 - Joel