From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Christophe Leroy <christophe.leroy@c-s.fr>,
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 14:17:01 +0100 [thread overview]
Message-ID: <33ad8e80-4275-d5bf-9b6a-052dd8afe7ef@molgen.mpg.de> (raw)
In-Reply-To: <ad2278fd-ea56-d715-7efb-c4e0adb7314e@c-s.fr>
Dear Christophe,
On 26.03.19 13:55, Christophe Leroy wrote:
> Le 26/03/2019 à 13:49, Paul Menzel a écrit :
>> 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?
It seems to have worked with Linux 4.18-rc4+ [1].
> If so, have you been able to bisect the problem?
No, sorry, I have not. I do not have resources for this.
Kind regards,
Paul
[1]: https://lists.ozlabs.org/pipermail/linuxppc-dev/2018-July/175658.html
prev parent reply other threads:[~2019-03-26 13:17 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
2019-03-26 13:17 ` Paul Menzel [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=33ad8e80-4275-d5bf-9b6a-052dd8afe7ef@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--cc=benh@kernel.crashing.org \
--cc=christophe.leroy@c-s.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
/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).