[lkml]   [2004]   [Jun]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: 2.6.x signal handler bug
    On Sat, Jun 26, 2004 at 09:05:34AM -0700, Davide Libenzi wrote:

    > You're receiving a SIGSEGV while SIGSEGV is blocked (force_sig_info). The
    > force_sig_info call wants to send a signal that the task can't refuse
    > (kinda The GodFather offers ;). The kernel will noticed this and will
    > restore the handler to SIG_DFL.


    So checking whether this is POSIX conforming:

    - Blocking a signal in its signal handler is explicitly allowed.
    - It is unspecified what longjmp() does with the signal mask.
    - The SIGSEGV that occurs during a stack overflow is of the GodFather kind.
    - If SIGSEGV is generated while blocked, the result is undefined

    So, maybe the restoring to SIG_DFL was not required, but it doesnt seem
    incorrect either. It may be a bit surprising.

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-03-22 14:04    [W:0.021 / U:17.708 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site