locked_inode...nd_lock_list(9)

📦 version 7.3.1, in nixpkgs unstable

💅 locked_inode_to_wb_and_lock_list — Kernel API Manual 💅

okay so you're reading the Kernel API Manual page for locked_inode_to_wb_and_lock_list(9), and honestly? it's a whole vibe. let's get into it bestie 🫶

✨ NAME ✨

locked_inode_to_wb_and_lock_list — figure out which wb a locked inode belongs to, and lock that thing. that's it, that's the job 💁‍♀️

🌸 SYNOPSIS 🌸

struct bdi_writeback * locked_inode_to_wb_and_lock_list (struct inode *inode );

like, it hands you back a struct bdi_writeback * and takes one struct inode *inode. simple. iconic. no cap. ✨

🎀 ARGUMENTS 🎀

  • inode — the inode you're curious about. heads up: you gotta be holding i_lock already, no exceptions, that's the entry fee 💅

🦋 DESCRIPTION 🦋

so it returns the inode's wb with its list_lock held. lockception, we love to see it 😭

the rules, because there are always rules:

  • inode->i_lock must be held on entry 🔒
  • it gets released on return (so don't go touching it after, bestie, it's gone)
  • the wb you get back is guaranteed to stay this inode's associated wb until its list_lock is released — that's the promise, and she keeps her promises 👑

it's giving "trust me bro" but like, in a legally binding kernel way 💀

🌈 SEE ALSO 🌈

all the siblings and cousins, in the kernel file ./fs/fs-writeback.c:

okay that's the whole page!! sourced from ./fs, dated October 2026 — go forth and hold your locks correctly, bestie, i believe in you 🧚💖 mwah 💋

📦 where this page comes from