From: Johannes Erdfelt <johannes@erdfelt.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@redhat.com>,
live-patching@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
"x86@kernel.org" <x86@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: ftrace regression with CONFIG_UNWINDER_FRAME_POINTER
Date: Mon, 15 Aug 2022 13:29:46 -0700 [thread overview]
Message-ID: <20220815202946.GF3948@sventech.com> (raw)
In-Reply-To: <YvqpnfM9ZdRO6oXa@zn.tnic>
On Mon, Aug 15, 2022, Borislav Petkov <bp@alien8.de> wrote:
> On Mon, Aug 15, 2022 at 04:06:46PM -0400, Steven Rostedt wrote:
> > On Mon, 15 Aug 2022 12:58:28 -0700
> > Johannes Erdfelt <johannes@erdfelt.com> wrote:
> >
> > > I recently ran across an oops with ftrace when using the frame pointer
> > > unwinder. It does not affect Linus' tree (tested 6.0-rc1), but it does
> > > affect 5.15.60 and 5.10.136 (at least, have not tested other kernels).
> > >
> > > It appears to be related to the recently merged retbleed mitigations,
> >
> > If you believe this, then Cc those that are involved with those
> > mitigations, which I did.
>
> Sounds like this one:
>
> https://lore.kernel.org/all/Yu2H%2FRdg%2FU4bHWaY@quatroqueijos/
Ahh, I missed this in my search to see if this was posted already.
The patch in that post appears to solve the oops I'm seeing (at least
on top of 5.15.60).
JE
next prev parent reply other threads:[~2022-08-16 0:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-15 19:58 ftrace regression with CONFIG_UNWINDER_FRAME_POINTER Johannes Erdfelt
2022-08-15 20:06 ` Steven Rostedt
2022-08-15 20:16 ` Borislav Petkov
2022-08-15 20:29 ` Johannes Erdfelt [this message]
2022-08-16 18:57 ` Paul Gortmaker
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=20220815202946.GF3948@sventech.com \
--to=johannes@erdfelt.com \
--cc=bp@alien8.de \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).