From: Manfred Spraul <manfred@colorfullife.com>
To: Andreas Dilger <adilger@clusterfs.com>, linux-kernel@vger.kernel.org
Subject: Re: [BUG] CONFIG_DEBUG_SLAB broken on SMP
Date: Wed, 09 Oct 2002 21:50:13 +0200 [thread overview]
Message-ID: <3DA48875.6020604@colorfullife.com> (raw)
> The problem appears to be in the SMP version of __kmem_cache_alloc()
> and __kmem_cache_free(), where it simply sticks the obj in the per-CPU
> list without doing the poison or redzone stuff that is done inside
> kmem_cache_free_one_tail().
>
The simplest solution is to skip the code that enables the per-cpu
caches if debugging is enabled:
Search for enable_all_cpucaches in mm/slab.c, and skip the call if DEBUG
is enabled.
2.5.41-mm1 contains a partially rewritten slab, which performs the
poisoning before adding an object into the cpu caches. Additionally,
even caches with constructors are not poisoned - ctor and dtor calls are
performed in kmem_cache_alloc/free.
--
Manfred
next reply other threads:[~2002-10-09 19:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-09 19:50 Manfred Spraul [this message]
2002-10-09 21:33 ` [BUG] CONFIG_DEBUG_SLAB broken on SMP William Lee Irwin III
-- strict thread matches above, loose matches on Subject: below --
2002-10-09 19:13 Andreas Dilger
2002-10-09 19:41 ` Andrew Morton
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=3DA48875.6020604@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=adilger@clusterfs.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