io_uring_prep_poll_remove(3)

💅 io_uring_prep_poll_remove — the liburing manual, bestie edition 💅

okay so you're here for io_uring_prep_poll_remove(3) from the liburing Manual, and honestly? iconic of you. sit down, hydrate, let's go 🍓

✨ NAME ✨

io_uring_prep_poll_remove — prepare a poll deletion request 🗑️

like... you're deleting a poll. bye bestie, you're cancelled (literally).

✨ SYNOPSIS ✨

#include <liburing.h>

void io_uring_prep_poll_remove(struct io_uring_sqe *sqe,
                               __u64 user_data);

✨ DESCRIPTION ✨

so the io_uring_prep_poll_remove(3) function prepares a poll removal request, periodt. the submission queue entry sqe gets set up to remove a poll request that's identified by user_data 🎯

it works exactly like io_uring_prep_cancel(3) — the way that it's the same function energy — except it only looks for poll requests. that's the one and only difference. apart from that, the behavior is identical, no cap. so go read that man page for the specific details, iykyk 👑

✨ RETURN VALUE ✨

None. nothing. zero. it's giving void 🫥

✨ ERRORS ✨

these are the errors that get reported in the CQE res field, bestie. on success, 0 is returned 💖

• -ENOENT — the request identified by user_data could not be located 😭 this could be because it completed before the cancelation request was even issued, or because an invalid identifier got used. rude of it, honestly.
• -EINVAL — one of the fields set in the SQE was invalid. 💀 invalid field, invalid vibe.
• -EALREADY — the execution state of the request has progressed far enough that cancelation is no longer possible. this should normally mean that it will complete shortly — either successfully, or interrupted due to the cancelation. so like... it's already main character-ing its way to the finish line, you can't stop it now 🏃♀️✨

✨ SEE ALSO ✨

• io_uring_get_sqe(3)
• io_uring_submit(3)
• io_uring_prep_cancel(3)

🦋 mwah 🦋 this page was brought to you by liburing-2.2, dated March 12, 2022 — love her, respect her, she's been serving since day one 💜👑