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:45:03 -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:

> > 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()?
Content of type "TEXT/PLAIN" skipped

View attachment "mm-slub-do-not-wake-kswapd-for-slubs-speculative-high-order-allocations.patch" of type "TEXT/PLAIN" (2243 bytes)