drm_warn_on_...t_all_locked(9)

💅 drm_warn_on_...t_all_locked(9) — from the Kernel API Manual, bestie ✨

Okay so real talk, the page title got truncated by the man page formatting (it's giving "my name is too long for the header"), but the actual thing we're looking at is drm_warn_on_modeset_not_all_locked. It lives in the Kernel API Manual section 9, and we're gonna get into it 🎀

---

✨ NAME ✨

drm_warn_on_modeset_not_all_locked — literally just checks that all modeset locks are locked. That's the whole vibe check 🔥

---

🦋 SYNOPSIS 🦋

void drm_warn_on_modeset_not_all_locked (struct drm_device *dev );

Note that trailing space before the closing paren in *dev ); — yes it's in the original, no I'm not fixing it, we don't do that here 💅

---

🌸 ARGUMENTS 🌸

• dev — the device 👑 (that's it, that's the argument, she's a simple girl)

---

💖 DESCRIPTION 💖

Useful as a debug assert. No cap, that's genuinely the entire description — it's a little one-liner of a function that just raises a warning if your modeset locks aren't all locked when they should be 🫶 Think of it as the function that goes "bestie… you forgot something 👀" but in dmesg.

It's a debug assert, so it's about catching things during development, not a runtime thing you build your whole app around 💀

---

👑 SEE ALSO 👑

Kernel file: ./drivers/gpu/drm/drm_modeset_lock.c — go read the source, it ate 💅

• kms locking(9)
• drm_modeset_lock_all(9)
• drm_modeset_unlock_all(9)
• drm_modeset_acquire_init(9)
• drm_modeset_acquire_fini(9)
• drm_modeset_drop_locks(9)
• drm_modeset_backoff(9)
• drm_modeset_lock_init(9)
• drm_modeset_lock(9)
• drm_modeset_lock_single_interruptible(9)
• drm_modeset_unlock(9)
• drm_modeset_lock_all_ctx(9)

Like, that's a whole friend group of modeset locking functions and they all reference each other. iykyk 🌈

---

That's the whole page, baddie — short and iconic. Signing off from ./drivers/gpu/drm, dated October 2026, with love from your girl drm_warn_on_...t_all_locked(9) 🧚‍♀️💜⭐