From: Jens Axboe <[email protected]>
To: Yang Yingliang <[email protected]>,
[email protected], [email protected]
Subject: Re: [PATCH] io_uring: fix memleak in io_sqe_files_register()
Date: Fri, 10 Jul 2020 07:51:18 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 7/10/20 8:14 AM, Yang Yingliang wrote:
> I got a memleak report when doing some fuzz test:
>
> BUG: memory leak
> unreferenced object 0x607eeac06e78 (size 8):
> comm "test", pid 295, jiffies 4294735835 (age 31.745s)
> hex dump (first 8 bytes):
> 00 00 00 00 00 00 00 00 ........
> backtrace:
> [<00000000932632e6>] percpu_ref_init+0x2a/0x1b0
> [<0000000092ddb796>] __io_uring_register+0x111d/0x22a0
> [<00000000eadd6c77>] __x64_sys_io_uring_register+0x17b/0x480
> [<00000000591b89a6>] do_syscall_64+0x56/0xa0
> [<00000000864a281d>] entry_SYSCALL_64_after_hwframe+0x44/0xa9
>
>
> Call percpu_ref_exit() on error path to avoid
> refcount memleak.
Applied, thanks.
--
Jens Axboe
prev parent reply other threads:[~2020-07-10 13:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-10 14:14 [PATCH] io_uring: fix memleak in io_sqe_files_register() Yang Yingliang
2020-07-10 13:51 ` 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 \
[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