ep_loop_check(9)

NAME 💅

okay bestie, welcome to the ep_loop_check(9) page from the Kernel API Manual. this function performs a check to verify that adding an epoll file (@to) into another epoll file (represented by @ep) does not create closed loops or too deep chains. it’s giving “safety inspector but make it kernel-core,” no cap. 🌀✨

SYNOPSIS 🎀

       int ep_loop_check (struct ep_ctl_ctx *ctx , struct eventpoll *ep ,
       struct eventpoll *to );

ARGUMENTS 🦋

• ctx — Per-CTL_ADD scratch context. the little scratchpad this check gets to use. 📝
• ep — pointer to the epoll we are inserting into. that’s the epoll on the receiving end of this operation. 👑
• to — pointer to the epoll to be inserted. that’s the guest getting added in. 🫶

RETURN 🌸

returns zero if adding the epoll to inside the epoll from does not violate the constraints, or -1 otherwise. so: zero = constraints are happy; -1 = nope, not today. 💀✨

SEE ALSO 🔥

• Kernel file ./fs/eventpoll.c
• busy_loop_ep_timeout(9)
• reverse_path_check(9)
• ep_poll(9)
• ep_loop_check_proc(9)

mwah 💋 this page is from source/version ./fs, dated October 2026, and yes the manual page is ep_loop_check(9). go forth and loop-check responsibly, bestie — periodt. 🧚‍♀️💖