All of lore.kernel.org
 help / color / mirror / Atom feed
From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Masami Hiramatsu (Google) <mhiramat@kernel.org>
Cc: Josh Poimboeuf <jpoimboe@kernel.org>,
	"Alan J. Wylie" <alan@wylie.me.uk>,
	linux-kernel@vger.kernel.org, regressions@lists.linux.dev,
	stable@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: "stack state/frame" and "jump dest instruction" errors (was Re: Linux 6.16)
Date: Wed, 30 Jul 2025 17:20:20 +0900	[thread overview]
Message-ID: <20250730172020.00a4dd1ad453d94c7ef47f30@kernel.org> (raw)
In-Reply-To: <20250729224000.2f23f59acc79a78f47c1624f@kernel.org>

On Tue, 29 Jul 2025 22:40:00 +0900
Masami Hiramatsu (Google) <mhiramat@kernel.org> wrote:

> On Mon, 28 Jul 2025 08:42:44 -0700
> Josh Poimboeuf <jpoimboe@kernel.org> wrote:
> 
> > On Mon, Jul 28, 2025 at 09:41:35AM +0100, Alan J. Wylie wrote:
> > > #regzbot introduced: 6.15.8..6.16
> 
> > I don't have time to look at this for at least the next few days, but I
> > suspect this one:
> > 
> >      1a3:	8f ea 78 10 c3 0a 06 00 00 	bextr  $0x60a,%ebx,%eax
> 
> Thanks for finding!
> Indeed, this is encoded by XOP which is not currently supported
> by x86 decodeer. 
> 
> > 
> > in which case the kernel's x86 decoder (which objtool also uses) needs
> > to be updated.
> 
> OK, let me see how XOP works.

I've sent it to;

https://lore.kernel.org/all/175386161199.564247.597496379413236944.stgit@devnote2/

I confirmed it worked with the XOP encoded "bextr".

Thank you,

-- 
Masami Hiramatsu (Google) <mhiramat@kernel.org>

      reply	other threads:[~2025-07-30  8:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-27 21:58 Linux 6.16 Linus Torvalds
2025-07-28  8:41 ` "stack state/frame" and "jump dest instruction" errors (was Re: Linux 6.16) Alan J. Wylie
2025-07-28 15:42   ` Josh Poimboeuf
2025-07-29  5:33     ` Linus Torvalds
2025-07-29 13:40     ` Masami Hiramatsu
2025-07-30  8:20       ` Masami Hiramatsu [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=20250730172020.00a4dd1ad453d94c7ef47f30@kernel.org \
    --to=mhiramat@kernel.org \
    --cc=alan@wylie.me.uk \
    --cc=jpoimboe@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=regressions@lists.linux.dev \
    --cc=stable@vger.kernel.org \
    --cc=torvalds@linux-foundation.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.