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: <20180326170529.214b7e6e@gandalf.local.home>
Date:   Mon, 26 Mar 2018 17:05:29 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Alexei Starovoitov <alexei.starovoitov@...il.com>
Cc:     Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
        linux-kernel@...r.kernel.org, Alexei Starovoitov <ast@...nel.org>,
        Peter Zijlstra <peterz@...radead.org>,
        Ingo Molnar <mingo@...nel.org>
Subject: Re: [RFC PATCH] tracepoint: Provide tracepoint_kernel_find_by_name

On Mon, 26 Mar 2018 13:48:36 -0700
Alexei Starovoitov <alexei.starovoitov@...il.com> wrote:

> 
> Mathieu, that's not enough.
> Commit log is also wrong.
> It needs to state that something like this is needed only because
> changing for_each_tracepoint_range() semantics will break lttng.
> I'll post a follow up patch shortly.

No it does not. This is needed because I find it cleaner. If you don't
want to pull this into your patch set. I'll pull it into mine.

-- Steve

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ