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: <20170921162027.1eb0d8c7@gandalf.local.home>
Date:   Thu, 21 Sep 2017 16:20:27 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Tom Zanussi <tom.zanussi@...ux.intel.com>
Cc:     tglx@...utronix.de, mhiramat@...nel.org, namhyung@...nel.org,
        vedang.patel@...el.com, bigeasy@...utronix.de,
        joel.opensrc@...il.com, joelaf@...gle.com,
        mathieu.desnoyers@...icios.com, baohong.liu@...el.com,
        linux-kernel@...r.kernel.org, linux-rt-users@...r.kernel.org
Subject: Re: [PATCH v2 00/40] tracing: Inter-event (e.g. latency) support

On Tue, 19 Sep 2017 13:44:28 -0500
Tom Zanussi <tom.zanussi@...ux.intel.com> wrote:

> Yeah, it's almost ready.  At this point, I've addressed all the comments
> except for:
> 
>  - PATCH v2 25/40] tracing: Add support for dynamic tracepoints
> 
>  which I need to do a little bit of research on to figure out what
> exactly I need to do there.

Let me know if you need any help.

> 
> I was also kind of looking for a couple patches from you to fold in
> which you had mentioned you were going to send for:
> 
>  -  [PATCH v2 35/40] tracing: Reverse the order event_mutex/trace_types_lock are taken

OK, I have a stand alone patch that you don't need to fold in that does
this properly. I tested the crap out of it (missed a few places), but
should be good. I'll send that netx.


>  -  [PATCH v2 40/40] tracing: Add trace_event_buffer_reserve() variant that allows recursion

I have this working too, but want to test it a little more before
sending. Once I do, you can add both patches ahead of your series. I
may just apply them to my tree now and start running them through my
formal tests.

> 
> I've been using the trace_recursive_lock() patch you posted in place of
> the latter and it's working fine.  :-)

Thanks!

-- Steve

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ