linux-kernel - Re: [RFC PATCH v2 4/5] tracing: Use tracing error

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: <1550157406.2498.4.camel@kernel.org>
Date:   Thu, 14 Feb 2019 09:16:46 -0600
From:   Tom Zanussi <zanussi@...nel.org>
To:     Masami Hiramatsu <mhiramat@...nel.org>
Cc:     rostedt@...dmis.org, tglx@...utronix.de, namhyung@...nel.org,
        bigeasy@...utronix.de, joel@...lfernandes.org,
        linux-kernel@...r.kernel.org, linux-rt-users@...r.kernel.org
Subject: Re: [RFC PATCH v2 4/5] tracing: Use tracing error_log with kprobe
 events (incomplete)

Hi Masami,

On Thu, 2019-02-14 at 12:13 +0900, Masami Hiramatsu wrote:
> Hi Tom,
> 
> On Wed, 13 Feb 2019 12:17:55 -0600
> Tom Zanussi <zanussi@...nel.org> wrote:
> 
> > From: Tom Zanussi <tom.zanussi@...ux.intel.com>
> > 
> > Here are a few examples of replacing kprobe_events error handling
> > with
> > tracing_log_err() from the new tracing error_log mechanism.  Only a
> > few example errors are converted, and even these are incomplete,
> > since
> > I didn't know where to get the current command and used a dummy
> > string
> > for those.  Also, these are completely untested, just provided for
> > RFC purposes.
> 
> OK, can I take this over? I would like to try to use this framework.
> 

Sure, be my guest. ;-)

Thanks,

Tom