jbd2_journal...reate_access(9)

💅 jbd2_journal_get_create_access — the NAME bit, bestie

Okay so this is a page from the Kernel API Manual (yep, the kernel manual, we're in the big leagues now 🎀) and it's all about jbd2_journal_get_create_access — which is literally just notifying intent to use a newly created bh. That's it. That's the whole vibe. ✨

---

✨ SYNOPSIS ✨

int jbd2_journal_get_create_access (handle_t *handle , struct
       buffer_head *bh );

Like, it returns an int, takes a handle_t *handle, and takes a struct buffer_head *bh. Slay. 🫶

---

🌸 ARGUMENTS 🌸

• handle — the transaction to new buffer to. 💖
• bh — the new buffer. 🦋

---

🧚 DESCRIPTION 🧚

Call this if you create a new bh.

Like… that's genuinely the whole instruction. No cap. If you made a new bh, this is the function you call — it's giving "notify intent to use newly created bh" energy, which is lowkey exactly what the NAME already told you. 👑

---

🔥 SEE ALSO 🔥

Kernel file ./fs/jbd2/transaction.c, plus the whole friend group of jbd2 functions:

• jbd2_journal_start(9)
• jbd2_journal_start_reserved(9)
• jbd2_journal_extend(9)
• jbd2__journal_restart(9)
• jbd2_journal_lock_updates(9)
• jbd2_journal_unlock_updates(9)
• jbd2_journal_get_write_access(9)
• jbd2_journal_get_undo_access(9)
• jbd2_journal_set_triggers(9)
• jbd2_journal_dirty_metadata(9)
• jbd2_journal_forget(9)
• jbd2_journal_stop(9)
• jbd2_journal_try_to_free_buffers(9)
• jbd2_journal_invalidate_folio(9)

---

And that's the whole page, bestie 💜 — sourced from ./fs/jbd2, dated October 2026, and yes the title up top really does get truncated to jbd2_journal...reate_access(9) like that. iconic honestly 😭 periodt 💅