io_uring_register_probe(3)

✨ io_uring_register_probe — register probe with io_uring ✨

okay bestie, welcome to the liburing manual, this one's io_uring_register_probe(3) and it's lowkey a little detective mission for your kernel 💅

🌸 SYNOPSIS 🌸

#include <liburing.h>

int io_uring_register_probe(struct io_uring *ring,
                            struct io_uring_probe *p,
                            unsigned nr);

🦋 DESCRIPTION 🦋

So here's the vibe: io_uring_register_probe(3) goes and asks the kernel which io_uring opcodes it actually supports, and then it fills in the probe structure p with the answer. no cap, it's literally just "hey kernel, whatcha got?" 💖

• the ring argument is the io_uring instance you're interrogating — that's the one getting queried, bestie 🔍
• the nr argument is the maximum number of opcodes to query, so it's your little cap on how much you're asking for

The probe structure holds all the tea about which opcodes the kernel supports. Once you've called this function, your app can use io_uring_opcode_supported(3) to check whether one specific opcode is supported. iykyk 🎀

okay but real talk — most applications should use io_uring_get_probe(3) or io_uring_get_probe_ring(3) instead, because those ones allocate and fill in the probe structure automatically for you. this function is the manual, do-it-yourself version. no shade, just saying 💅

👑 RETURN VALUE 👑

• returns 0 on success — slay ✨
• on error, it returns a negative errno value 😭

🌈 SEE ALSO 🌈

• io_uring_get_probe(3)
• io_uring_get_probe_ring(3)
• io_uring_opcode_supported(3)
• io_uring_free_probe(3)
• io_uring_register(2)

that's the whole page, bestie, you ate 🫶 this was liburing-2.4, dated January 18, 2025, from the liburing manual — mwah, go probe something iconic 💖✨🎀