blkg_get(9)

💅 blkg_get(9) — the Kernel API Manual glow-up

Okay so bestie, welcome to blkg_get, a page straight outta the Kernel API Manual. It's short, it's sweet, and it's lowkey the reference-counting baddie you didn't know you needed. Let's get into it ✨

---

🎀 NAME 🎀

blkg_get — get a blkg reference. That's it. That's the whole vibe. Grab a ref, be the main character 🫶

---

⭐ SYNOPSIS ⭐

void blkg_get (struct blkcg_gq *blkg );

Literally one line, no cap. Note the return type is void — she gives you nothing back except the ref itself, and honestly? Iconic 💅

---

🌸 ARGUMENTS 🌸

• blkg — the blkg you wanna get a reference on. That's the whole parameter, bestie. Hand it over and let her cook 🍓

---

💖 DESCRIPTION 💖

Okay so here's the situation: the caller should be holding an existing reference.

That's the whole description. She's concise, she's a little mysterious, she knows her worth 👑 The takeaway is you gotta already have a reference in hand before you go calling this — that's the rule, fr fr. Don't come in empty-handed 🙈

---

🦋 SEE ALSO 🦋

Kernel file ./block/blk-cgroup.h — plus the whole friend group, all invited to the function party:

• bio_issue_as_root_blkg(9)
• blkg_lookup(9)
• blkg_to_pd(9)
• pd_to_blkg(9)
• blkg_tryget(9)
• blkg_put(9)
• blkg_for_each_descendant_pre(9)
• blkg_for_each_descendant_post(9)
• blkcg_set_delay(9)
• blkcg_clear_delay(9)
• blk_cgroup_mergeable(9)

Every single one, present and accounted for. Go read them, they're literally right there 🧚

---

Ngl the whole page is basically "you should already hold a reference" — so like, do that first? Please? For me? 🥺

---

And that's a wrap, bestie! This adorable little number lives in ./block, and she was blessed upon the world in October 2026, answering to the name blkg_get(9). Slay, stay ref-counted, and remember: hold your reference before you get another one 💜✨🎀