linux-kernel - Re: [RFC PATCH v3 0/5] tracing: common 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] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 05 Mar 2019 16:05:42 -0600
From:   Tom Zanussi <zanussi@...nel.org>
To:     Steven Rostedt <rostedt@...dmis.org>
Cc:     tglx@...utronix.de, mhiramat@...nel.org, namhyung@...nel.org,
        bigeasy@...utronix.de, joel@...lfernandes.org,
        linux-kernel@...r.kernel.org, linux-rt-users@...r.kernel.org
Subject: Re: [RFC PATCH v3 0/5] tracing: common error_log for ftrace

Hi Steve,

On Tue, 2019-03-05 at 16:58 -0500, Steven Rostedt wrote:
> On Mon,  4 Mar 2019 17:36:43 -0600
> Tom Zanussi <zanussi@...nel.org> wrote:
> 
> > From: Tom Zanussi <tom.zanussi@...ux.intel.com>
> > 
> > Hi,
> > 
> > This is v3 of the frace error_log RFC patchset, which is the same
> > as
> > the previous version but adds the numbering Masami suggested before
> > each item in the log.  Masami also said he was going to take over
> > the
> > kprobe events patch, but I left it in for now for completeness as
> > it
> > still provides a useful example of possible usage, for evaluation
> > of
> > the overall scheme.  I'll remove it when it's no longer an RFC.
> > 
> > Changes from v2:
> > 
> >   - Added [n] numbering as suggested by Masami
> > 
> > 
> 
> Hi Tom,
> 
> Thanks for doing this!
> 
> Note, I'm marking this as TODO, as the merge window has opened and
> this
> will have to wait till it closes. But that means it may get buried by
> other patches and such marked as TODO. :-p
> 
> Can you send me a friendly reminder in two weeks if you don't hear
> from
> me?
> 

Sure, will do.

Thanks,

Tom

> Thanks!
> 
> -- Steve