It's ok for io_uring request allocation to fail, however there are reports that it starts killing tasks instead of just returning back to the userspace. Add __GFP_NORETRY, so it doesn't trigger OOM killer. Cc: stable@xxxxxxxxxxxxxxx Fixes: 2b188cc1bb857 ("Add io_uring IO interface") Reported-by: yang lan <lanyang0908@xxxxxxxxx> Signed-off-by: Pavel Begunkov <asml.silence@xxxxxxxxx> --- io_uring/io_uring.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/io_uring/io_uring.c b/io_uring/io_uring.c index dab09f568294..ad34a4320dab 100644 --- a/io_uring/io_uring.c +++ b/io_uring/io_uring.c @@ -1073,7 +1073,7 @@ static void io_flush_cached_locked_reqs(struct io_ring_ctx *ctx, __cold bool __io_alloc_req_refill(struct io_ring_ctx *ctx) __must_hold(&ctx->uring_lock) { - gfp_t gfp = GFP_KERNEL | __GFP_NOWARN; + gfp_t gfp = GFP_KERNEL | __GFP_NOWARN | __GFP_NORETRY; void *reqs[IO_REQ_ALLOC_BATCH]; int ret, i; -- 2.40.0