From mboxrd@z Thu Jan 1 00:00:00 1970 From: Satyam Sharma Subject: Re: BUG: scheduling while atomic: ifconfig/0x00000002/4170 Date: Thu, 6 Sep 2007 14:11:46 +0530 (IST) Message-ID: References: <20070902184439.GA14306@paradigm.rfc822.org> <6bffcb0e0709021659o3856cd06gabc054c949a84397@mail.gmail.com> <20070906082301.GB21929@gondor.apana.org.au> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=UTF-8 Cc: Florian Lohoff , Linux Kernel Mailing List , Netdev , linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Michal Piotrowski , ipw3945-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org, yi.zhu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org To: Herbert Xu Return-path: In-Reply-To: <20070906082301.GB21929-lOAM2aK0SrRLBo1qDEOMRrpzq4S04n8Q@public.gmane.org> Sender: linux-wireless-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: netdev.vger.kernel.org On Thu, 6 Sep 2007, Herbert Xu wrote: > On Thu, Sep 06, 2007 at 10:32:33AM +0530, Satyam Sharma wrote: > > > > > > [ 382.529041] [] dev_close+0x24/0x67 > > > > [ 382.529052] [] ieee80211_master_stop+0x4a/0x6d [mac80211] > > This is where the bug is. You cannot call dev_close from an > atomic context as i33380211_master_stop does it within spin > locks. Doh, of course! I must be blind ... and wait_for_completion()'s might_sleep() clearly didn't trigger earlier because Florian must've had CONFIG_DEBUG_SPINLOCK_SLEEP off in his .config ...