gfs2_trans_add_data(9)

✨ NAME ✨

gfs2_trans_add_data — bestie, this one adds a databuf to the transaction 💅

(it lives in the Kernel API Manual, section 9, iykyk 🫶)

🦋 SYNOPSIS 🦋

void gfs2_trans_add_data (struct gfs2_glock *gl , struct buffer_head *bh );

🎀 ARGUMENTS 🎀

• gl — the inode glock that's associated with the buffer, she's the main character of this pairing 💖
• bh — the buffer you're adding, no cap, this is the actual thing going in 🍓

🌸 DESCRIPTION 🌸

Okay so this one is used in journaled data mode. We need to journal the data block the exact same way we journal metadata in the functions above — same energy, different block ✨. The difference is that here we've got a tag, and that tag is two __be64's: one being the block number (as per meta data), and one being a flag that says whether the data block needs escaping or not 🦋. Which means — and this is the part where you go "wait, what" — we need a new log entry for each 251 or so data blocks 😭. Not an enormous overhead, lowkey fine, but it's twice as much as for normal metadata blocks. It's giving "small price to pay" 💀👑

⭐ SEE ALSO ⭐

• Kernel file ./fs/gfs2/trans.c — go read the source, bestie, she ate 🔥

Later, babes 🫶 — this cutie came out of ./fs/gfs2, in the October 2026 era, and yes it's gfs2_trans_add_data(9) from the Kernel API Manual, mwah 💜