__read_seqcount_retry(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ¦‹ __read_seqcount_retry(9) β€” Kernel API Manual πŸ¦‹

πŸ’– NAME πŸ’–

__read_seqcount_retry β€” end a seqcount_t read section w/o barrier

✨ SYNOPSIS ✨

__read_seqcount_retry (s , start );

πŸŽ€ ARGUMENTS πŸŽ€

  • s β€” pointer to seqcount_t or any of the seqcount_LOCKNAME_t variants.
  • start β€” count, from read_seqcount_begin.

πŸ¦‹ DESCRIPTION πŸ¦‹

Okay so __read_seqcount_retry is giving read_seqcount_retry energy, but it has no smp_rmb barrier. No barrier, no cap. Callers should ensure that smp_rmb or equivalent ordering is provided before actually loading any of the variables that are to be protected in this critical section.

Use carefully, only in critical code, and comment how the barrier is provided. πŸ’…

🌈 RETURN 🌈

true if a read section retry is required, else false. Lowkey simple, bestie.

πŸ‘‘ SEE ALSO πŸ‘‘

Kernel file: ./include/linux/seqlock.h β€” the whole seqlock friend group:


okay bye bestie! 🫢✨ this page is sourced from ./include/linux, dated October 2026, and it's all about __read_seqcount_retry(9) πŸŽ€

πŸ“¦ where this page comes from