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:	Thu, 16 Jun 2011 08:34:19 -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.

After backing them out, I got 18 hours of uptime so far.

This could just be dumb luck, or it could be some slub vs. kswapd
interaction.  Or maybe I simply am not triggering the original
bug any more because kswapd is now doing all the work, but may
still be able to trigger it under more memory pressure...

Either way, since this could still be dumb luck, I'll let you
guys know if/when I see a next crash :)

-- 
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/