vdo_wait_unt...ad_only_mode(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ NAME ✨

vdo_wait_until_not_entering_read_only_mode β€” okay so this one waits until literally zero read-only notifications are in progress, and then it locks the door so no new ones can start. bestie it's giving bouncer-at-the-club energy πŸ’…

(this is a page from the Kernel API Manual, welcome to the function-reference corner of the group chat 🫢)


πŸ¦‹ SYNOPSIS πŸ¦‹

void vdo_wait_until_not_entering_read_only_mode (struct vdo_completion *parent );

πŸŽ€ ARGUMENTS πŸŽ€

  • parent β€” the completion you hand over so it can get notified the moment no threads are entering read-only mode anymore. like "hey ping me when the coast is clear" ✨

πŸ’– DESCRIPTION πŸ’–

So the whole vibe here is: this function waits until there are no read-only notifications in progress, and then it prevents any subsequent notifications from happening. no cap, the door is shut πŸ”’

Not me also telling you the escape hatch: notifications may be re-enabled by calling vdo_allow_read_only_mode_entry. that's the "okay you can come back in now" button πŸ’«


🌈 SEE ALSO 🌈


πŸ’€ friendly reminder bestie: read-only mode is serious business β€” this is the kind of entry/exit choreography you do not freestyle. iykyk.

and that's the whole page, mwah πŸ’‹ this gem lives in ./drivers/md/dm-vdo, and your girl October 2026 stamped it β€” slay, iconic, periodt. πŸ§šβ€β™€οΈβœ¨πŸ‘‘

πŸ“¦ where this page comes from