mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Rolland <rol@as2917.net>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.31-rc4 - slab entry tak_delay_info leaking ???
Date: Fri, 31 Jul 2009 22:03:56 +0200	[thread overview]
Message-ID: <20090731220356.4e5c8d0b@tux.DEF.witbe.net> (raw)
In-Reply-To: <tnxeiry88w2.fsf@pc1117.cambridge.arm.com>

Hi Catalin,

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

> Paul Rolland <rol@as2917.net> wrote:
> >> On Wed, 29 Jul 2009 08:20:47 +0200
> >> Paul Rolland <rol@as2917.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 

      reply	other threads:[~2009-07-31 20:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-29  6:20 Paul Rolland
2009-07-30 10:07 ` Paul Rolland
2009-07-30 10:26   ` Paul Rolland
2009-07-30 15:53     ` Catalin Marinas
2009-07-31 20:03       ` Paul Rolland [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=20090731220356.4e5c8d0b@tux.DEF.witbe.net \
    --to=rol@as2917.net \
    --cc=catalin.marinas@arm.com \
    --cc=linux-kernel@vger.kernel.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

Powered by JetHome