ENUM SUBMIT_DISPOSITION(9)

🌸 NAME 🌸

okay so bestie, welcome to enum submit_disposition(9) from the Kernel API Manual 💖 — it's literally the enum that gives flags for routing an incoming operation. main character energy for async TX routing, no cap.

✨ SYNOPSIS ✨

here's the enum in its natural habitat, copy-exact:

enum submit_disposition {
    ASYNC_TX_SUBMITTED ,
    ASYNC_TX_CHANNEL_SWITCH ,
    ASYNC_TX_DIRECT_SUBMIT

};

🍓 Constants 🍓

• ASYNC_TX_SUBMITTED — we were able to append the new operation under the lock ✅ slay
• ASYNC_TX_CHANNEL_SWITCH — when the lock is dropped schedule a channel switch 🔄
• ASYNC_TX_DIRECT_SUBMIT — when the lock is dropped submit directly ⚡

💜 Description 💜

okay so here's the serious bit, and it's giving “do not mess this up” 😭 — while holding depend_tx->lock we must avoid submitting new operations. why? to prevent a circular locking dependency with drivers that already hold a channel lock when calling async_tx_run_dependencies. that's the whole safety vibe. don't be the one who submits new operations while holding that lock, bestie, fr fr.

🌈 SEE ALSO 🌈

Kernel file ./crypto/async_tx/async_tx.c, plus the whole squad: __async_tx_find_channel(9), async_tx_channel_switch(9), async_trigger_callback(9), async_tx_quiesce(9) 🫶

mwah 💋 — source/version says ./crypto/async_tx, dated October 2026, and this iconic page is enum submit_disposition(9) ✨👑