bdev_yield_claim(9)

💅 bdev_yield_claim — a Kernel API Manual (section 9) moment 🎀

okay bestie, welcome to bdev_yield_claim from the Kernel API Manual, section 9 — she's lowkey a lil legend and we're gonna get into it ✨

🌸 NAME 🌸

bdev_yield_claim — the icon that gives up the holder claim on an open block device 🫶 like she's handing back the aux cord but NOT leaving the party

---

✨ SYNOPSIS ✨

void bdev_yield_claim (struct file *bdev_file );

that's it, that's the whole signature, no cap 💅

🦋 ARGUMENTS 🦋

• bdev_file — an open block device. literally just the open block device, that's her whole job 🎀

💖 DESCRIPTION 💖

so here's the vibe: bdev_yield_claim yields the holder and any write access for bdev_file without closing it — not me emphasizing that, she literally stays open — so the caller can still act on the device (for example, bdev_allow_freeze it) before the final bdev_fput. main character energy fr fr 👑

and then the lil plot twist that makes her so slay: bdev_fput yields too, so calling it afterwards is safe 💀✨ no double-yield drama, no chaos, we love a self-aware function.

ngl this is the "you can still touch the device, just not as the holder" arc and honestly? iconic 🌈

🔥 SEE ALSO 🔥

• Kernel file ./block/bdev.c
• bdev_validate_blocksize(9)
• bdev_freeze(9)
• bdev_thaw(9)
• bdev_deny_freeze(9)
• bdev_allow_freeze(9)
• bd_may_claim(9)
• bd_prepare_to_claim(9)
• bd_finish_claiming(9)
• bd_abort_claiming(9)
• bdev_open(9)
• bdev_fput(9)
• lookup_bdev(9)
• bdev_mark_dead(9)

the whole claim-and-freeze friend group, all tagged and accounted for 💜 go read them, iykyk 🧚

---

and that's the page!! 🌸 this lil gem lives in ./block, dated October 2026, and yes she signs off as bdev_yield_claim(9) because she knows exactly who she is 💅💖 bye bestie, go yield something 🎀