From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757890Ab1FPMeX (ORCPT ); Thu, 16 Jun 2011 08:34:23 -0400 Received: from mx1.redhat.com ([209.132.183.28]:56079 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755692Ab1FPMeW (ORCPT ); Thu, 16 Jun 2011 08:34:22 -0400 Message-ID: <4DF9F84B.7040007@redhat.com> Date: Thu, 16 Jun 2011 08:34:19 -0400 From: Rik van Riel User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110428 Fedora/3.1.10-1.fc15 Lightning/1.0b3pre Thunderbird/3.1.10 MIME-Version: 1.0 To: Christoph Lameter CC: Linux kernel Mailing List , Kyle McMartin Subject: Re: SLUB BUG: check_slab called with interrupts enabled References: <4DF8C80F.7090403@redhat.com> <4DF8CCE1.80400@redhat.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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