as a related thread to the earlier one, is there any protection against the kernel stack extending downwards until it overruns the thread_info structure? i'm skeptical that there's *any* call chain in kernel code that would suck up that much kernel stack, but i'm just curious. rday -- ======================================================================== Robert P. J. Day Linux Consulting, Training and Annoying Kernel Pedantry: Have classroom, will lecture. http://crashcourse.ca Waterloo, Ontario, CANADA ======================================================================== -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ