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 00:12:24 -0400 [thread overview]
Message-ID: <20220816041224.GE73154@windriver.com> (raw)
In-Reply-To: <YvEULC3tjmzgan7J@kroah.com>
[Re: v5.15.57 regression - boot panic after retbleed backports with CONFIG_KPROBES_SANITY_TEST=y] On 08/08/2022 (Mon 15:48) Greg Kroah-Hartman wrote:
> On Fri, Aug 05, 2022 at 08:11:00PM -0400, Paul Gortmaker wrote:
> > [Re: v5.15.57 regression - boot panic after retbleed backports with CONFIG_KPROBES_SANITY_TEST=y] On 05/08/2022 (Fri 18:13) Thadeu Lima de Souza Cascardo wrote:
[...]
> > > Can you try the patch below?
> >
> > [ 2.529263] rcu: Hierarchical SRCU implementation.
> > [ 2.530393] Kprobe smoke test: started
> > [ 2.555965] Kprobe smoke test: passed successfully
> > [ 2.556454] smp: Bringing up secondary CPUs ...
> >
> > As per above, the same spot in the kprobe test seems to manage to not
> > panic anymore and the remainder of the boot looks clean and normal.
> >
> > I tested directly on vanilla v5.15.57.
> >
> > Thanks for the quick response!
>
> Great, can someone send a "real" patch for this then?
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.
--
>
> thanks,
>
> greg k-h
next prev parent reply other threads:[~2022-08-16 7:34 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 [this message]
2022-08-16 7:29 ` Thadeu Lima de Souza Cascardo
2022-08-16 13:47 ` Paul Gortmaker
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=20220816041224.GE73154@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).