Messages in this thread | | | Date | Mon, 1 Mar 1999 18:15:58 +0000 (GMT) | From | Mark Hemment <> | Subject | Re: 2.2.1: memory corruption and SIGSEGV handlers. |
| |
Richard,
> > > So you are saying that setup_frame() should reserve enough signal > > > stack-space to use the default handler if the signal stack grows > > > beyond limits? Let's look at the case of root where there is no > > > getrlimit set. > > > > No. The default action for SEGV (the signal we are interested here), > > is to drop core. This doesn't require any user-stack space (just a call > > to do_exit()). > > > > But isn't that call on the signal stack?
No. do_exit() would be called from the kernel's signal delivery code (in fact it already is when the installed handler is SIG_DFL). All carries on running in kernel space, there is no return to user-space and so no need to use the user's stack.
Mark
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |