public inbox for [email protected]
 help / color / mirror / Atom feed
From: Jens Axboe <[email protected]>
To: Pavel Begunkov <[email protected]>,
	Rafael Mendonca <[email protected]>
Cc: [email protected], [email protected]
Subject: Re: [PATCH] io-wq: Fix memory leak in worker creation
Date: Wed, 19 Oct 2022 19:26:30 -0700	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

On Wed, 19 Oct 2022 22:47:09 -0300, Rafael Mendonca wrote:
> If the CPU mask allocation for a node fails, then the memory allocated for
> the 'io_wqe' struct of the current node doesn't get freed on the error
> handling path, since it has not yet been added to the 'wqes' array.
> 
> This was spotted when fuzzing v6.1-rc1 with Syzkaller:
> BUG: memory leak
> unreferenced object 0xffff8880093d5000 (size 1024):
>   comm "syz-executor.2", pid 7701, jiffies 4295048595 (age 13.900s)
>   hex dump (first 32 bytes):
>     00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
>     00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
>   backtrace:
>     [<00000000cb463369>] __kmem_cache_alloc_node+0x18e/0x720
>     [<00000000147a3f9c>] kmalloc_node_trace+0x2a/0x130
>     [<000000004e107011>] io_wq_create+0x7b9/0xdc0
>     [<00000000c38b2018>] io_uring_alloc_task_context+0x31e/0x59d
>     [<00000000867399da>] __io_uring_add_tctx_node.cold+0x19/0x1ba
>     [<000000007e0e7a79>] io_uring_setup.cold+0x1b80/0x1dce
>     [<00000000b545e9f6>] __x64_sys_io_uring_setup+0x5d/0x80
>     [<000000008a8a7508>] do_syscall_64+0x5d/0x90
>     [<000000004ac08bec>] entry_SYSCALL_64_after_hwframe+0x63/0xcd
> 
> [...]

Applied, thanks!

[1/1] io-wq: Fix memory leak in worker creation
      commit: 839a0c962971a5a95515c1637aede8a4fbc6547f

Best regards,
-- 
Jens Axboe



      reply	other threads:[~2022-10-20  2:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-20  1:47 [PATCH] io-wq: Fix memory leak in worker creation Rafael Mendonca
2022-10-20  2:26 ` Jens Axboe [this message]

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 \
    --in-reply-to=166623279015.153364.8618304798678076215.b4-ty@kernel.dk \
    [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