linux-kernel - Re: ftrace regression with CONFIG_UNWINDER_FRAME

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20220816185716.GA75067@windriver.com>
Date:   Tue, 16 Aug 2022 14:57:16 -0400
From:   Paul Gortmaker <paul.gortmaker@...driver.com>
To:     Johannes Erdfelt <johannes@...felt.com>
Cc:     Borislav Petkov <bp@...en8.de>,
        Steven Rostedt <rostedt@...dmis.org>,
        Ingo Molnar <mingo@...hat.com>, live-patching@...r.kernel.org,
        LKML <linux-kernel@...r.kernel.org>,
        "x86@...nel.org" <x86@...nel.org>,
        Thomas Gleixner <tglx@...utronix.de>,
        Josh Poimboeuf <jpoimboe@...hat.com>,
        Peter Zijlstra <peterz@...radead.org>
Subject: Re: ftrace regression with CONFIG_UNWINDER_FRAME_POINTER

[Re: ftrace regression with CONFIG_UNWINDER_FRAME_POINTER] On 15/08/2022 (Mon 13:29) Johannes Erdfelt wrote:

> On Mon, Aug 15, 2022, Borislav Petkov <bp@...en8.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@...felt.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).

Note that if you reload that thread, you'll see what you tested was not
a full fix - a series of three commits is pending for 5.15-stable now.

Paul.
--

> 
> JE
>