* Procfs-related core dump deadlock
@ 2002-02-28 22:51 John S. J. Anderson
0 siblings, 0 replies; only message in thread
From: John S. J. Anderson @ 2002-02-28 22:51 UTC (permalink / raw)
To: linux-kernel
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2002-02-28 22:58 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-02-28 22:51 Procfs-related core dump deadlock John S. J. Anderson
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).