[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200925051518.GA605188@kroah.com>
Date: Fri, 25 Sep 2020 07:15:18 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Naresh Kamboju <naresh.kamboju@...aro.org>
Cc: Joel Fernandes <joel@...lfernandes.org>,
Steven Rostedt <rostedt@...dmis.org>,
Peter Zijlstra <peterz@...radead.org>,
Namhyung Kim <namhyung@...nel.org>,
LKML <linux-kernel@...r.kernel.org>,
linux- stable <stable@...r.kernel.org>,
Sasha Levin <sashal@...nel.org>,
Masami Hiramatsu <mhiramat@...nel.org>,
LTP List <ltp@...ts.linux.it>, lkft-triage@...ts.linaro.org
Subject: Re: [stable 4.19] [PANIC]: tracing: Centralize preemptirq
tracepoints and unify their usage
On Fri, Sep 25, 2020 at 10:13:05AM +0530, Naresh Kamboju wrote:
> >From stable rc 4.18.1 onwards to today's stable rc 4.19.147
>
> There are two problems while running LTP tracing tests
> 1) kernel panic on i386, qemu_i386, x86_64 and qemu_x86_64 [1]
> 2) " segfault at 0 ip " and "Code: Bad RIP value" on x86_64 and qemu_x86_64 [2]
> Please refer to the full test logs from below links.
>
> The first bad commit found by git bisect.
> commit: c3bc8fd637a9623f5c507bd18f9677effbddf584
> tracing: Centralize preemptirq tracepoints and unify their usage
>
> Reported-by: Naresh Kamboju <naresh.kamboju@...aro.org>
So this also is reproducable in 5.4 and Linus's tree right now?
Or are newer kernels working fine?
thanks,
greg k-h
Powered by blists - more mailing lists