From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: serious multithreaded core-dumping problems
Date: Tue, 18 Nov 2003 21:54:41 +0000 [thread overview]
Message-ID: <marc-linux-ia64-106919259317135@msgid-missing> (raw)
While working on a new-syscall-stub-enabled libc, I noticed serious
stability problems with 2.6.0-test9 when dumping core from a
multi-threaded app. I thought this code had been well-tested on ia64
and multi-threaded apps, but I'm wondering now whether the code relied
on implicit synchronization guarantees from LinuxThreads which don't
hold for NPTL (and indeed, the code in binfmt_elf32 looks rather racy
to me). Does someone have the bandwidth to investigate this? I'm
willing to do it, but my plate is pretty full and I'm worried we may
miss the 2.6.0 (final) if I have to look into it.
--david
reply other threads:[~2003-11-18 21:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=marc-linux-ia64-106919259317135@msgid-missing \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@vger.kernel.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