From: root <admin@windowsforum.com>
To: <mathieu.desnoyers@efficios.com>
Cc: <peterz@infradead.org>,<mingo@redhat.com>,<linux-kernel@vger.kernel.org>,<mjfara@gmail.com>
Subject: [BUG] sched_mm_cid_exit+0xe2: page fault on CID bitmap write with nopti on 6.19.0
Date: Thu, 12 Feb 2026 21:12:13 +0000 [thread overview]
Message-ID: <20260212211213.F1BE52A1C1D@windowsforum.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 5957 bytes --]
To: mathieu.desnoyers@efficios.com
Cc: peterz@infradead.org, mingo@redhat.com, linux-kernel@vger.kernel.org
Subject: [BUG] sched_mm_cid_exit+0xe2: page fault on CID bitmap write with nopti on 6.19.0
Hi Mathieu,
I'm hitting a repeatable page fault in sched_mm_cid_exit() on 6.19.0
when booting with nopti. The crash occurs during process exit
(do_exit -> sched_mm_cid_exit) on an atomic bit-clear (lock btr) of
the CID bitmap. The faulting address is within a 2MB huge page that
returns a permissions violation on supervisor write access.
The bug triggered 8 times over ~20 hours on a single boot, hitting
multiple unrelated processes (git, gce_workload_ce). Eventually D-Bus
died and systemd became non-functional, requiring a hard power-off.
Reproducer:
Boot 6.19.0 with "nopti" (or "mitigations=off") on the cmdline.
Run any workload that spawns and exits processes frequently
(e.g. repeated git operations). Crashes begin within hours.
Workarounds tested:
- CONFIG_SCHED_MM_CID=n: eliminates the crash (confirmed)
- Removing "nopti" from cmdline (PTI enabled): no crash observed
(other spectre/ibrs params remained disabled during this test)
Environment:
Kernel: 6.19.0 (built from kernel.org tarball, LOCALVERSION=-gce)
Config: CONFIG_SCHED_MM_CID=y, CONFIG_CPU_MITIGATIONS=y (but
mitigations disabled at boot via cmdline, see below)
Boot params: nospectre_v1 nospectre_v2 spectre_v2=off
spec_store_bypass_disable=off nopti noibrs noibpb
no_stf_barrier mitigations=off
CPU: Intel Xeon Platinum 8581C @ 2.30GHz
(pcid, invpcid, la57, 52-bit physical / 57-bit virtual)
Platform: Google Compute Engine VM
8 vCPUs, 4 cores (HT), 30GB RAM, single NUMA node
Preemption: PREEMPT_NONE, HZ_250
Modules: all unsigned (E taint) — stock: xfs, nft_compat,
aesni_intel, virtio_rng, ip_tables, etc.
Full .config available on request.
All 8 crashes share identical characteristics:
- RIP: sched_mm_cid_exit+0xe2/0x200
- Fault type: supervisor write, permissions violation (error 0x0003)
- PMD: 2MB huge page mapping (bit 7 set), dirty+accessed
- Affected process exits with irqs disabled and preempt_count 1
Crash summary (oops #1-#2 occurred early in the boot but were not
captured by journald; the D taint on #3 confirms prior oopses):
Oops Time Process CPU Fault address PMD
#3 16:21:40 git[872493] 0 ff12983438c79bd0 80000001f8c001a1
#4 16:24:26 git[874084] 3 ff1298343a86c5d0 80000001fa8001a1
#5 16:33:52 git[882005] 0 ff1298343a86b0d0 80000001fa8001a1
#6 16:49:41 gce_workload_ce[919343] 4 ff1298343a868dd0 80000001fa8001a1
#7 18:54:23 git[982223] 1 ff1298343a86e8d0 80000001fa8001a1
#8 19:27:13 git[1010036] 6 ff1298343a86bed0 80000001fa8001a1
Observations:
- Oopses #4-#8 all fault within the same PMD (80000001fa8001a1) at
different offsets, suggesting the 2MB huge page mapping for the CID
bitmap has incorrect write permissions, rather than individual
bitmap entries being corrupted.
- Oops #3 uses a different PMD (80000001f8c001a1), indicating the
issue can affect multiple huge page mappings.
- Crashes occur on all CPUs (0,1,3,4,6) — not tied to a specific
core.
- Not process-specific: both git (via exit(2) syscall) and
gce_workload_ce (via signal delivery -> do_group_exit) trigger it.
Full oops from first captured occurrence (#3):
BUG: unable to handle page fault for address: ff12983438c79bd0
#PF: supervisor write access in kernel mode
#PF: error_code(0x0003) - permissions violation
PGD 1fba01067 P4D 1fba02067 PUD 1002a0063 PMD 80000001f8c001a1
Oops: Oops: 0003 [#3] SMP NOPTI
CPU: 0 UID: 0 PID: 872493 Comm: git Tainted: G D E 6.19.0-gce #1 PREEMPT(none)
Tainted: [D]=DIE, [E]=UNSIGNED_MODULE
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/24/2025
RIP: 0010:sched_mm_cid_exit+0xe2/0x200
Code: 48 03 05 29 54 44 02 8b 10 81 e2 ff ff ff bf 89 10 8b 05 51 0b fa 01 83 c0 3f c1 e8 03 25 f8 ff ff 1f 48 8d 84 43 c0 06 00 00 <f0> 48 0f b3 10 48 81 f9 ff ef ff ff 77 0c 48 8d bb 10 01 00 00 e8
RSP: 0018:ff7720274e6a3b58 EFLAGS: 00010002
RAX: ff12983434c79bd0 RBX: ff12983434c79500 RCX: ff12983434c7960f
RDX: 0000000020000006 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ff7720274e6a3b80 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
R13: ff129836b560b180 R14: ff129833634d0000 R15: ff129833634d0000
FS: 000077b36aadc6c0(0000) GS:ff12983a5742b000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ff12983438c79bd0 CR3: 0000000351154002 CR4: 0000000000371ef0
Call Trace:
<TASK>
do_exit+0xc3/0xa00
__x64_sys_exit+0x1b/0x20
x64_sys_call+0x234d/0x2360
do_syscall_64+0x7b/0x580
? _raw_spin_unlock_irq+0xe/0x50
? __x64_sys_rt_sigprocmask+0xdd/0x160
? x64_sys_call+0x160f/0x2360
? do_syscall_64+0xb4/0x580
? __do_sys_newfstatat+0x56/0x90
? __x64_sys_newfstatat+0x1c/0x30
? x64_sys_call+0x1510/0x2360
? do_syscall_64+0xb4/0x580
? __x64_sys_newfstatat+0x1c/0x30
? x64_sys_call+0x1510/0x2360
? do_syscall_64+0xb4/0x580
? x64_sys_call+0x1510/0x2360
? do_syscall_64+0xb4/0x580
? exc_page_fault+0x8b/0x180
entry_SYSCALL_64_after_hwframe+0x76/0x7e
</TASK>
Modules linked in: xt_comment(E) nft_compat(E) tcp_diag(E) inet_diag(E)
8021q(E) garp(E) mrp(E) nls_iso8859_1(E) xfs(E) intel_rapl_msr(E)
intel_rapl_common(E) intel_uncore_frequency_common(E)
ghash_clmulni_intel(E) aesni_intel(E) rapl(E) pvpanic_mmio(E)
pvpanic(E) mac_hid(E) efi_pstore(E) virtio_rng(E) ip_tables(E)
---[ end trace 0000000000000000 ]---
note: git[872493] exited with irqs disabled
note: git[872493] exited with preempt_count 1
Thanks,
next reply other threads:[~2026-02-12 21:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-12 21:12 root [this message]
2026-02-12 21:19 ` Mathieu Desnoyers
2026-02-12 23:21 ` Thomas Gleixner
2026-02-13 11:16 ` Greg Kroah-Hartman
2026-02-12 21:13 mjfara
2026-02-12 21:14 mjfara
2026-02-12 21:33 Mike Fara
2026-02-12 22:28 Mike Fara
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=20260212211213.F1BE52A1C1D@windowsforum.com \
--to=admin@windowsforum.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@redhat.com \
--cc=mjfara@gmail.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
all inboxes | Powered by JetHome®