kiocb_end_write(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… kiocb_end_write β€” a kernel API manual moment

okay so welcome to the kiocb_end_write(9) page, bestie, this is from the Kernel API Manual and it's short but she's important. Buckle up πŸŽ€


✨ NAME ✨

kiocb_end_write β€” drop write access to a superblock after async file io

like, you were holding the write vibe and now you're letting it go πŸ¦‹


✨ SYNOPSIS ✨

void kiocb_end_write (struct kiocb *iocb );

that's it. that's the whole function. no return value, she just does the thing and leaves πŸ’…


✨ ARGUMENTS ✨

  • iocb β€” the io context we submitted the write with (yes the original page spells it "sumbitted", we're keeping the energy, it's iconic 😭)

✨ DESCRIPTION ✨

okay so this one is lowkey a pair situation. kiocb_end_write should be matched with a call to kiocb_start_write β€” they're a matching set, a duo, main character energy together πŸ‘‘

you start the write, you end the write, the superblock's write access gets dropped, everybody goes home. no cap. ✨

no fr like genuinely β€” if you call one without the other, that's not the vibe. they go together or not at all πŸ’€

✨ SEE ALSO ✨

she's got a lot of friends, honestly obsessed with her social circle 🫢 the kernel file is ./include/linux/fs.h, and here's the whole crew:

like i said. huge friend group. iykyk 🌈


and that's the whole page, bestie!! πŸ’– this one came out of ./include/linux and it's dated October 2026 β€” so like, from the future, slay, we love a time traveler ⭐ mwah, go call kiocb_start_write first, bye πŸ§šβ€β™€οΈ

πŸ“¦ where this page comes from