STRUCT ACTION(9)

💖 NAME 💖

Okay bestie, welcome to the struct action(9) page from the Kernel API Manual — and the whole vibe is: struct action is an action to be performed in each of a set of zones. Periodt. ✨

✨ SYNOPSIS ✨

struct action {
    bool in_use;
    const struct admin_state_code *operation;
    vdo_action_preamble_fn preamble;
    vdo_zone_action_fn zone_action;
    vdo_action_conclusion_fn conclusion;
    struct vdo_completion *parent;
    void *context;
    struct action *next;
 };

🫶 Members 🫶

• in_use — whether this structure is in use. literally the “are we doing this or not” flag, no cap.
• operation — the admin operation associated with this action. it’s giving “which admin op are we tied to?” energy.
• preamble — the method to run on the initiator thread before the action is applied to each zone. pre-game ritual, but make it kernel thread.
• zone_action — the action to be performed in each zone. the main character doing the actual work in every zone, iykyk.
• conclusion — the method to run on the initiator thread after the action is applied to each zone.</the> cleanup era on the initiator thread, obsessively after the zone action is done.
• parent — the object to notify when the action is complete. ping bestie when it’s finished, basically.
• context — the action specific context. the lil action-specific bag of stuff it needs.
• next — the action to perform after this one. the queue said “and then?” and this field said “say less.” 💅

🔥 SEE ALSO 🔥

Kernel file ./drivers/md/dm-vdo/action-manager.c struct action_manager(9), vdo_make_action_manager(9), vdo_schedule_default_action(9), vdo_schedule_action(9), vdo_schedule_operation(9), vdo_schedule_operation_with_context(9)

Mwah 💋 — source/version: ./drivers/md/dm-vdo, dated October 2026. struct action(9) out! 🦋🎀💜