From: Frans Pop <elendil@planet.nl>
To: "Pekka Enberg" <penberg@cs.helsinki.fi>
Cc: "Pete Zaitcev" <zaitcev@redhat.com>,
"Ingo Molnar" <mingo@elte.hu>,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
gregkh@suse.de, "Christoph Lameter" <clameter@sgi.com>
Subject: Re: [sched-devel/latest] WARNING: at mm/slub.c:2443
Date: Wed, 23 Apr 2008 20:15:26 +0200 [thread overview]
Message-ID: <200804232015.27257.elendil@planet.nl> (raw)
In-Reply-To: <84144f020804231035w3fdb10aax4b90dc4e0bc1957d@mail.gmail.com>
On Wednesday 23 April 2008, Pekka Enberg wrote:
> Well, a race in mon_text_release() after the kmem_cache_free() loop
> and the call to kmem_cache_destroy() but looks like that can't happen
> either. Frans, is this easily triggerable? If so, can you try with
> CONFIG_SLAB and CONFIG_DEBUG_SLAB enabled instead?
Not really. I've only seen it once two days ago and not at all today while I
was doing the traces for the scheduling issue.
I can give it a go, but I'm not yet ready to switch to current git on this
box for longer periods (although so far I've actually had less issues than
with .24-rc1; fingers crossed). If I get anything I'll follow up.
next prev parent reply other threads:[~2008-04-23 18:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-21 21:10 [sched-devel/latest] WARNING: at mm/slub.c:2443 Frans Pop
2008-04-22 13:40 ` Ingo Molnar
2008-04-22 17:27 ` Pekka J Enberg
2008-04-22 19:22 ` Christoph Lameter
2008-04-22 21:32 ` Pete Zaitcev
2008-04-23 5:21 ` Pekka J Enberg
2008-04-23 6:51 ` Pete Zaitcev
2008-04-23 7:31 ` Pekka Enberg
2008-04-23 7:34 ` Pekka Enberg
2008-04-23 17:13 ` Pete Zaitcev
2008-04-23 7:38 ` Pekka J Enberg
2008-04-23 17:11 ` Pete Zaitcev
2008-04-23 17:35 ` Pekka Enberg
2008-04-23 18:15 ` Frans Pop [this message]
2008-04-24 14:13 ` Frans Pop
2008-05-02 9:17 ` 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=200804232015.27257.elendil@planet.nl \
--to=elendil@planet.nl \
--cc=clameter@sgi.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=penberg@cs.helsinki.fi \
--cc=zaitcev@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.