| |||||||||||||
How exactly would you handle a stack overflow in kernel space?How exactly would you handle a stack overflow in kernel space?Posted Sep 10, 2005 10:15 UTC (Sat) by pkolloch (subscriber, #21709)In reply to: 4K stacks for everyone? by mcelrath Parent article: 4K stacks for everyone?
I think it is not that easy to gracefully deal with stack overflows, even if they get detected. What do you do, if the process scheduler triggers a stack overflow? Disable it?
Even for device drivers the general case gets tricky... [besides the fact that at least the device in question would have to stop working]
(Log in to post comments)
How exactly would you handle a stack overflow in kernel space? Posted Sep 11, 2005 1:04 UTC (Sun) by giraffedata (subscriber, #1954) [Link] In most cases, an oops is easy, and significantly more graceful than what we have now. In some cases (e.g. process scheduler), oops isn't possible, but panic is still more graceful than we we have.
|
|||||||||||||