linux-kernel - Re: [PATCH] tracing: Kernel access to Ftrace instances

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]

Message-ID: <20190327122912.70bcf31a@gandalf.local.home>
Date:   Wed, 27 Mar 2019 12:29:12 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Divya Indi <divya.indi@...cle.com>
Cc:     linux-kernel@...r.kernel.org, Joe Jin <joe.jin@...cle.com>
Subject: Re: [PATCH] tracing: Kernel access to Ftrace instances

On Wed, 20 Mar 2019 11:28:51 -0700
Divya Indi <divya.indi@...cle.com> wrote:

> Ftrace provides the feature “instances” that provides the capability to
> create multiple Ftrace ring buffers. However, currently these buffers
> are created/accessed via userspace only. The kernel APIs providing these
> features are not exported, hence cannot be used by other kernel
> components.
> 
> This patch aims to extend this infrastructure to provide the
> flexibility to create/log/remove/ enable-disable existing trace events
> to these buffers from within the kernel.
> 
> Signed-off-by: Divya Indi <divya.indi@...cle.com>
> Reviewed-by: Joe Jin <joe.jin@...cle.com>
> ---


I added this to my queue, for 5.2 and then we'll see what it will do.

-- Steve