Re: init_idle reaped before final call

From: Thomas Hood (jdthood@mail.com)
Date: Tue Mar 05 2002 - 17:06:43 EST

Next message: Tim Waugh: "Re: [BUG] 2.4.18-pre/rc broke PLIP"
Previous message: Steffen Persvold: "Re: Does kmalloc always return address below 4GB?"
Maybe in reply to: Kip Walker: "init_idle reaped before final call"
Next in thread: Keith Owens: "Re: init_idle reaped before final call"
Reply: Keith Owens: "Re: init_idle reaped before final call"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

I think you're right. To prevent the mistake from
happening again, I'd suggest you add a comment to your
patch for init_idle(), explaining that it can't be __init
because it is called by cpu_idle, which is called
by rest_init(), which ...

I wonder if an automated __init consistency checker
would be helpful.

-- Thomas Hood

- 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/

Next message: Tim Waugh: "Re: [BUG] 2.4.18-pre/rc broke PLIP"
Previous message: Steffen Persvold: "Re: Does kmalloc always return address below 4GB?"
Maybe in reply to: Kip Walker: "init_idle reaped before final call"
Next in thread: Keith Owens: "Re: init_idle reaped before final call"
Reply: Keith Owens: "Re: init_idle reaped before final call"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Thu Mar 07 2002 - 21:00:47 EST