__rt_mutex_slowlock(9)

🌸 NAME 🌸

Okay bestie, welcome to __rt_mutex_slowlock(9), straight outta the Kernel API Manual. This is the locking slowpath that gets invoked when lock::wait_lock is already held. Yes, you read that right — it's giving “deep kernel locking business” energy, and we're gonna get through it together. 💅

✨ SYNOPSIS ✨

int __rt_mutex_slowlock (struct rt_mutex_base *lock , struct ww_acquire_ctx *ww_ctx , unsigned int state , enum rtmutex_chainwalk chwalk , struct rt_mutex_waiter *waiter , struct wake_q_head *wake_q );

It's declared to return int, and every single parameter is accounted for below. No cap. 🫶

🎀 ARGUMENTS 🎀

• lock — the rtmutex to block lock. That's the lock we're doing the whole slowpath thing for. 🔥
• ww_ctx — the WW mutex context pointer. It's giving “context, but for WW mutexes.” ✨
• state — the task state for sleeping. You know, the vibe the task is in while it snoozes. 😴
• chwalk — indicator whether a full or partial chainwalk is requested. So it literally tells you which chainwalk flavor we're dealing with. 🦋
• waiter — initializer waiter for blocking. This is the waiter that gets initialized for the blocking situation. 🎀
• wake_q — the wake_q to wake tasks after we release the wait_lock. So after the wait_lock is released, this is the wake queue doing the waking. 👑

💜 SEE ALSO 💜

• Kernel file ./kernel/locking/rtmutex.c
• rt_mutex_slowlock_block(9)
• rtlock_slowlock_locked(9)

Signed off from ./kernel/locking, October 2026 edition — source/version and date noted, bestie. Bye and slay your locking journey. 💖✨