folio_trylock(9)

📦 version 7.3.1, in nixpkgs unstable

🌸 folio_trylock(9) 🌸

okay so bestie, welcome to the Kernel API Manual 💖 this is the page for folio_trylock(9), and it's giving “just try the lock, no big dramatic wait” energy. ✨

🎀 NAME 🎀

folio_trylock — Attempt to lock a folio.

🦋 SYNOPSIS 🦋

bool folio_trylock (struct folio *folio );

💖 ARGUMENTS 💖

  • folio — The folio to attempt to lock. that's the whole arg, periodt 🫶

✨ DESCRIPTION ✨

Sometimes it is undesirable to wait for a folio to be unlocked (eg when the locks are being taken in the wrong order, or if making progress through a batch of folios is more important than processing them in order). Usually folio_lock is the correct function to call.

ngl, that “Usually folio_lock is the correct function to call” line is the main character warning here — don't just grab folio_trylock because the name sounds cute. 💅

🌈 CONTEXT 🌈

Any context. literally any. no cap. 🦋

👑 RETURN 👑

Whether the lock was successfully acquired. yes, that's the whole return vibe — a lil success check. 🎀

🔥 SEE ALSO 🔥

Kernel file ./include/linux/pagemap.h — yes, that exact one — plus this whole squad of besties:

okay that's the whole page 💖 the source/version bit is ./include/linux, and the date is October 2026 — go forth and try your locks, bestie, slay 💅✨

📦 where this page comes from