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

[Masami Ichikawa]

On Thu, Jan 16, 2020 at 7:09 PM Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx> wrote:
>
> 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@xxxxxxxxx>
> > ---
> >  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>

Sorry, I'll resend patch without stable mailing list.


-- 
Masami Ichikawa