libnvme_mi_submit_exit(9)

📦 version 3.2, in arch rolling

✨ libnvme_mi_submit_exit ✨

okay so this is a page from the libnvme API manual, and we're about to get into a very specific little hook function. stay with me bestie, it's actually iconic 💅

🌸 NAME 🌸

libnvme_mi_submit_exit — a weak hook that gets called after an MI message completes. literally the after-party of MI messages 🎀

🦋 SYNOPSIS 🦋

void libnvme_mi_submit_exit (__u8 type , const struct nvme_mi_msg_hdr
*hdr , size_t hdr_len , const void *data , size_t data_len , void
*user_data );

💖 ARGUMENTS 💖

  • type — the MCTP message type. just a lil __u8 telling you what kind of message we're dealing with 🫶
  • hdr — a pointer to the MI response message header. const struct nvme_mi_msg_hdr *, no cap ✨
  • hdr_len — the length of that response message header, in bytes. size_t behavior fr fr
  • data — a pointer to the response payload data. const void *, very mysterious, very main character 🌈
  • user_data — the value that was returned by the matching libnvme_mi_submit_entry call. yep, it's giving matched set 👑

💜 DESCRIPTION 💜

so here's the vibe: libnvme_mi_submit_exit is a weak symbol, which means an application can totally override it and use it to intercept completed MI transactions. like, it's a hook you can claim as your own 🔥

it gets called with that opaque pointer returned by the corresponding libnvme_mi_submit_entry call. the two of them are literally a matched pair — entry and exit, iykyk 😭💖

no extra behavior beyond that, bestie — it's a weak symbol and the docs keep it exactly that simple. don't go inventing side effects 🩷

and that's the whole page, fr fr. this gem is from the libnvme API manual, dated October 2026 — and honestly? she ate. periodt. 💅✨🎀🦋💖

📦 where this page comes from