linux-kernel - Re: 2.6.31-rc4 - slab entry tak_delay

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

Message-ID: <20090731220356.4e5c8d0b@tux.DEF.witbe.net>
Date:	Fri, 31 Jul 2009 22:03:56 +0200
From:	Paul Rolland <rol@...917.net>
To:	Catalin Marinas <catalin.marinas@....com>
Cc:	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.31-rc4 - slab entry tak_delay_info leaking ???

Hi Catalin,

On Thu, 30 Jul 2009 16:53:33 +0100
Catalin Marinas <catalin.marinas@....com> wrote:

> Paul Rolland <rol@...917.net> wrote:
> >> On Wed, 29 Jul 2009 08:20:47 +0200
> >> Paul Rolland <rol@...917.net> wrote:
> >> > Since I'm running 2.6.31-rc? (3 or 4 I think), I often find my
> >> > machine with my X session killed in the morning, and the kdm login
> >> > screen displayed.
> [...]
> > Well, I've killed my X session, and it stopped the "leak"... but
> > didn't recover the "lost" task_delay_info...
> 
> You could try to enable CONFIG_KMEMLEAK and see if you get any leaks
> reported for the "lost" task_delay_info (see Documentation/kmemleak.txt).

I'm now running a kmemleak-eanbled version of the kernel, and waiting for
the same problem to happen again.

In the meantime, my machine is kmemleak-complaining a lot :
Jul 31 20:57:35 tux kernel: kmemleak: 52 new suspected memory leaks
(see /sys/kernel/debug/kmemleak) 
Jul 31 21:07:41 tux kernel: kmemleak: 34 new suspected memory leaks
(see /sys/kernel/debug/kmemleak) 
Jul 31 21:17:47 tux kernel: kmemleak: 23 new suspected memory leaks
(see /sys/kernel/debug/kmemleak) 
Jul 31 21:27:54 tux kernel: kmemleak: 33 new suspected memory leaks
(see /sys/kernel/debug/kmemleak) 
Jul 31 21:38:01 tux kernel: kmemleak: 20 new suspected memory leaks
(see /sys/kernel/debug/kmemleak) 
Jul 31 21:48:07 tux kernel: kmemleak: 21 new suspected memory leaks
(see /sys/kernel/debug/kmemleak) 
Jul 31 21:58:15 tux kernel: kmemleak: 32 new suspected memory leaks 
(see /sys/kernel/debug/kmemleak)
 
What should I do with these reports ? Is there an easy way to check if they
are normal (false-positive) ?

Regards,
Paul

-- 
Paul Rolland                                E-Mail : rol(at)witbe.net
CTO - Witbe.net SA                          Tel. +33 (0)1 47 67 77 77
Les Collines de l'Arche                     Fax. +33 (0)1 47 67 77 99
F-92057 Paris La Defense                    RIPE : PR12-RIPE

Please no HTML, I'm not a browser - Pas d'HTML, je ne suis pas un
navigateur "Some people dream of success... while others wake up and work
hard at it" 

"I worry about my child and the Internet all the time, even though she's
too young to have logged on yet. Here's what I worry about. I worry that 10
or 15 years from now, she will come to me and say 'Daddy, where were you
when they took freedom of the press away from the Internet?'"
--Mike Godwin, Electronic Frontier Foundation 
--
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/