From: jacobs@genehack.org (John S. J. Anderson)
To: linux-kernel@vger.kernel.org
Subject: Procfs-related core dump deadlock
Date: Thu, 28 Feb 2002 17:51:00 -0500 [thread overview]
Message-ID: <877koxxlt7.fsf@mendel.genehack.org> (raw)
Greetings --
We've been experiencing some strange situations on our production
machines, which look identical to the problems described in
<http://lists.insecure.org/linux-kernel/2001/Dec/1539.html>.
A follow-up to that message
(<http://lists.insecure.org/linux-kernel/2001/Dec/1604.html>) mentions
that the problem is likely to be due to a deadlock associated with the
coredump process.
The first message has some quoted text claiming that the problem went
away in 2.4.10, but the poster is seeing it in 2.4.14, and we're still
seeing it in 2.4.17-aa.
Does anybody have any idea of where to start looking, or what could
have changed in the 2.4.10 -> 2.4.14 time frame that would have
re-introduced this behavior?
We're currently kludging around the problem with 'ulimit -c 0' in
relevant environments, but it would be nice to have a real fix.
john.
--
The only skills I have the patience to learn are those that have no real
application in life. -- Calvin
reply other threads:[~2002-02-28 22:58 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=877koxxlt7.fsf@mendel.genehack.org \
--to=jacobs@genehack.org \
--cc=linux-kernel@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