From: "Andrey J. Melnikoff (TEMHOTA)" <temnota@kmv.ru>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: Willy Tarreau <willy@w.ods.org>, linux-kernel@vger.kernel.org
Subject: [RESOLVED] Re: [2.4.28-rc1] process stuck in release_task() call
Date: Tue, 30 Nov 2004 22:46:56 +0300 [thread overview]
Message-ID: <20041130194656.GA24188@kmv.ru> (raw)
In-Reply-To: <20041116100639.GA11948@logos.cnet>
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
next prev parent reply other threads:[~2004-11-30 19:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-09 16:24 [2.4.28-rc1] process stuck in release_task() call Andrey J. Melnikoff (TEMHOTA)
2004-11-10 18:58 ` Marcelo Tosatti
2004-11-11 8:33 ` Willy Tarreau
2004-11-11 8:01 ` Marcelo Tosatti
[not found] ` <20041112135942.GW24130@kmv.ru>
[not found] ` <20041116100639.GA11948@logos.cnet>
2004-11-30 19:46 ` Andrey J. Melnikoff (TEMHOTA) [this message]
2004-11-11 13:37 ` Andrey Melnikoff
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20041130194656.GA24188@kmv.ru \
--to=temnota@kmv.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=willy@w.ods.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox