Feature request: OOM handling

I am currently writing a filesystem application that runs on end-user devices and I would like to take advantage of io_uring. This often means that memory usage is very unpredictable and OOM conditions may happen often. In this case, I do not want to leave my filesystem in an inconsistent state because some computation (e.g. IO submissions, task spawning, and so on) panics.

Is it possible to have the compio library return errors when an out-of-memory condition happens?

Start by reviewing the compio io_uring paths and the APIs involved in IO submissions and task spawning. Determine where out-of-memory conditions can currently panic and whether those entry points can return errors without leaving filesystem operations inconsistent. Done means the supported behavior and scope are defined, with tests covering OOM handling.

Written by the indexing model from the issue text.