rt_mutex_start_proxy_lock(9)

✨ rt_mutex_start_proxy_lock ✨

okay bestie, welcome to the Kernel API Manual entry for rt_mutex_start_proxy_lock — this is the one that gets the lock party started for another task, not you. main character energy is elsewhere, and that's fine 🫶

---

🌸 NAME 🌸

rt_mutex_start_proxy_lock — Start lock acquisition for another task

---

🎀 SYNOPSIS 🎀

int rt_mutex_start_proxy_lock (struct rt_mutex_base *lock , struct
rt_mutex_waiter *waiter , struct task_struct *task );

---

💅 ARGUMENTS 💅

• lock — the rt_mutex to take, aka the thing we're all fighting over 💖
• waiter — the pre-initialized rt_mutex_waiter, already dressed and ready to queue
• task — the task to prepare, because we're doing this on their behalf, not ours

---

🦋 DESCRIPTION 🦋

Starts the rt_mutex acquire; it enqueues the waiter and does deadlock detection. It does not wait — see rt_mutex_wait_proxy_lock for that, because waiting is a whole separate vibe and not this function's business, ngl.

Special API call for PI-futex support. iykyk ✨

---

⭐ NOTE ⭐

unlike __rt_mutex_start_proxy_lock, this one _DOES_ remove the waiter on failure. like, it cleans up after itself, we love an accountable icon 💅

---

🔥 RETURN 🔥

• 0 — task blocked on lock
• 1 — acquired the lock for task, caller should wake it up
• <0 — error 😭

---

🌈 SEE ALSO 🌈

Kernel file ./kernel/locking/rtmutex_api.c

• rt_mutex_lock_nested(9)
• rt_mutex_lock(9)
• rt_mutex_lock_interruptible(9)
• rt_mutex_lock_killable(9)
• rt_mutex_trylock(9)
• rt_mutex_unlock(9)
• __rt_mutex_futex_unlock(9)
• __rt_mutex_init(9)
• rt_mutex_init_proxy_locked(9)
• rt_mutex_proxy_unlock(9)
• __rt_mutex_start_proxy_lock(9)
• rt_mutex_wait_proxy_lock(9)
• rt_mutex_cleanup_proxy_lock(9)

---

okay that's the whole page, bestie, slay 💖 this beauty lives under ./kernel/locking and it's dated October 2026, with the header vibe of rt_mutex_start_proxy_lock(9) — go forth and proxy-lock responsibly 🎀🫶