linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christophe Leroy <christophe.leroy@c-s.fr>
To: Paul Menzel <pmenzel@molgen.mpg.de>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Paul Mackerras <paulus@samba.org>,
	Michael Ellerman <mpe@ellerman.id.au>
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: Reading `/sys/kernel/debug/kmemleak` takes 3 s and content not shown
Date: Tue, 26 Mar 2019 13:55:46 +0100	[thread overview]
Message-ID: <ad2278fd-ea56-d715-7efb-c4e0adb7314e@c-s.fr> (raw)
In-Reply-To: <f18fb509-bee1-e411-3761-bd28a0d8aab7@molgen.mpg.de>



Le 26/03/2019 à 13:49, Paul Menzel a écrit :
> Dear Linux folks,
> 
> 
> On 19.02.19 10:44, Paul Menzel wrote:
> 
>> On a the IBM S822LC (8335-GTA) with Ubuntu 18.10, and Linux 5.0-rc5+
>> accessing `/sys/kernel/debug/kmemleak` takes a long time. According to
>> strace it takes three seconds.
>>
>> $ dmesg | grep leak
>> [    4.407957] kmemleak: Kernel memory leak detector initialized
>> [    4.407959] kmemleak: Automatic memory scanning thread started
>> [745989.625624] kmemleak: 1 new suspected memory leaks (see 
>> /sys/kernel/debug/kmemleak)
>> [1002619.951902] kmemleak: 1 new suspected memory leaks (see 
>> /sys/kernel/debug/kmemleak)
>> ```
>>
>> Unfortunately, the leaks supposedly stored in that file are not shown
>> either.
> 
> The problem is still present with Linux 5.0. Do you have an idea, how to 
> fix this?
> 

Have you identified a previous version that works properly ?

If so, have you been able to bisect the problem ?

Christophe

  reply	other threads:[~2019-03-26 12:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-19  9:44 Reading `/sys/kernel/debug/kmemleak` takes 3 s and content not shown Paul Menzel
2019-03-26 12:49 ` Paul Menzel
2019-03-26 12:55   ` Christophe Leroy [this message]
2019-03-26 13:17     ` Paul Menzel

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=ad2278fd-ea56-d715-7efb-c4e0adb7314e@c-s.fr \
    --to=christophe.leroy@c-s.fr \
    --cc=benh@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).