trace_block_touch_buffer(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… trace_block_touch_buffer(9) πŸ’…

okay bestie, welcome to the Kernel API Manual ✨ β€” today's main character is trace_block_touch_buffer, and honestly? she's short, she's sweet, she does one (1) thing and she does it flawlessly. no cap. πŸŽ€


🌸 NAME 🌸

trace_block_touch_buffer β€” mark a buffer accessed πŸ‘€βœ¨

like literally that's her whole job and she's obsessed with it.


πŸ¦‹ SYNOPSIS πŸ¦‹

void trace_block_touch_buffer (struct buffer_head *bh );

that's it. that's the whole function signature. a void returning icon. πŸ‘‘


πŸŽ€ ARGUMENTS πŸŽ€

  • bh β€” the buffer_head being touched πŸ’… (yes that's the actual name of the type, we don't make the rules, we just vibe with them)

✨ DESCRIPTION ✨

so basically: this is called from touch_buffer. that's the tea. 🍡

fr fr, that's the entire description β€” she's a tracepoint, she's not here to overexplain herself, she's here to mark a buffer accessed and leave. lowkey iconic behaviour if you ask me 🫢


🌈 SEE ALSO 🌈

the whole friend group πŸ₯° β€” go say hi to her sisters:

and if you wanna read the source (and you should, bestie, iykyk), hit up the kernel file ./include/trace/events/block.h πŸ’–


🧚 quick vibe check: this page is literally four lines of substance, so don't go looking for hidden lore. what's here is what's here. periodt.

and that's the whole page, bestie!! πŸ“ this lil gem comes to you from ./include/trace/events, dated October 2026 β€” mwah, go touch some buffers (respectfully) πŸ’œπŸ”₯

πŸ“¦ where this page comes from