write_seqcount_latch_end(9)
π
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 toseqcount_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:
seqcount_init(9)SEQCNT_ZERO(9)__read_seqcount_begin(9)raw_read_seqcount_begin(9)read_seqcount_begin(9)raw_read_seqcount(9)raw_seqcount_try_begin(9)raw_seqcount_begin(9)__read_seqcount_retry(9)read_seqcount_retry(9)raw_write_seqcount_begin(9)raw_write_seqcount_end(9)write_seqcount_begin_nested(9)write_seqcount_begin(9)write_seqcount_end(9)raw_write_seqcount_barrier(9)write_seqcount_invalidate(9)SEQCNT_LATCH_ZERO(9)seqcount_latch_init(9)raw_read_seqcount_latch(9)read_seqcount_latch(9)raw_read_seqcount_latch_retry(9)read_seqcount_latch_retry(9)raw_write_seqcount_latch(9)write_seqcount_latch_begin(9)write_seqcount_latch(9)seqlock_init(9)DEFINE_SEQLOCK(9)read_seqbegin(9)read_seqretry(9)write_seqlock(9)write_sequnlock(9)write_seqlock_bh(9)write_sequnlock_bh(9)write_seqlock_irq(9)write_sequnlock_irq(9)write_seqlock_irqsave(9)write_sequnlock_irqrestore(9)read_seqlock_excl(9)read_sequnlock_excl(9)read_seqlock_excl_bh(9)read_sequnlock_excl_bh(9)read_seqlock_excl_irq(9)read_sequnlock_excl_irq(9)read_seqlock_excl_irqsave(9)read_sequnlock_excl_irqrestore(9)read_seqbegin_or_lock(9)need_seqretry(9)done_seqretry(9)read_seqbegin_or_lock_irqsave(9)done_seqretry_irqrestore(9)scoped_seqlock_read(9)
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 aswrite_seqcount_latch_end(9). mwah, go update all your copies first ππ¦
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms