linux-kernel - Re: [PATCH] tracing: Do not set trace clock if tracefs lockdown is in effect

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: <20200116100925.GA157179@kroah.com>
Date:   Thu, 16 Jan 2020 11:09:25 +0100
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Masami Ichikawa <masami256@...il.com>
Cc:     rostedt@...dmis.org, mingo@...hat.com,
        linux-kernel@...r.kernel.org, stable@...r.kernel.org
Subject: Re: [PATCH] tracing: Do not set trace clock  if tracefs lockdown is
 in effect

On Thu, Jan 16, 2020 at 06:47:06PM +0900, Masami Ichikawa wrote:
> When trace_clock option is not set and unstable clcok detected,
> tracing_set_default_clock() sets trace_clock(ThinkPad A285 is one of
> case). In that case, if lockdown is in effect, null pointer
> dereference error happens in ring_buffer_set_clock().
> 
> Link: https://bugzilla.redhat.com/show_bug.cgi?id=1788488
> Signed-off-by: Masami Ichikawa <masami256@...il.com>
> ---
>  kernel/trace/trace.c | 5 +++++
>  1 file changed, 5 insertions(+)


<formletter>

This is not the correct way to submit patches for inclusion in the
stable kernel tree.  Please read:
    https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for how to do this properly.

</formletter>