write_seqcount_latch_end(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… write_seqcount_latch_end β€” Kernel API Manual ✨

okay so bestie, welcome to the Kernel API Manual entry for write_seqcount_latch_end πŸ’– this is the girl whose whole job is closing the door behind you after a latch write, and honestly? she ate.


🌸 NAME 🌸

write_seqcount_latch_end β€” end a seqcount_latch_t write section πŸŽ€


✨ SYNOPSIS ✨

void write_seqcount_latch_end (seqcount_latch_t *s );

πŸŽ€ ARGUMENTS πŸŽ€

  • s β€” pointer to seqcount_latch_t 🫢 that's the latch you're closing out, no cap.

πŸ’– DESCRIPTION πŸ’–

Marks the end of a seqcount_latch_t writer section β€” and the timing is everything πŸ’… you call this after all copies of the latch-protected data have been updated. Every single one. All the copies. Updated first, then you end the section. The way that order is not negotiable 😭

Think of it as the "okay we're done, you can look now" moment, except the readers are kernel code and there is no chill ✨


πŸ¦‹ SEE ALSO πŸ¦‹

it's giving family reunion β€” the whole seqlock.h crew lives in the kernel file ./include/linux/seqlock.h 🌈 and here they all are, bestie, every single one:

iykyk πŸ’€ that's the whole group chat and yes they all have (9) after their names, we're being consistent.


not me ending this page without the receipts πŸ™ˆ β€” this one lives under ./include/linux, dated October 2026, and it's filed as write_seqcount_latch_end(9). mwah, go update all your copies first πŸ’‹πŸ¦‹
πŸ“¦ where this page comes from