Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: John Sperbeck <jsperbeck@google.com>
Cc: bp@alien8.de, jpoimboe@kernel.org, patches@lists.linux.dev,
	peterz@infradead.org, stable@vger.kernel.org
Subject: Re: [PATCH] objtool/x86: add missing embedded_insn check
Date: Thu, 26 Oct 2023 10:17:34 +0200	[thread overview]
Message-ID: <2023102648-regalia-unisexual-db49@gregkh> (raw)
In-Reply-To: <CAFNjLiWtmsticUCB+_D_MMqXCtH=RGr4f1avNYhtk+_CVGgsDg@mail.gmail.com>

On Wed, Oct 25, 2023 at 10:35:08PM -0700, John Sperbeck wrote:
> On Wed, Oct 25, 2023 at 10:17 PM Greg KH <gregkh@linuxfoundation.org> wrote:
> >
> > On Thu, Oct 26, 2023 at 01:57:28AM +0000, John Sperbeck wrote:
> > > When dbf460087755 ("objtool/x86: Fixup frame-pointer vs rethunk")
> > > was backported to some stable branches, the check for dest->embedded_insn
> > > in is_special_call() was missed.  Add it back in.
> > >
> > > Signed-off-by: John Sperbeck <jsperbeck@google.com>
> > > ---
> > >
> > >
> > > I think 6.1.y, 5.15.y, and 5.10.y are the LTS branches missing the
> > > bit of code that this patch re-adds.
> >
> > Did you test this and find it solved anything for you?  Your changelog
> > is pretty sparse :(
> >
> > thanks,
> >
> > greg k-h
> 
> I wasn't sure what to write for the comment.  The original backported
> commit said that it prevented this objtool warning:
> 
>     vmlinux.o: warning: objtool: srso_untrain_ret+0xd: call without
> frame pointer save/setup
> 
> But because of the missing piece, the warning still appears.  That is,
> the backport had no effect at all.

Perhaps say that?

> With this patch, the message really is gone in my builds.  Shall I
> resend my patch with an updated comment?

Build warnings going away is good, but does the result still run
properly?

> I also wasn't sure whether a Fixes annotation was appropriate, and
> which commit to reference, if so.

That's fine, just more information might be nice here.

thanks,

greg k-h


      reply	other threads:[~2023-10-26  8:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-26  1:57 [PATCH] objtool/x86: add missing embedded_insn check John Sperbeck
2023-10-26  1:58 ` kernel test robot
2023-10-26  5:17 ` Greg KH
2023-10-26  5:35   ` John Sperbeck
2023-10-26  8:17     ` Greg KH [this message]

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=2023102648-regalia-unisexual-db49@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=bp@alien8.de \
    --cc=jpoimboe@kernel.org \
    --cc=jsperbeck@google.com \
    --cc=patches@lists.linux.dev \
    --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