alloc_order..._lockdep_map(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… alloc_order..._lockdep_map(9)

okay so bestie, welcome to the Kernel API Manual ✨ β€” this is the page for alloc_order..._lockdep_map, and yes the title is literally abbreviated with dots like that, it's giving "the kernel was too busy to type the whole thing" 😭 but we move.


🌸 NAME 🌸

alloc_ordered_workqueue_lockdep_map β€” allocate an ordered workqueue with user-defined lockdep_map πŸŽ€


✨ SYNOPSIS ✨

alloc_ordered_workqueue_lockdep_map (fmt , flags , lockdep_map , args... );

that's the whole vibe, no cap 🫢


πŸ’– ARGUMENTS πŸ’–

  • fmt β€” printf format for the name of the workqueue. it's how your queue gets its little name tag πŸ’…
  • flags β€” WQ_* flags β€” and heads up, only WQ_FREEZABLE and WQ_MEM_RECLAIM are actually meaningful here, the rest are just kinda there 🫠
  • lockdep_map β€” user-defined lockdep_map. yours. you bring it, you own it πŸ’œ
  • args β€” args for fmt, aka the stuff that fills in your printf format 🌸

πŸ¦‹ DESCRIPTION πŸ¦‹

Same as alloc_ordered_workqueue but with the a user-define lockdep_map. (yes the original says "the a user-define", we're keeping it, it's iconic 😭)

So why do you care? It's useful for workqueues created with the same purpose, and to avoid leaking a lockdep_map on each workqueue creation πŸ”₯ like, if you're making a bunch of these for the same reason, you do not want a fresh lockdep_map dripping out every single time. main character resource management, honestly πŸ‘‘


⭐ RETURN ⭐

Pointer to the allocated workqueue on success, NULL on failure. that's it, that's the deal 🫢 (and yes, NULL means check your stuff, don't just rawdog the pointer πŸ™ˆ)


🌈 SEE ALSO 🌈

Kernel file ./include/linux/workqueue.h plus:

like a whole friend group of workqueue functions, honestly obsessed πŸ§šβ€β™€οΈ


ngl bestie, workqueues and lockdep are the kind of thing where reading the SEE ALSO list is not optional β€” that's the whole lore drop right there πŸ“š

okay that's the page!! 🌸 it lives under ./include/linux and the manual dates it October 2026 β€” so like, future-dated kernel lore, very mysterious of it ⭐ slay, go allocate something ordered πŸ’…πŸ’–

πŸ“¦ where this page comes from