buffer_migrate_folio(9)

💅 buffer_migrate_folio(9) 🦋

okay so bestie, welcome to the Kernel API Manual entry for buffer_migrate_folio(9) — yes the (9) means kernel-internal, we're in the deep end and it's giving main character energy ✨

✨ NAME ✨

buffer_migrate_folio — the migration function for folios with buffers. periodt 💖

🌸 SYNOPSIS 🌸

int buffer_migrate_folio (struct address_space *mapping , struct folio
*dst , struct folio *src , enum migrate_mode mode );

🎀 ARGUMENTS 🎀

• mapping — the address space that contains src. that's the home base 🏠
• dst — the folio we're migrating to (the destination slay) 💫
• src — the folio we're migrating from (the one leaving the group chat) 😭
• mode — how to migrate the folio. the vibe check for the whole operation 🔥

💜 DESCRIPTION 💜

so here's the tea 🍓 — this function can only be used if the underlying filesystem guarantees that no other references to src exist. like, fr fr, that's not optional.

for example: attached buffer heads are accessed only under the folio lock. that's the guarantee in action, iykyk 🔒

⚠️ if your filesystem cannot provide this guarantee, buffer_migrate_folio_norefs may be more appropriate. please don't skip this, bestie, this is one of those "read the docs or cry later" situations 😭💀

🌈 RETURN 🌈

• 0 on success 🎉
• a negative errno on failure 🙈

👑 SEE ALSO 👑

• Kernel file ./mm/migrate.c: isolate_movable_ops_page(9)
• putback_movable_ops_page(9)
• migrate_movable_ops_page(9)
• migrate_folio(9)
• buffer_migrate_folio_norefs(9)

and that's a wrap, babe 🫶 this iconic lil page came from the source ./mm, dated October 2026, and it lives in the Kernel API Manual. go migrate some folios responsibly, mwah 💋🎀