From: Ingo Molnar <mingo@elte.hu>
To: Christoph Lameter <clameter@sgi.com>
Cc: Pekka J Enberg <penberg@cs.helsinki.fi>,
linux-kernel@vger.kernel.org,
James Bottomley <James.Bottomley@HansenPartnership.com>
Subject: Re: [bug] SCSI/SLUB - latest -git: WARNING: at mm/slub.c:2443 kmem_cache_destroy, scsi_put_host_cmd_pool()
Date: Mon, 21 Apr 2008 15:50:53 +0200 [thread overview]
Message-ID: <20080421135052.GL9554@elte.hu> (raw)
In-Reply-To: <Pine.LNX.4.64.0804202257120.13872@schroedinger.engr.sgi.com>
* Christoph Lameter <clameter@sgi.com> wrote:
> On Sat, 19 Apr 2008, Pekka J Enberg wrote:
>
> > > [a few .config options were turned off: just accept all the defaults
> > > after 'make oldconfig']
> >
> > I couldn't spot anything in particular in SLUB which makes me think
> > SCSI code simply didn't free all objects before
> > scsi_put_host_cmd_pool() called kmem_cache_destroy() to kill the
> > cache.
> >
> > James, does this make sense or should I just look at SLUB harder?
>
> The WARN is intended to warn that a kmem_cache_destroy was run with
> objects not freed.
i suspect if that warn-on triggers more frequently then it might make
sense to turn it into a pretty SLUB warning about that cache, with a
stackdump at the end. (that way people are not tricked into mistakenly
believing that it's a SLUB bug)
Ingo
next prev parent reply other threads:[~2008-04-21 13:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-19 8:57 [bug] SCSI/SLUB - latest -git: WARNING: at mm/slub.c:2443 kmem_cache_destroy, scsi_put_host_cmd_pool() Ingo Molnar
2008-04-19 9:11 ` Pekka J Enberg
2008-04-19 10:43 ` Ingo Molnar
2008-04-21 5:58 ` Christoph Lameter
2008-04-21 13:50 ` Ingo Molnar [this message]
2008-04-19 13:22 ` James Bottomley
2008-04-21 13:49 ` Ingo Molnar
2008-04-21 15:57 ` James Bottomley
2008-04-22 13:10 ` Ingo Molnar
2008-04-22 13:39 ` James Bottomley
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=20080421135052.GL9554@elte.hu \
--to=mingo@elte.hu \
--cc=James.Bottomley@HansenPartnership.com \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
/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