mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Daniel J Blueman <daniel.blueman@gmail.com>
Cc: Catalin Marinas <catalin.marinas@gmail.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [2.6.35-rc6 patch] increase kmemleak robustness at boot
Date: Wed, 28 Jul 2010 19:49:10 +0300	[thread overview]
Message-ID: <4C505F86.7050509@cs.helsinki.fi> (raw)
In-Reply-To: <AANLkTin-9jtHP1xmhUp4uUQNZD64pN3Ee5Kn2cqH64Go@mail.gmail.com>

Daniel J Blueman wrote:
> I've consistently been experiencing kmemleak exhaust it's 400-entry
> early-boot buffer and disabling itself; there have been reports of
> this also, and I'm finding this on x86-64 with various debug options
> enabled.
> 
> If we issue a warning and allow the buffer to wrap, we don't need to
> hit the kill-switch. While we lose track of some early potential
> leaks, it's better than no functionality.
> 
> Let me know if it's acceptable, and many thanks for such an excellent tool,

Is it just potential leaks that we lose or can this cause false positives?

  reply	other threads:[~2010-07-28 16:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-28 16:40 Daniel J Blueman
2010-07-28 16:49 ` Pekka Enberg [this message]
2010-07-28 18:39   ` Daniel J Blueman
2010-07-29 11:34   ` Catalin Marinas
2010-07-29 12:48     ` Daniel J Blueman
2010-07-29 15:12       ` Pekka Enberg
2010-07-29 18:03         ` Daniel J Blueman
2010-07-29 18:50           ` Pekka Enberg
2010-07-29 20:39             ` Catalin Marinas
2010-07-31  9:42               ` Pekka Enberg

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=4C505F86.7050509@cs.helsinki.fi \
    --to=penberg@cs.helsinki.fi \
    --cc=catalin.marinas@gmail.com \
    --cc=daniel.blueman@gmail.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