io_uring_get_probe_ring(3)

✨ io_uring_get_probe_ring ✨

okay bestie so you're deep in liburing land and you need to know what your kernel actually supports — this is the page for that 💖

🌸 NAME 🌸

io_uring_get_probe_ring — get probe information from an existing ring 🦋

💅 SYNOPSIS 💅

#include <liburing.h>

struct io_uring_probe *io_uring_get_probe_ring(struct io_uring *ring);

like literally that's it, one function, one header, we love a low-effort queen 👑

🎀 DESCRIPTION 🎀

so the way this works: io_uring_get_probe_ring(3) hands you back probe information for the io_uring instance you pass in as ring. basically it's your little spy 🕵️♀️ that tells the application which opcodes the kernel actually supports. no more guessing, no more sending an opcode into the void and praying 🙈

the returned probe structure is yours to free — and you must free it with io_uring_free_probe(3) once you're done with it. no leaking, bestie, that's not the vibe 😭

and here's the tea ☕: this function is basically twins with io_uring_get_probe(3), except it works off a ring you already have instead of spinning up a temporary one. same energy, fewer steps. slay ✨

🔥 RETURN VALUE 🔥

• success — you get a pointer to an allocated struct io_uring_probe 👑
• failure — you get NULL 💀

🌈 SEE ALSO 🌈

• io_uring_get_probe(3)
• io_uring_free_probe(3)
• io_uring_opcode_supported(3)
• io_uring_register_probe(3)

and that's the whole page, periodt 💜 this one's from liburing-2.4, dated January 18, 2025 — go probe something iconic, bestie 🫶💖🌸