From: Rik van Riel <riel@redhat.com>
To: Christoph Lameter <cl@linux.com>
Cc: Linux kernel Mailing List <linux-kernel@vger.kernel.org>,
Kyle McMartin <kyle@redhat.com>
Subject: Re: SLUB BUG: check_slab called with interrupts enabled
Date: Wed, 15 Jun 2011 12:24:24 -0400 [thread overview]
Message-ID: <4DF8DCB8.9050103@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1106151040020.768@router.home>
On 06/15/2011 11:45 AM, Christoph Lameter wrote:
> On Wed, 15 Jun 2011, Rik van Riel wrote:
>
>> > There are no additional special slub patches applied right? Because
>> some
>> > of the patches under discussion change the interrupt disable handling a
>> > bit.
>>
>> Just the two attached ones, which don't seem to touch the
>> code path in question...
>
> I also do not see how these could break something. But they are mucking
> around with the __GFP_WAIT flag. __GFP_WAIT determines the reenabling and
> redisabling of interrupts in __slab_alloc(). If some variables gets
> corrupted then this could be the result.
>
> Print out the value of gfpflags before and after the call to new_slab()
> from __slab_alloc()?
Since I'm building a new kernel anyway (with Neil Horman's
patch to make netconsole work with tun/tap), I have commented
out these two slub patches.
Lets see what happens...
--
All rights reversed
next prev parent reply other threads:[~2011-06-15 16:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-15 14:56 SLUB BUG: check_slab called with interrupts enabled Rik van Riel
2011-06-15 15:03 ` Christoph Lameter
2011-06-15 15:16 ` Rik van Riel
2011-06-15 15:45 ` Christoph Lameter
2011-06-15 16:24 ` Rik van Riel [this message]
2011-06-16 12:34 ` Rik van Riel
2011-06-16 15:57 ` Christoph Lameter
2011-06-17 0:22 ` Rik van Riel
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=4DF8DCB8.9050103@redhat.com \
--to=riel@redhat.com \
--cc=cl@linux.com \
--cc=kyle@redhat.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