From: Steven Rostedt <rostedt@goodmis.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Joel Fernandes <joel@joelfernandes.org>,
Peter Zijlstra <peterz@infradead.org>,
Namhyung Kim <namhyung@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linux- stable <stable@vger.kernel.org>,
Sasha Levin <sashal@kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
LTP List <ltp@lists.linux.it>,
lkft-triage@lists.linaro.org
Subject: Re: [stable 4.19] [PANIC]: tracing: Centralize preemptirq tracepoints and unify their usage
Date: Fri, 25 Sep 2020 10:59:14 -0400 [thread overview]
Message-ID: <20200925105914.7de88d27@oasis.local.home> (raw)
In-Reply-To: <20200925105458.567d0bf4@oasis.local.home>
On Fri, 25 Sep 2020 10:54:58 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:
> The crash looks like its cr3 related, which I believe Peter Zijlstra
s/cr3/cr2/
-- Steve
> did a restructuring of that code to not let it be an issue anymore.
> I'll have to look deeper. The rework may be too intrusive to backport,
> but we do have other work arounds for this issue if that would be
> acceptable for backporting.
>
next prev parent reply other threads:[~2020-09-25 14:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-23 2:38 [lkp-robot] [tracing] c3bc8fd637: WARNING:at_kernel/rcu/tree.c:#rcu_irq_enter kernel test robot
2018-08-28 19:53 ` Joel Fernandes
2020-09-25 4:43 ` [stable 4.19] [PANIC]: tracing: Centralize preemptirq tracepoints and unify their usage Naresh Kamboju
2020-09-25 5:15 ` Greg Kroah-Hartman
2020-09-25 7:25 ` Naresh Kamboju
2020-09-25 14:54 ` Steven Rostedt
2020-09-25 14:59 ` Steven Rostedt [this message]
2020-09-25 15:07 ` Steven Rostedt
2020-09-25 15:12 ` Greg Kroah-Hartman
2020-09-25 15:30 ` Steven Rostedt
2020-10-05 13:18 ` Greg Kroah-Hartman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200925105914.7de88d27@oasis.local.home \
--to=rostedt@goodmis.org \
--cc=gregkh@linuxfoundation.org \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=ltp@lists.linux.it \
--cc=mhiramat@kernel.org \
--cc=namhyung@kernel.org \
--cc=naresh.kamboju@linaro.org \
--cc=peterz@infradead.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®