RE: BUG: sleeping function called from invalid context at kernel/fork.c:385

> Ahh okay. cscope will do that too.... But all have __exit.

The trick is that one of them *shouldn't* have __exit.  With cscope
you'll have to use the "Find functions calling this function:"
mode to try and find the __init function that is calling an
__exit function.

-Tony
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • RE: BUG: sleeping function called from invalid context at kernel/fork.c:385
    • From: Christoph Lameter <[email protected]>

• References:
  • Re: BUG: sleeping function called from invalid context at kernel/fork.c:385
    • From: Christoph Lameter <[email protected]>

• Prev by Date: Re: [patch 2/3] Fix XFS_IOC_*_TO_HANDLE and XFS_IOC_{OPEN,READLINK}_BY_HANDLE in compat mode
• Next by Date: Re: [patch] x86_64, irq: check remote IRR bit before migrating level triggered irq
• Previous by thread: Re: BUG: sleeping function called from invalid context at kernel/fork.c:385
• Next by thread: RE: BUG: sleeping function called from invalid context at kernel/fork.c:385
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]