lkml.org 
[lkml]   [1999]   [Mar]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: 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/

\
 
 \ /
  Last update: 2005-03-22 13:50    [W:0.086 / U:0.020 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site