ww_mutex_trylock(9)

📦 version 7.3.1, in nixpkgs unstable

💅 ww_mutex_trylock — kernel API manual, bestie edition 💅

okay so this is a page from the Kernel API Manual, and honestly? it's a little icon and you're gonna understand it in like two minutes. no cap. 🎀

✨ NAME ✨

ww_mutex_trylock — literally just tries to acquire the w/w mutex, with an optional acquire context. that's it, that's the whole vibe. 🦋

🌸 SYNOPSIS 🌸

int ww_mutex_trylock (struct ww_mutex *ww , struct ww_acquire_ctx
*ww_ctx );

💖 ARGUMENTS 💖

  • ww — the mutex you wanna lock. the main character of this whole operation. 👑
  • ww_ctx — optional w/w acquire context. optional!! like a cute accessory, you can bring it or not. ✨

🔥 DESCRIPTION 🔥

So the whole thing here is that this trylocks a mutex with the optional acquire context, and no deadlock detection is possible. none. zero. not a thing. 💀

It returns 1 if the mutex has been acquired successfully, and 0 otherwise. that's the whole return situation, super simple.

Unlike ww_mutex_lock, no deadlock handling is performed. however — and this is the little plot twist 🌀 — if a ctx is specified, -EALREADY handling may happen in calls to ww_mutex_trylock.

🚨 bestie listen to me: a mutex acquired with this function must be released with ww_mutex_unlock. no skipping that step, i'm serious. 🙈

🦋 SEE ALSO 🦋

Kernel file ./kernel/locking/mutex.c — plus the whole friend group:

🎀 sign-off 🎀

this little love letter lives in ./kernel/locking, and it's stamped October 2026 — so like, future vibes but make it kernel. slay, go forth, and remember to unlock. periodt. 💜🌈⭐

📦 where this page comes from