same_state_synchronize_rcu(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… NAME πŸ’…

welcome to the Kernel API Manual, bestie β€” today’s main character is same_state_synchronize_rcu (yes, the (9) is part of the whole vibe ✨), and the question on the table is: are two old-state values identical? πŸ‘€


πŸŽ€ SYNOPSIS πŸŽ€

the whole mood, exactly as written:

bool same_state_synchronize_rcu (unsigned long oldstate1 , unsigned long
       oldstate2 );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • oldstate1 β€” the first old-state value, bestie 🫢
  • oldstate2 β€” the second old-state value, no cap πŸ’…

✨ DESCRIPTION ✨

okay so here’s the tea, and it’s actually simple: both old-state values must have been obtained from either get_state_synchronize_rcu, start_poll_synchronize_rcu, or get_completed_synchronize_rcu. that’s the rule β€” not me making stuff up, it’s literally the requirement πŸ’–

then the function returns true if the two values are identical and false otherwise. cute, right? it’s giving tiny bool energy.

this lets structures whose lifetimes are tracked by old-state values push these values to a list header, and that allows those structures to be slightly smaller. slay for memory efficiency, honestly 🌸


🌈 SEE ALSO 🌈

go read these too, bestie β€” all of them, in this exact order, because the lore is real:


πŸŽ€ that’s the whole page, bestie β€” source/version ./include/linux, date October 2026, and the title stays same_state_synchronize_rcu(9) πŸŽ€

πŸ“¦ where this page comes from