From: Pavel Begunkov <[email protected]>
To: Lukas Bulwahn <[email protected]>, Jens Axboe <[email protected]>
Cc: Linux Kernel Mailing List <[email protected]>,
[email protected]
Subject: Re: Observation of a memory leak with commit e98e49b2bbf7 ("io_uring: extend task put optimisations")
Date: Sun, 9 Jan 2022 00:57:15 +0000 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 1/7/22 16:22, Pavel Begunkov wrote:
> On 1/7/22 15:00, Lukas Bulwahn wrote:
>> Dear Pavel, dear Jens,
>>
>> In our syzkaller instance running on linux-next,
>> https://elisa-builder-00.iol.unh.edu/syzkaller-next/, we have been
>> observing a memory leak in copy_process for quite some time.
>>
>> It is reproducible on v5.15-rc1, v5.15, v5.16-rc8 and next-20220106:
>>
>> https://elisa-builder-00.iol.unh.edu/syzkaller-next/crash?id=1169da08a3e72457301987b70bcce62f0f49bdbb
>>
>> So, it is in mainline, was released and has not been fixed in linux-next yet.
>>
>> As syzkaller also provides a reproducer, we bisected this memory leak
>> to be introduced with commit e98e49b2bbf7 ("io_uring: extend task put
>> optimisations").
>>
>> Could you please have a look how your commit introduces this memory
>> leak? We will gladly support testing your fix in case help is needed.
>
> Thanks for letting know
> I think I know what it is, will get back later.
https://lore.kernel.org/io-uring/69f226b35fbdb996ab799a8bbc1c06bf634ccec1.1641688805.git.asml.silence@gmail.com
Should fix it, tested with the repro
--
Pavel Begunkov
prev parent reply other threads:[~2022-01-09 0:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-07 15:00 Observation of a memory leak with commit e98e49b2bbf7 ("io_uring: extend task put optimisations") Lukas Bulwahn
2022-01-07 16:22 ` Pavel Begunkov
2022-01-09 0:57 ` Pavel Begunkov [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] \
[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