futex_requeue(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ futex_requeue(9) β€” Kernel API Manual ✨

okay so welcome to the Kernel API Manual, bestie, and specifically to the futex_requeue(9) page. grab your iced coffee 🧊 because this one is short, a little cursed, and extremely deprecated.


πŸ’– NAME πŸ’–

futex_requeue - requeue without expected value comparison, deprecated. yes, β€œdeprecated” is right there in the NAME section, so that’s the vibe check and it did not pass πŸ’€

✨ SYNOPSIS ✨

int futex_requeue (futex_t *uaddr , futex_t *uaddr2 , int nr_wake , int
       nr_requeue , int opflags );

πŸŽ€ ARGUMENTS πŸŽ€

  • uaddr β€” the page literally says -- undescribed --, so we are not out here inventing lore. that’s the whole description, bestie 🫢
  • uaddr2 β€” also literally -- undescribed --. iconic? maybe not, but we respect the honesty πŸ’…
  • nr_wake β€” wake up to this many tasks ✨
  • nr_requeue β€” requeue up to this many tasks πŸŽ€
  • opflags β€” yep, -- undescribed -- again. no cap, that’s what the page gives us πŸ™ˆ

πŸ¦‹ DESCRIPTION πŸ¦‹

Due to its inherently racy implementation, futex_requeue is deprecated in favor of futex_cmp_requeue.

bestie, that’s the actual warning energy: it’s inherently racy and deprecated. use futex_cmp_requeue instead, fr fr 🚨

🌸 SEE ALSO 🌸


cute sign-off time: this page’s source/version footer is ./tools/testing/selftests/fute..., it’s dated October 2026, and the page tag is futex_requeue(9). slay, stay safe, and maybe use the non-deprecated one πŸ’œπŸŒˆ

πŸ“¦ where this page comes from