<axboe>
Ne02ptzero: do you have a reproducer? regardless of whether or not it's an app or kernel issue, reproducer helps highlight it. and more often than not, it highlights what the app ends up doing wrong. it's like explaining the code, rubber ducking :)
<axboe>
Ne02ptzero: I'm assuming you are replenishing the buffers back into the ring when they have been used?
<axboe>
Ne02ptzero: and is IORING_CQE_F_BUFFER set? if the ring is empty, you should be getting -ENOBUFS in cqe->res for that request
<axboe>
in any case, a reproducer will undoubtedly help
axboe has quit [Remote host closed the connection]
axboe has joined #io_uring
<Ne02ptzero>
Found the issue! If it can help someone: Turns out I was re-using the buffer given me by the read operations for the response-write operations. (recv() -> buffer_id -> write() with the same buffer)
<Ne02ptzero>
Giving back the buffer after the read and using a different buffer bool for the write operations seems to have fixed it. Strange behaviour though.
<Ne02ptzero>
axboe: Thanks for your help and your time! I mainly used the io-uring-udp.c in examples/ as a debug / compare tool.
<axboe>
Ne02ptzero: excellent! thanks for reporting back