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] [day] [month] [year] [list]
Message-ID: <20190726132922.GA2868@twin.jikos.cz>
Date:   Fri, 26 Jul 2019 15:29:22 +0200
From:   David Sterba <dsterba@...e.cz>
To:     Paul Menzel <pmenzel@...gen.mpg.de>
Cc:     Chris Mason <clm@...com>, Josef Bacik <josef@...icpanda.com>,
        David Sterba <dsterba@...e.com>, linux-btrfs@...r.kernel.org,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Catalin Marinas <catalin.marinas@....com>
Subject: Re: BTRFS: Kmemleak errrors with do_sys_ftruncate

On Fri, Jul 26, 2019 at 03:16:57PM +0200, Paul Menzel wrote:
> Dear Linux folks,
> 
> 
> On a Power 8 server
> 
>     Linux power 5.3.0-rc1+ #1 SMP Fri Jul 26 11:34:28 CEST 2019 ppc64le ppc64le ppc64le GNU/Linux
> 
> Kmemleak reports the warnings below.

There are memory leaks of struct extent_state introduced in 5.3 pull and
there's a fix going to 5.3-rc2 (https://patchwork.kernel.org/patch/11060447/).

> I believe these have been present for some releases already, but Kmemleak
> was broken until now on that system, so that I could only report them now.

We have a leak detector built-in btrfs so I think we'd notice and that
you observe the known leak. You could try to apply the patch or wait for
rc2 and restst.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ