[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ad2278fd-ea56-d715-7efb-c4e0adb7314e@c-s.fr>
Date: Tue, 26 Mar 2019 13:55:46 +0100
From: Christophe Leroy <christophe.leroy@....fr>
To: Paul Menzel <pmenzel@...gen.mpg.de>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Paul Mackerras <paulus@...ba.org>,
Michael Ellerman <mpe@...erman.id.au>
Cc: linuxppc-dev@...ts.ozlabs.org, linux-kernel@...r.kernel.org
Subject: Re: Reading `/sys/kernel/debug/kmemleak` takes 3 s and content not
shown
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
Powered by blists - more mailing lists