| 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
| ||
|
Message-ID: <4DF8DCB8.9050103@redhat.com> Date: Wed, 15 Jun 2011 12:24:24 -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: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 -- 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/
Powered by blists - more mailing lists