dm_test_lin...ks_all_links(9)

📦 version 7.3.1, in nixpkgs unstable

okay so bestie, welcome to the Kernel API Manual ✨ (also yes, the header up top abbreviates it as dm_test_lin...ks_all_links(9) — that's just the terminal being dramatic and truncating, the actual full name is right there in the title, we're fine 💅)

🎀 NAME 🎀

dm_test_link_lock_locks_and_unlocks_all_links — literally the test that proves lock/unlock actually touches every single link, no skipping, no shortcuts 💖

✨ SYNOPSIS ✨

void dm_test_link_lock_locks_and_unlocks_all_links (struct kunit *test
);

🦋 ARGUMENTS 🦋

  • test — the KUnit test context 🧚 that's it, that's the whole argument, she's low maintenance

💜 DESCRIPTION 💜

so the vibe here is: link_lock needs to acquire the mutex of every entry from 0 to max_link when it's locking. every. single. one. no cap. 👑

and when it unlocks? it releases all of them. the whole squad, back to free, all of them. 🫶

then — and this is the part that actually matters, the main character moment — a subsequent lock/unlock cycle must succeed. that second cycle is the proof bestie, because if any mutex got left held the first time around, that follow-up cycle would just. not. work. 😭 so it passing means the mutexes were genuinely left released. iconic behaviour, honestly. ⭐

🌈 SEE ALSO 🌈

📁 Kernel file

  • ./drivers/gpu/drm/amd/display/amdgpu_dm/tests/amdgpu_dm_hdcp_test.c

🔥 the whole friend group (all of these, fr fr)

💀 friendly reminder bestie: this whole party lives under ./drivers/gpu/drm/amd/display/... so don't go looking for it in some random folder, iykyk 🙈

and that's the page! 🍓 source + version vibes come from ./drivers/gpu/drm/amd/display/..., dated October 2026 — she said see you in October, periodt. 💅🎀

📦 where this page comes from