public inbox for [email protected]
 help / color / mirror / Atom feed
From: Pavel Begunkov <[email protected]>
To: yang lan <[email protected]>
Cc: [email protected], Jens Axboe <[email protected]>
Subject: Re: [PATCH 1/1] io_uring: more graceful request alloc OOM
Date: Mon, 22 May 2023 01:40:33 +0100	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAAehj2nmnN98ZYzcFMR0DsKXqEM7L8DH8SM4NusPqzoHu_VNPw@mail.gmail.com>

On 5/20/23 10:38, yang lan wrote:
> Hi,
> 
> Thanks for your response.
> 
> But I applied this patch to LTS kernel 5.10.180, it can still trigger this bug.
> 
> --- io_uring/io_uring.c.back    2023-05-20 17:11:25.870550438 +0800
> +++ io_uring/io_uring.c 2023-05-20 16:35:24.265846283 +0800
> @@ -1970,7 +1970,7 @@
> static struct io_kiocb *io_alloc_req(struct io_ring_ctx *ctx)
>          __must_hold(&ctx->uring_lock)
>   {
>          struct io_submit_state *state = &ctx->submit_state;
> -       gfp_t gfp = GFP_KERNEL | __GFP_NOWARN;
> +       gfp_t gfp = GFP_KERNEL | __GFP_NOWARN | __GFP_NORETRY;
>          int ret, i;
> 
>          BUILD_BUG_ON(ARRAY_SIZE(state->reqs) < IO_REQ_ALLOC_BATCH);
> 
> The io_uring.c.back is the original file.
> Do I apply this patch wrong?

The patch looks fine. I run a self-written test before
sending with 6.4, worked as expected. I need to run the syz
test, maybe it shifted to another spot, e.g. in provided
buffers.

-- 
Pavel Begunkov

  reply	other threads:[~2023-05-22  0:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-19 14:05 [PATCH 1/1] io_uring: more graceful request alloc OOM Pavel Begunkov
2023-05-20  1:57 ` Jens Axboe
2023-05-20  9:38 ` yang lan
2023-05-22  0:40   ` Pavel Begunkov [this message]
2023-05-22  7:55     ` yang lan
2023-05-23 12:08       ` Pavel Begunkov
2023-05-24  3:15         ` yang lan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox