public inbox for [email protected]
 help / color / mirror / Atom feed
From: Lukas Bulwahn <[email protected]>
To: Pavel Begunkov <[email protected]>, Jens Axboe <[email protected]>
Cc: Linux Kernel Mailing List <[email protected]>,
	[email protected]
Subject: Observation of a memory leak with commit e98e49b2bbf7 ("io_uring: extend task put optimisations")
Date: Fri, 7 Jan 2022 16:00:39 +0100	[thread overview]
Message-ID: <CAKXUXMzHUi3q4K-OpiBKyMAsQ2K=FOsVzULC76v05nCUKNCA+Q@mail.gmail.com> (raw)

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.


Best regards,

Lukas

             reply	other threads:[~2022-01-07 15:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-07 15:00 Lukas Bulwahn [this message]
2022-01-07 16:22 ` Observation of a memory leak with commit e98e49b2bbf7 ("io_uring: extend task put optimisations") Pavel Begunkov
2022-01-09  0:57   ` Pavel Begunkov

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='CAKXUXMzHUi3q4K-OpiBKyMAsQ2K=FOsVzULC76v05nCUKNCA+Q@mail.gmail.com' \
    [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