From: David Sterba <dsterba@suse.cz>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: Chris Mason <clm@fb.com>, Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>,
linux-btrfs@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>
Subject: Re: BTRFS: Kmemleak errrors with do_sys_ftruncate
Date: Fri, 26 Jul 2019 15:29:22 +0200 [thread overview]
Message-ID: <20190726132922.GA2868@twin.jikos.cz> (raw)
In-Reply-To: <8c9b2f4e-252c-fee7-ef52-4ec2b9b54042@molgen.mpg.de>
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.
prev parent reply other threads:[~2019-07-26 13:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-26 13:16 Paul Menzel
2019-07-26 13:25 ` Nikolay Borisov
2019-07-26 13:29 ` David Sterba [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 \
--in-reply-to=20190726132922.GA2868@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=catalin.marinas@arm.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmenzel@molgen.mpg.de \
/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
all inboxes | Powered by JetHome®