memalloc_pin_save(9)

💖 NAME 💖

okay so this is memalloc_pin_save(9) from the Kernel API Manual, and it Marks implicit ~__GFP_MOVABLE scope. Lowkey a tiny scope marker with main character energy. 💅

🌸 SYNOPSIS 🌸

unsigned int memalloc_pin_save (void );

🦋 ARGUMENTS 🦋

• void — no arguments, bestie. Nothing to pass, no vibe check needed.

✨ DESCRIPTION ✨

This function marks the beginning of the ~__GFP_MOVABLE allocation scope. All further allocations will implicitly remove the __GFP_MOVABLE flag — yes, automatically, no cap. That constrains those allocations to zones that allow long term pinning, i.e. not ZONE_MOVABLE zones. It's giving “please stay pinnable, bestie.” 🫶

🎀 RETURN 🎀

The saved flags to be passed to memalloc_pin_restore. Hold onto them, fr fr — they're literally the thing you hand back later. 😭

🌈 SEE ALSO 🌈

Kernel file ./include/linux/sched/mm.h — that's the spot. Then the whole little friend group:

• mmgrab(9)
• mmget(9)
• might_alloc(9)
• memalloc_flags_save(9)
• memalloc_noio_save(9)
• memalloc_noio_restore(9)
• memalloc_nofs_save(9)
• memalloc_nofs_restore(9)
• memalloc_noreclaim_save(9)
• memalloc_noreclaim_restore(9)
• memalloc_pin_restore(9)
• set_active_memcg(9)

mwah 💋 — source/version + date check: ./include/linux/sched, October 2026, for memalloc_pin_save(9). Bye bestie! 💜