From: Vegard Nossum <vegard.nossum@gmail.com>
To: Sitsofe Wheeler <sitsofe@yahoo.com>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Pekka Enberg <penberg@cs.helsinki.fi>
Subject: Re: Is kmemcheck currently broken on tip?
Date: Sat, 21 Feb 2009 22:35:19 +0100 [thread overview]
Message-ID: <19f34abd0902211335g354b6860ic7244fb699d7d01b@mail.gmail.com> (raw)
In-Reply-To: <19f34abd0902211332r6fd0a1e3l3cee6c49e85f879e@mail.gmail.com>
> 2009/2/21 Sitsofe Wheeler <sitsofe@yahoo.com>:
>> Hi,
>>
>> I've been trying to test kmemcheck in linux-tip on my EeePC and things
>> have been going suspiciously not so slow with little extra memory used
>> (at least compared to the last time I used kmemcheck). While I see
>> [ 0.063412] kmemcheck: "Bugs, beware!"
>> in dmesg, I'm not sure kmemcheck is working especially since nothing is
>> flagged when I trigger the issue described in
>> http://marc.info/?l=linux-kernel&m=123472656015761&w=1 ...
Ah, sorry, you'll probably have to disable SLUB debugging on the
command line if it was enabled by default in the config. Boot with
slub_debug=- parameter. Maybe we should print a warning for this...
Vegard
--
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
-- E. W. Dijkstra, EWD1036
next prev parent reply other threads:[~2009-02-21 21:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-21 21:19 Sitsofe Wheeler
2009-02-21 21:32 ` Vegard Nossum
2009-02-21 21:35 ` Vegard Nossum [this message]
2009-02-21 22:19 ` Vegard Nossum
2009-02-22 0:22 ` Sitsofe Wheeler
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=19f34abd0902211335g354b6860ic7244fb699d7d01b@mail.gmail.com \
--to=vegard.nossum@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=penberg@cs.helsinki.fi \
--cc=sitsofe@yahoo.com \
/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
all inboxes | Powered by JetHome®