From: K Prateek Nayak <kprateek.nayak@amd.com>
To: kernel test robot <oliver.sang@intel.com>,
Peter Zijlstra <peterz@infradead.org>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-arch@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [peterz-queue:locking/core] [futex] 58141fa298: Oops:general_protection_fault,probably_for_non-canonical_address#:#[##]SMP
Date: Fri, 10 Jul 2026 13:36:05 +0530 [thread overview]
Message-ID: <2e3a18e4-8746-4df5-b4b1-2d76b3d16940@amd.com> (raw)
In-Reply-To: <202607091538.58e3f39-lkp@intel.com>
Hello Oliver,
On 7/9/2026 1:47 PM, kernel test robot wrote:
> [ 1.259631][ T1] Running RCU Tasks Trace wait API self tests
> [ 1.261867][ T1] posixtimers hash table entries: 1024 (order: 5, 81920 bytes, linear)
> [ 1.264376][ T1] Oops: general protection fault, probably for non-canonical address 0x123456789abcdef: 0000 [#1] SMP
Thank you for the report! This is an unpatched address for the runtime
constant which suggests we are using the address before it is patched.
Following seems to solve it for me on your config:
(Prepared on top of queue:locking/core)
diff --git a/kernel/futex/core.c b/kernel/futex/core.c
index c6af6edf5d7ae..0864c6e8cde78 100644
--- a/kernel/futex/core.c
+++ b/kernel/futex/core.c
@@ -2027,6 +2027,8 @@ static int __init futex_init(void)
runtime_const_init(mask, __futex_mask);
runtime_const_init(ptr, __futex_queues);
+ barrier();
+
BUG_ON(!futex_queues());
for_each_node(n) {
---
Could you please check if this is the same issue you are hitting too?
My default config seems to have been much less aggressive at
optimization to have exposed this problem.
--
Thanks and Regards,
Prateek
prev parent reply other threads:[~2026-07-10 8:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-09 8:17 [peterz-queue:locking/core] [futex] 58141fa298: Oops:general_protection_fault,probably_for_non-canonical_address#:#[##]SMP kernel test robot
2026-07-10 8:06 ` K Prateek Nayak [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=2e3a18e4-8746-4df5-b4b1-2d76b3d16940@amd.com \
--to=kprateek.nayak@amd.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.com \
--cc=peterz@infradead.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