linux-kernel - Re: SLUB BUG: check_slab called with interrupts enabled

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 15 Jun 2011 10:03:14 -0500 (CDT)
From:	Christoph Lameter <cl@...ux.com>
To:	Rik van Riel <riel@...hat.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 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.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/