Revision dd12f48d4e8774415b528d3991ae47c28f26e1ac authored by Bhavesh P. Davda on 17 August 2005, 18:26:33 UTC, committed by Linus Torvalds on 17 August 2005, 19:52:04 UTC
This bug is quite subtle and only happens in a very interesting
situation where a real-time threaded process is in the middle of a
coredump when someone whacks it with a SIGKILL.  However, this deadlock
leaves the system pretty hosed and you have to reboot to recover.

Not good for real-time priority-preemption applications like our
telephony application, with 90+ real-time (SCHED_FIFO and SCHED_RR)
processes, many of them multi-threaded, interacting with each other for
high volume call processing.

Acked-by: Roland McGrath <roland@redhat.com>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
1 parent ade6648
History
File Mode Size
call.h -rw-r--r-- 8.6 KB
connection.h -rw-r--r-- 3.1 KB
krxiod.h -rw-r--r-- 1.1 KB
krxsecd.h -rw-r--r-- 773 bytes
krxtimod.h -rw-r--r-- 1.3 KB
message.h -rw-r--r-- 2.3 KB
packet.h -rw-r--r-- 5.0 KB
peer.h -rw-r--r-- 2.9 KB
rxrpc.h -rw-r--r-- 861 bytes
transport.h -rw-r--r-- 3.7 KB
types.h -rw-r--r-- 1.3 KB

back to top