drm_dp_mst_get_mstb_malloc(9)

📦 version 7.3.1, in nixpkgs unstable

💅 drm_dp_mst_get_mstb_malloc — the girls are reading the kernel API manual (section 9, bestie)

Okay so this is a page from the Kernel API Manual, and it's about drm_dp_mst_get_mstb_malloc. Yes it's a whole mouthful, no we're not changing it, and yes it's lowkey iconic. Let's get into it ✨

🎀 NAME 🎀

drm_dp_mst_get_mstb_malloc — increment the malloc refcount of a branch device. That's it, that's the whole job. She's a one-task queen 👑

✨ SYNOPSIS ✨

void drm_dp_mst_get_mstb_malloc (struct drm_dp_mst_branch *mstb );

Look at her. Barely any words. Returns nothing. Just vibes and a refcount bump 🫶

🌸 ARGUMENTS 🌸

  • mstb — the struct drm_dp_mst_branch you want to increment the malloc refcount of. Like, that exact one. Not a lookalike. Not a cousin. That one 💖

🦋 DESCRIPTION 🦋

So what she actually does: she increments drm_dp_mst_branch.malloc_kref. That's the move. That's the whole move.

And like — important — when drm_dp_mst_branch.malloc_kref reaches 0, the memory allocation for mstb will be released and mstb may no longer be used. So bestie, do not keep touching it after that. It's giving "the light is off, nobody's home" 💀

See also: drm_dp_mst_put_mstb_malloc — that's her counterpart, the one who gives the refcount back. They're a matching set, honestly adorable.

🔥 SEE ALSO 🔥

The friend group is honestly massive, but we love a full roster. No gatekeeping here:

Like I said. Huge friend group. Every single one of them tagged 💜

✨ and that's the page, bestie ✨

This cutie lives at ./drivers/gpu/drm/display in the kernel tree, dated October 2026, and she answers to drm_dp_mst_get_mstb_malloc(9) — write that down, there will be a quiz 🎀💖

📦 where this page comes from