[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4DF8CCE1.80400@redhat.com>
Date: Wed, 15 Jun 2011 11:16:49 -0400
From: Rik van Riel <riel@...hat.com>
To: Christoph Lameter <cl@...ux.com>
CC: Linux kernel Mailing List <linux-kernel@...r.kernel.org>,
Kyle McMartin <kyle@...hat.com>
Subject: Re: SLUB BUG: check_slab called with interrupts enabled
On 06/15/2011 11:03 AM, Christoph Lameter wrote:
> On Wed, 15 Jun 2011, Rik van Riel wrote:
>
>> Hi Christoph,
>>
>> last night I got an interesting backtrace running 3.0-rc3
>> (Fedora Rawhide kernel package). Unfortunately netconsole
>> seems to be incompatible with KVM at the moment, so I had
>> to capture the oops on my digital camera and will be
>> transcribing just the backtrace.
>>
>> Essentially, kernel 3.0-rc3 hit this bug:
>>
>> static int check_slab(struct kmem_cache *s, struct page *page)
>> {
>> int maxobj;
>>
>> VM_BUG_ON(!irqs_disabled());
>>
>> The call trace:
>>
>> check_slab
>> alloc_debug_processing
>> __slab_alloc
>> kmem_cache_alloc
>> bvec_alloc_bs
>> bio_alloc_bioset
>> bio_alloc
>> mpage_alloc
>> do_mpage_readpage
>> ... followed by ext4 and VFS code, obviously innocent
>
> __slab_alloc() disables interrupts so alloc_debug_processing() should not
> run into this issue.
>
> 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...
--
All rights reversed
View attachment "mm-slub-do-not-take-expensive-steps-for-slubs-speculative-high-order-allocations.patch" of type "text/plain" (3236 bytes)
View attachment "mm-slub-do-not-wake-kswapd-for-slubs-speculative-high-order-allocations.patch" of type "text/plain" (2243 bytes)
Powered by blists - more mailing lists