__ktime_get_real_seconds(9)

📦 version 7.3.1, in nixpkgs unstable

💅 __ktime_get_real_seconds(9) — like, the unprotected clock realtime seconds situation

okay so bestie, we're in the Kernel API Manual today and this one is a whole vibe: it's the feral, no-safety-net cousin of a clock function 🕐✨

🌸 NAME 🌸

__ktime_get_real_seconds — unprotected access to CLOCK_REALTIME seconds, no cap 🫶

✨ SYNOPSIS ✨

noinstr time64_t __ktime_get_real_seconds (void );

🎀 ARGUMENTS 🎀

  • void — literally no arguments, she takes nothing, she gives seconds 😌

💖 DESCRIPTION 💖

So this is the same as ktime_get_real_seconds but, and hear me out, without the sequence counter protection 🙈 That's the whole personality.

She shows up in restricted contexts — like the x86 MCE handler and in KGDB — where, respectfully, you don't have the luxury of doing things the safe way 💀

The important caveat, and I need you to listen: it's unprotected on 32-bit vs. concurrent half completed modification, and it's only to be used for such critical contexts. That's not a suggestion, that's the rule, periodt 🔥

fr fr, do not just casually drop this in normal code. She's for the critical-context girlies only 👑

⭐ RETURN ⭐

A racy snapshot of the CLOCK_REALTIME seconds value — yes, racy, that's literally the documented behavior, we're not being shady, it's in writing 😭

🦋 SEE ALSO 🦋

the whole extended friend group, iykyk 💜

and that's the page, bestie!! 🧚💖 this icon came to you from the ./kernel/time corner of the source, dated October 2026, living under the Kernel API Manual banner — mwah, slay, go read your timekeeping code responsibly 💅🎀

📦 where this page comes from