From: Greg KH <gregkh@linuxfoundation.org>
To: Thadeu Lima de Souza Cascardo <cascardo@canonical.com>
Cc: stable@vger.kernel.org, paul.gortmaker@windriver.com,
peterz@infradead.org, bp@suse.de, jpoimboe@kernel.org
Subject: Re: [PATCH 1/3] Revert "x86/ftrace: Use alternative RET encoding"
Date: Tue, 16 Aug 2022 12:23:58 +0200 [thread overview]
Message-ID: <YvtwPpKJ5nqfmTFf@kroah.com> (raw)
In-Reply-To: <YvtueWo2F3ZR/Y3r@quatroqueijos>
On Tue, Aug 16, 2022 at 07:16:25AM -0300, Thadeu Lima de Souza Cascardo wrote:
> On Tue, Aug 16, 2022 at 11:18:52AM +0200, Greg KH wrote:
> > On Tue, Aug 16, 2022 at 05:26:56AM -0300, Thadeu Lima de Souza Cascardo wrote:
> > > This reverts commit 3af2ebf798c52b20de827b9dfec13472ab4a7964.
> > >
> > > This temporarily reverts the backport of upstream commit
> > > 1f001e9da6bbf482311e45e48f53c2bd2179e59c. It was not correct to copy the
> > > ftrace stub as it would contain a relative jump to the return thunk which
> > > would not apply to the context where it was being copied to, leading to
> > > ftrace support to be broken.
> > >
> > > Signed-off-by: Thadeu Lima de Souza Cascardo <cascardo@canonical.com>
> > > ---
> > > arch/x86/kernel/ftrace.c | 7 ++-----
> > > 1 file changed, 2 insertions(+), 5 deletions(-)
> >
> > What stable tree(s) is this to be for?
> >
> > Context is everything :)
> >
> > thanks,
> >
> > greg k-h
>
> Yeah, I was just thinking that I missed it, and whether I would be able to
> respond to my own message before you did. :-)
>
> This series is targed at 5.15. I will look at 5.10 next.
Thanks, I'll queue this up after the current 5.15-rc is released later
this week.
greg k-h
next prev parent reply other threads:[~2022-08-16 10:56 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
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 [this message]
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=YvtwPpKJ5nqfmTFf@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=bp@suse.de \
--cc=cascardo@canonical.com \
--cc=jpoimboe@kernel.org \
--cc=paul.gortmaker@windriver.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.