public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Borislav Petkov <bp@alien8.de>
Cc: "Paul E. McKenney" <paulmck@kernel.org>,
	linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org,
	x86@kernel.org, peterz@infradead.org, keescook@chromium.org,
	elver@google.com, dvyukov@google.com, glider@google.com
Subject: Re: [BUG] missing return thunk: __ret+0x5/0x7e-__ret+0x0/0x7e: e9 f6 ff ff ff
Date: Thu, 24 Aug 2023 15:52:56 +0200	[thread overview]
Message-ID: <2023082458-vividness-habitable-cbc8@gregkh> (raw)
In-Reply-To: <20230816181720.GNZN0SsKi/B4eCsZHu@fat_crate.local>

On Wed, Aug 16, 2023 at 08:17:20PM +0200, Borislav Petkov wrote:
> Hey Paul,
> 
> On Wed, Aug 16, 2023 at 10:54:09AM -0700, Paul E. McKenney wrote:
> > I hit the splat at the end of this message in recent mainline, and has
> > appeared some time since v6.5-rc1.  Should I be worried?
> 
> does it go away if you try the latest tip:x86/urgent branch?

Note, this problem is showing up in the 6.1.y branch right now, due to
one objtool patch not being able to be backported there easily (i.e. I
tried and gave up.)

4ae68b26c3ab ("objtool/x86: Fix SRSO mess") being the commit that I
can't seem to get to work properly, my attempt can be seen here:
	https://lore.kernel.org/r/2023082212-pregnant-lizard-80e0@gregkh

Just a heads up as this will start to affect users of the next 6.1.y
release, and probably older releases, as they are taking portions of the
"fixes for fixes" but not the above mentioned one.

thanks,

greg k-h

  parent reply	other threads:[~2023-08-24 13:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-16 17:54 [BUG] missing return thunk: __ret+0x5/0x7e-__ret+0x0/0x7e: e9 f6 ff ff ff Paul E. McKenney
2023-08-16 18:17 ` Borislav Petkov
2023-08-16 18:54   ` Paul E. McKenney
2023-08-24 13:52   ` Greg KH [this message]
2023-08-25  6:33     ` Borislav Petkov
2023-08-25  7:15       ` Josh Poimboeuf
2023-08-25  7:24         ` Greg KH
2023-08-25 23:26     ` Josh Poimboeuf
2023-08-26 11:24       ` Greg KH
2023-08-17 20:49 ` Nikolay Borisov
2023-08-17 21:29   ` Paul E. McKenney

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=2023082458-vividness-habitable-cbc8@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=bp@alien8.de \
    --cc=dvyukov@google.com \
    --cc=elver@google.com \
    --cc=glider@google.com \
    --cc=keescook@chromium.org \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@kernel.org \
    --cc=peterz@infradead.org \
    --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