From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from psmtp.com (na3sys010amx163.postini.com [74.125.245.163]) by kanga.kvack.org (Postfix) with SMTP id F32346B006C for ; Mon, 9 Jul 2012 09:55:04 -0400 (EDT) Date: Mon, 9 Jul 2012 08:55:02 -0500 (CDT) From: Christoph Lameter Subject: Re: WARNING: __GFP_FS allocations with IRQs disabled (kmemcheck_alloc_shadow) In-Reply-To: Message-ID: References: <20120708040009.GA8363@localhost> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-mm@kvack.org List-ID: To: JoonSoo Kim Cc: Fengguang Wu , Vegard Nossum , Pekka Enberg , Linux Memory Management List , LKML On Mon, 9 Jul 2012, JoonSoo Kim wrote: > 2012/7/8 Fengguang Wu : > > Hi Vegard, > > > > This warning code is triggered for the attached config: > > > > __lockdep_trace_alloc(): > > /* > > * Oi! Can't be having __GFP_FS allocations with IRQs disabled. > > */ > > if (DEBUG_LOCKS_WARN_ON(irqs_disabled_flags(flags))) > > return; > > > > Where the irq is possibly disabled at the beginning of __slab_alloc(): > > > > local_irq_save(flags); > > Currently, in slub code, kmemcheck_alloc_shadow is always invoked with > irq_disabled. > I think that something like below is needed. Or you could move the kmem_check_enabled section to occur before the irq is disabled. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org