From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Thadeu Lima de Souza Cascardo <cascardo@canonical.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
stable@vger.kernel.org, Peter Zijlstra <peterz@infradead.org>,
Borislav Petkov <bp@suse.de>,
Josh Poimboeuf <jpoimboe@kernel.org>
Subject: Re: v5.15.57 regression - boot panic after retbleed backports with CONFIG_KPROBES_SANITY_TEST=y
Date: Tue, 16 Aug 2022 09:47:57 -0400 [thread overview]
Message-ID: <20220816134757.GF73154@windriver.com> (raw)
In-Reply-To: <YvtHVORl4FqwEM9y@quatroqueijos>
[Re: v5.15.57 regression - boot panic after retbleed backports with CONFIG_KPROBES_SANITY_TEST=y] On 16/08/2022 (Tue 04:29) Thadeu Lima de Souza Cascardo wrote:
> On Tue, Aug 16, 2022 at 12:12:24AM -0400, Paul Gortmaker wrote:
> > Cascardo,
> >
> > Was this a final patch or just a "can you test this so we can better
> > understand the regression" intermediate step? I don't think anyone
> > wants to guess at that or at what you wanted to put in the commit log.
> >
> > It would be nice to close this out vs. leaving it hanging out there.
> >
> > Thanks,
> > Paul.
> > --
>
> Not a final thing, I was catching up on other stuff before I could go back to
> it, was planning on doing it this week. Just need to sort out the order of some
> commits here to get to that end result.
Great - I didn't want to nag, but some new ftrace/kprobe regressions
were reported on a Yocto variant of v5.15 and I immediately thought of
this being the underlying cause and the breakage being more than just
the CONFIG_KPROBES_SANITY_TEST corner case I originally reported.
The good news is that I've tested with your new three pack and that
fixes both new issues. I'll loop back and re-check the original issue
as well for completeness, but if you don't hear from me again, you can
assume that went well too. So, if Greg wants to, feel free to add:
Tested-by: Paul Gortmaker <paul.gortmaker@windriver.com>
Thanks again for fixing this. Much appreciated.
Paul.
--
>
> Cascardo.
>
> >
> > >
> > > thanks,
> > >
> > > greg k-h
next prev parent reply other threads:[~2022-08-16 13:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-05 20:04 v5.15.57 regression - boot panic after retbleed backports with CONFIG_KPROBES_SANITY_TEST=y Paul Gortmaker
2022-08-05 21:13 ` Thadeu Lima de Souza Cascardo
2022-08-06 0:11 ` Paul Gortmaker
2022-08-08 13:48 ` Greg Kroah-Hartman
2022-08-16 4:12 ` Paul Gortmaker
2022-08-16 7:29 ` Thadeu Lima de Souza Cascardo
2022-08-16 13:47 ` Paul Gortmaker [this message]
2022-08-16 8:26 ` [PATCH 1/3] Revert "x86/ftrace: Use alternative RET encoding" Thadeu Lima de Souza Cascardo
2022-08-16 8:26 ` [PATCH 2/3] x86/ibt,ftrace: Make function-graph play nice Thadeu Lima de Souza Cascardo
2022-08-16 8:26 ` [PATCH 3/3] x86/ftrace: Use alternative RET encoding Thadeu Lima de Souza Cascardo
2022-08-16 9:18 ` [PATCH 1/3] Revert "x86/ftrace: Use alternative RET encoding" Greg KH
2022-08-16 10:16 ` Thadeu Lima de Souza Cascardo
2022-08-16 10:23 ` Greg KH
2022-08-19 11:16 ` Greg KH
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=20220816134757.GF73154@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=bp@suse.de \
--cc=cascardo@canonical.com \
--cc=gregkh@linuxfoundation.org \
--cc=jpoimboe@kernel.org \
--cc=peterz@infradead.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;
as well as URLs for NNTP newsgroup(s).