public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Breno Leitao <leitao@debian.org>, peterz@infradead.org, bp@alien8.de
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@kernel.org>,
	Vincent Guittot <vincent.guittot@linaro.org>,
	Dietmar Eggemann <dietmar.eggemann@arm.com>
Subject: Re: general protection fault, probably for non-canonical address in pick_next_task_fair()
Date: Thu, 29 Feb 2024 23:58:42 +0100	[thread overview]
Message-ID: <87msri7u8t.ffs@tglx> (raw)
In-Reply-To: <ZeCo7STWxq+oyN2U@gmail.com>

On Thu, Feb 29 2024 at 07:55, Breno Leitao wrote:
> I've been running some stress test using stress-ng with a kernel with some
> debug options enabled, such as KASAN and friends (See the config below).
>
> I saw it in rc4 and the decode instructions are a bit off (as it is here
> also - search for mavabs in dmesg below and you will find something as `(bad)`,
> so I though it was a machine issue. But now I see it again, and I am sharing
> for awareness.

The (bad) is after the faulting instruction, but gives an hint:

  2e:	0f 84 67 ff ff ff    	je     0xffffffffffffff9b
  34:	48 89 ef             	mov    %rbp,%rdi
  37:	e8 cf 70 76 00       	call   0x76710b
  3c:	e9                   	.byte 0xe9

That's an invalid opcode, which means that memory is corrupted.

Thanks,

        tglx

  reply	other threads:[~2024-02-29 22:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-29 15:55 general protection fault, probably for non-canonical address in pick_next_task_fair() Breno Leitao
2024-02-29 22:58 ` Thomas Gleixner [this message]
2024-03-01  3:43 ` Abel Wu
2024-03-01  3:47 ` Abel Wu
2024-03-01  7:14   ` Chen Yu

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=87msri7u8t.ffs@tglx \
    --to=tglx@linutronix.de \
    --cc=bp@alien8.de \
    --cc=dietmar.eggemann@arm.com \
    --cc=leitao@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=vincent.guittot@linaro.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