blkcg_deactivate_policy(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… blkcg_deactivate_policy β€” the manual page (Kernel API Manual, bestie)

okay so first things first: this is blkcg_deactivate_policy(9) from the Kernel API Manual, and we're about to make deactivating a blkcg policy on a gendisk make Senseβ„’. buckle up πŸŽ€


✨ NAME ✨

blkcg_deactivate_policy β€” deactivate a blkcg policy on a gendisk

like literally, that's the whole vibe: policy goes off, disk says bye πŸ‘‹


πŸ¦‹ SYNOPSIS πŸ¦‹

void blkcg_deactivate_policy (struct gendisk *disk , const struct
       blkcg_policy *pol );

so you're handing it a disk and a pol, and it returns void β€” meaning it gives you nothing back, no return value, no lil gift, just vibes and side effects πŸ’€ don't @ me


🌸 ARGUMENTS 🌸

  • disk β€” gendisk of interest 🫢 the disk you're looking at, the main character of this operation
  • pol β€” blkcg policy to deactivate ✨ the policy that's getting un-invited from the party

πŸ’– DESCRIPTION πŸ’–

Deactivate pol on disk. that's it, that's the whole thing, no cap πŸ’…

and the important part β€” the part where you do not freestyle, bestie β€” it follows the same synchronization rules as blkcg_activate_policy. so whatever locking and ordering energy the activate side has going on, this one is matching it exactly. same rules, different direction. iykyk πŸ”₯

ngl this is the "don't get creative with concurrency" part of the page. the manual says "same synchronization rules as blkcg_activate_policy" and it means it fr fr πŸ™ˆ

πŸ‘‘ SEE ALSO πŸ‘‘

Kernel file ./block/blk-cgroup.c β€” and then the whole friend group, all of these icons:

bestie do NOT skip blkcg_activate_policy(9) in that list β€” it's literally the one the DESCRIPTION told you to match synchronization with 🧚


🌈 sign-off 🌈

and that's the page!! it lives under ./block, this is the October 2026 version of the Kernel API Manual, and we are so obsessed πŸ’œπŸ“ go forth and deactivate responsibly, mwah 🫢✨

πŸ“¦ where this page comes from