synchronize_rcu_tasks_rude(9)

💅 synchronize_rcu_tasks_rude(9) — Kernel API Manual, but make it group-chat ✨

🌸 NAME 🌸

<pink>synchronize_rcu_tasks_rude</pink> — bestie, this one waits for a rude rcu-tasks grace period to finish. Periodt.

✨ SYNOPSIS ✨

void synchronize_rcu_tasks_rude (void );

🎀 ARGUMENTS 🎀

• void — literally no arguments, bestie. Nothing to pass, nothing to stress about.

🦋 DESCRIPTION 🦋

Ok so here’s the vibe: control comes back to whoever called this some time after a rude rcu-tasks grace period has elapsed. In other words? After all currently executing rude rcu-tasks read-side critical sections have elapsed. Slay.

These read-side critical sections are delimited by calls to:

• schedule
• cond_resched_tasks_rcu_qs
• userspace execution (which is a schedulable context)
• and, in theory, anyway, cond_resched

This is a very specialized primitive, intended only for a few uses in tracing and other situations requiring manipulation of function preambles and profiling hooks. The synchronize_rcu_tasks_rude function is not (yet) intended for heavy use from multiple CPUs. So don’t be out here spamming it from every CPU like it’s a group chat, okay? 💀

For the memory ordering guarantees tea, see the description of synchronize_rcu — it has the more detailed info. 🫶

🌈 SEE ALSO 🌈

• Kernel file ./kernel/rcu/tasks.h
• struct rcu_tasks_percpu(9)
• struct rcu_tasks(9)
• call_rcu_tasks(9)
• synchronize_rcu_tasks(9)
• rcu_barrier_tasks(9)

Okay bestie, that’s the whole page. Source/version vibe: ./kernel/rcu; date: October 2026; and the star of the show is synchronize_rcu_tasks_rude(9). Go off, but only for those few specialized uses, mwah 💖✨