trace_block_dirty_buffer(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸŽ€ NAME πŸŽ€

okay so bestie, welcome to the manual page for trace_block_dirty_buffer(9) β€” it's from the Kernel API Manual, and it's here to explain one tiny thing: how a buffer gets marked dirty. πŸ’…

  • trace_block_dirty_buffer β€” mark a buffer dirty. That's the whole name, no cap. 🫢

✨ SYNOPSIS ✨

void trace_block_dirty_buffer (struct buffer_head *bh );

Yes, that's the exact signature: it returns void (nothing comes back, bestie), and it takes a struct buffer_head * named bh. ✨

πŸ’– ARGUMENTS πŸ’–

  • bh β€” the buffer_head being dirtied πŸ’…. That's the one argument, and she's doing all the work here.

🌸 DESCRIPTION 🌸

Called from mark_buffer_dirty. That's it. That's the whole description, and honestly she ate. πŸ”₯

πŸ¦‹ SEE ALSO πŸ¦‹

Kernel file: ./include/trace/events/block.h β€” that's the file, iykyk. ✨


mwah πŸ’‹ β€” source/version: ./include/trace/events; date: October 2026; page: trace_block_dirty_buffer(9). Bye bestie, go keep those buffers in check! πŸ«ΆπŸ’–

πŸ“¦ where this page comes from