linux-kernel - Re: detecting kernel mem leak

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] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 15 May 2008 12:58:38 +0200
From:	Stéphane ANCELOT <sancelot@...e.fr>
To:	unlisted-recipients:; (no To-header on input)
Cc:	linux-kernel@...r.kernel.org
Subject: Re: detecting kernel mem leak



Pekka Enberg a écrit :
> On Tue, May 13, 2008 at 11:50 AM, Stéphane ANCELOT <sancelot@...e.fr> wrote:
>   
>>  The are some signifiant changes in slabinfo but now, I do not know where
>>  to search ?
>>     
>
> Can you please post your full dmesg, /proc/slabinfo and /proc/meminfo
> output please?
> --
>   
Enclosed are outputs.

However, after some analyzes and enabling DEBUG mem features of the 
kernel , I found anormal proc_inode_cache , and a bug in fork process 
(my kernel has got  patches enabling Realtime features)
This has been corrected, but know, I am waiting again for new results of 
stability , there may be other problems.
Best Regards
Steph
 
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>
>
>   

View attachment "v1m.txt" of type "text/plain" (22022 bytes)

View attachment "v2m.txt" of type "text/plain" (22022 bytes)

View attachment "dmesg.txt" of type "text/plain" (15294 bytes)