kunit_release_action(9)

🎀 NAME 🎀

bestie, this is kunit_release_action from the Kernel API Manual — Run a matching action call immediately. 💅

Okay so this is the function that says “actually, let’s do that deferred thing right now” instead of waiting for the test to wrap. ✨

✨ SYNOPSIS ✨

void kunit_release_action (struct kunit *test , kunit_action_t *action ,
void *ctx );

💅 ARGUMENTS 💅

• test — Test case the action is associated with. 🫶
• action — The deferred function to trigger. 🔥
• ctx — The context passed to the deferred function to trigger. 🎀

🦋 DESCRIPTION 🦋

Execute a function deferred via kunit_add_action) immediately, rather than when the test ends. Yes bestie, trigger it now — no waiting for the end-of-test cleanup era. 🌸

If the function/context pair was deferred multiple times, it will only be executed once here. The most recent deferral will no longer execute when the test ends. That’s the whole vibe: one immediate run, and the latest queued repeat gets cancelled from the end-of-test lineup. 💀

This line:

kunit_release_action(test, func, ctx);

is equivalent to:

func(ctx);
kunit_remove_action(test, func, ctx);

So it’s literally “call the func, then remove the matching action” — iconic combo, no cap. 👑

See also: devm_release_action for the devres equivalent. 🌈

🌈 SEE ALSO 🌈

The kernel file ./include/kunit/resource.h is the main character here, and these are all the linked faves:

• struct kunit_resource(9)
• kunit_get_resource(9)
• kunit_put_resource(9)
• __kunit_add_resource(9)
• kunit_add_resource(9)
• kunit_add_named_resource(9)
• kunit_alloc_and_get_resource(9)
• kunit_alloc_resource(9)
• kunit_resource_name_match(9)
• kunit_find_resource(9)
• kunit_find_named_resource(9)
• kunit_destroy_resource(9)
• kunit_remove_resource(9)
• KUNIT_DEFINE_ACTION_WRAPPER(9)
• kunit_add_action(9)
• kunit_add_action_or_reset(9)
• kunit_remove_action(9)

xoxo bestie 💖 — this one comes from ./include/kunit and is dated October 2026 ✨