Messages in this thread | | | Date | Wed, 19 Mar 2003 20:39:32 -0800 | From | Greg KH <> | Subject | Re: Sleeping in illegal context with 2.5.65-mm2 |
| |
On Thu, Mar 20, 2003 at 03:58:41AM +0100, Alexander Hoogerhuis wrote: > Caught this one while booting my laptop: > > drivers/usb/core/usb.c: registered new driver hci_usb > Module bluetooth cannot be unloaded due to unsafe usage in include/linux/module.h:457 > Debug: sleeping function called from illegal context at mm/slab.c:1723 > Call Trace: > [<c0119d92>] __might_sleep+0x5f/0x65 > [<c013a097>] kmalloc+0x88/0x8f > [<c0238111>] usb_alloc_urb+0x21/0x51 > [<f09180bc>] hci_usb_enable_intr+0x20/0xf8 [hci_usb]
The call to usb_alloc_urb() here is being done with the GFP_ATOMIC flag, which is correct. Do we need to fix up the warning message to prevent false positives like this from happening?
thanks,
greg k-h - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |