linux-kernel - Re: Observation of a memory leak with commit e98e49b2bbf7 ("io

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <e8f2a002-4364-18e4-41a4-228cd364feef@gmail.com>
Date:   Fri, 7 Jan 2022 16:22:44 +0000
From:   Pavel Begunkov <asml.silence@...il.com>
To:     Lukas Bulwahn <lukas.bulwahn@...il.com>,
        Jens Axboe <axboe@...nel.dk>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        io-uring@...r.kernel.org
Subject: Re: Observation of a memory leak with commit e98e49b2bbf7 ("io_uring:
 extend task put optimisations")

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.

-- 
Pavel Begunkov