[lkml]   [2003]   [Mar]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: 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?


    greg k-h
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-03-22 13:34    [W:0.021 / U:0.056 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site