[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.00.1207090853450.27519@router.home>
Date: Mon, 9 Jul 2012 08:55:02 -0500 (CDT)
From: Christoph Lameter <cl@...ux.com>
To: JoonSoo Kim <js1304@...il.com>
cc: Fengguang Wu <fengguang.wu@...el.com>,
Vegard Nossum <vegard.nossum@...il.com>,
Pekka Enberg <penberg@...nel.org>,
Linux Memory Management List <linux-mm@...ck.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: WARNING: __GFP_FS allocations with IRQs disabled
(kmemcheck_alloc_shadow)
On Mon, 9 Jul 2012, JoonSoo Kim wrote:
> 2012/7/8 Fengguang Wu <fengguang.wu@...el.com>:
> > 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 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