read_seqcount_retry(9)

📦 version 7.3.1, in nixpkgs unstable

💅 read_seqcount_retry(9) 💅

okay so bestie, welcome to the Kernel API Manual 🎀 — this is the page for read_seqcount_retry, and it's literally the "are we still valid or nah" checkpoint of the seqcount_t world. stay with me, it's short and it slaps ✨

🌸 NAME 🌸

read_seqcount_retry — end a seqcount_t read critical section 🔚

✨ SYNOPSIS ✨

read_seqcount_retry (s , start );

yes that's it, that's the whole vibe. two args, no drama 🫶

🎀 ARGUMENTS 🎀

  • s — pointer to seqcount_t, or literally any of the seqcount_LOCKNAME_t variants (they all get along 💖)
  • start — the count you got from read_seqcount_begin — you must have grabbed it there, iykyk 👑

🦋 DESCRIPTION 🦋

so read_seqcount_retry closes the read critical section of the given seqcount_t. that's the whole job bestie, it's a closer 🔥

but here's the important part, no cap: if the critical section was invalid, it must be ignored (and typically retried). like, the data you read? not trustworthy, throw it out, run it back 💀🙈

🌈 RETURN 🌈

  • returns true if a read section retry is required 👀
  • else false ✨

👑 SEE ALSO 👑

kernel file ./include/linux/seqlock.h — go read the source bestie, it's giving main character energy 🧚

that's the whole page bestie, go be valid out there 💜

this cutie came from ./include/linux and it's dated October 2026 🍓 mwah, bye 👋✨

📦 where this page comes from