On Wed, 30 May 2007, Randy Dunlap wrote: > OK. I would write the file to disk and view it with an editor. > Then at each occurrence of /exit.text/, see if it's inside an __init > function... Ahh okay. cscope will do that too.... But all have __exit. - 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:
- References:
- RE: BUG: sleeping function called from invalid context at kernel/fork.c:385
- From: "Luck, Tony" <[email protected]>
- RE: BUG: sleeping function called from invalid context at kernel/fork.c:385
- From: Christoph Lameter <[email protected]>
- Re: BUG: sleeping function called from invalid context at kernel/fork.c:385
- From: Randy Dunlap <[email protected]>
- Re: BUG: sleeping function called from invalid context at kernel/fork.c:385
- From: Christoph Lameter <[email protected]>
- Re: BUG: sleeping function called from invalid context at kernel/fork.c:385
- From: Randy Dunlap <[email protected]>
- RE: BUG: sleeping function called from invalid context at kernel/fork.c:385
- Prev by Date: Re: [PATCH] drivers/block/ub.c: use list_for_each_entry()
- Next by Date: Re: [PATCH} x86_64 PM_TRACE support.
- 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):