[RESOLVED] Re: [2.4.28-rc1] process stuck in release_task() call

From: Andrey J. Melnikoff (TEMHOTA) (temnota_at_kmv.ru)
Date: 11/30/04

  • Next message: Bernard Hatt: "Re: Yet another filesystem - sffs"
    Date:	Tue, 30 Nov 2004 22:46:56 +0300
    To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
    
    

    Hello Marcelo, Willy!
     On Tue, Nov 16, 2004 at 08:06:42AM -0200, Marcelo Tosatti wrote next:

    > On Fri, Nov 12, 2004 at 04:59:42PM +0300, Andrey J. Melnikoff (TEMHOTA) wrote:
    > Andrey,
    >
    > I do not have much of a clue of what is going on here.
    show_trace() has made a fool of me and I started to ask silly questions :)
     
    > Can you try 2.4.27 please?
    Ok, i'm tested 2.4.25 - same result. But this is complete userland problem.

    There two problem:

    First - show_trace() give incorrect traces. it strat unwind stack from
    address in `tsk->thread.esp', but it should use address saved in `regs->ebp'
    - this make more accuracy stack trace.

    Second - strange libpthreads problem.
    libpthreads always install own sa_restorer helper, and when first signal
    arrived - call signal handler and if (when process in signal handler)
    arrived new signal - lipthreads start play with rt_sigprocmask() and
    rt_sigsuspend() syscalls inside own sa_restorer helper.
    woops - infinity loop inside libpthreads.

    -- 
     Best regards, TEMHOTA-RIPN aka MJA13-RIPE
     System Administrator. mailto:temnota@kmv.ru
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at  http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at  http://www.tux.org/lkml/
    

  • Next message: Bernard Hatt: "Re: Yet another filesystem - sffs"

    Relevant Pages

    • Re: [patch] signal handler defaulting fix ...
      ... during the delivery disables the signal. ... Then when the signal handler ... again, the kernel does not honor the existing handler, but it reset to ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: Add pselect, ppoll system calls.
      ... sure that the signal handler should be called. ... version of my program on Solaris 10 or the Unix-03 conversion of AIX ... I'd say the behaviour should in fact be like what sigsuspend() does. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: [PATCH] PPC32: cancel syscall restart on signal delivery
      ... > You're missing that the only thing that ever looks at restart_block is the ... that can get changed by the signal handler. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • [BUG] in copy_siginfo_to_user32 on ppc64 (and others?) in 2.6.9/2.6.10
      ... the problems that I had tracking it down. ... different based on whether I used a signal handler in the regular way, ... then copied the results to the userspace struct using ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: More trouble with i386 EFLAGS and ptrace
      ... I bought it, but the GDB testsuite didn't. ... there's generally no signal handler for SIGTRAP, ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)