From: Borislav Petkov <bp@alien8.de>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Johannes Erdfelt <johannes@erdfelt.com>,
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 22:16:29 +0200 [thread overview]
Message-ID: <YvqpnfM9ZdRO6oXa@zn.tnic> (raw)
In-Reply-To: <20220815160646.0dca7227@gandalf.local.home>
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/
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2022-08-15 23:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220815195828.GE3948@sventech.com>
2022-08-15 20:06 ` ftrace regression with CONFIG_UNWINDER_FRAME_POINTER Steven Rostedt
2022-08-15 20:16 ` Borislav Petkov [this message]
2022-08-15 20:29 ` Johannes Erdfelt
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=YvqpnfM9ZdRO6oXa@zn.tnic \
--to=bp@alien8.de \
--cc=johannes@erdfelt.com \
--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