kmsan_unpoison_entry_regs(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… kmsan_unpoison_entry_regs β€” Kernel API Manual πŸ’…

okay so bestie, welcome to the kmsan_unpoison_entry_regs page, it's a little one but she's iconic ✨ this lives in the Kernel API Manual, and honestly it's giving "short but crucial" energy πŸŽ€

🌸 NAME 🌸

kmsan_unpoison_entry_regs β€” handle pt_regs in low-level entry code πŸ’–

✨ SYNOPSIS ✨

void kmsan_unpoison_entry_regs (const struct pt_regs *regs );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • regs β€” a struct pt_regs pointer that you got straight from assembly code, no cap 🫢

πŸ’… DESCRIPTION πŸ’…

so basically, KMSAN unpoisons the contents of the pt_regs you pass in, and the whole point of that is to stop potential false positive reports from happening 😭 she's out here clearing the vibes so the error detector doesn't start drama over nothing, periodt.

and here's the main character detail πŸ”₯ β€” unlike kmsan_unpoison_memory, this function kmsan_unpoison_entry_regs can be called from the regions where kmsan_in_runtime returns true, which is literally the case in early entry code. so like, she's the one you call when you're in the no-go zone and the regular function can't come with you πŸ’€ iykyk.

ngl, that runtime restriction is the whole reason this function exists separately β€” don't try to swap in kmsan_unpoison_memory and hope for the best, she will not survive early entry code πŸ™ˆ

πŸ‘‘ SEE ALSO πŸ‘‘

kernel file ./include/linux/kmsan.h, plus the whole friend group 🌈:


and that's the whole page bestie, you ate that πŸ“ this lil drop came from ./include/linux and is dated October 2026 β€” mwah, see you in the next manpage πŸ’œπŸ§šβ­

πŸ“¦ where this page comes from