From: Chris Wright <chrisw@osdl.org>
To: linux-kernel@vger.kernel.org, stable@kernel.org, torvalds@osdl.org
Cc: Justin Forbes <jmforbes@linuxtx.org>,
Zwane Mwaikambo <zwane@arm.linux.org.uk>,
"Theodore Ts'o" <tytso@mit.edu>,
Randy Dunlap <rdunlap@xenotime.net>,
Chuck Wolber <chuckw@quantumlinux.com>,
akpm@osdl.org, alan@lxorguk.ukuu.org.uk,
"Kathleen Glass" <kkglass@avaya.com>,
"James E Rhodes" <jrhodes@avaya.com>,
Roland McGrath <roland@redhat.com>,
Chris Wright <chrisw@osdl.org>
Subject: [PATCH 2/7] [PATCH] NPTL signal delivery deadlock fix
Date: Fri, 26 Aug 2005 12:17:57 -0700 [thread overview]
Message-ID: <20050826191837.205011000@localhost.localdomain> (raw)
In-Reply-To: 20050826191755.052951000@localhost.localdomain
[-- Attachment #1: nptl-signal-delivery-deadlock-fix.patch --]
[-- Type: text/plain, Size: 1241 bytes --]
-stable review patch. If anyone has any objections, please let us know.
------------------
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>
Signed-off-by: Chris Wright <chrisw@osdl.org>
---
kernel/signal.c | 2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
Index: linux-2.6.12.y/kernel/signal.c
===================================================================
--- linux-2.6.12.y.orig/kernel/signal.c
+++ linux-2.6.12.y/kernel/signal.c
@@ -686,7 +686,7 @@ static void handle_stop_signal(int sig,
{
struct task_struct *t;
- if (p->flags & SIGNAL_GROUP_EXIT)
+ if (p->signal->flags & SIGNAL_GROUP_EXIT)
/*
* The process is in the middle of dying already.
*/
--
next prev parent reply other threads:[~2005-08-26 19:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-26 19:17 [PATCH 0/7] -stable review Chris Wright
2005-08-26 19:17 ` [PATCH 1/7] [IPSEC] Restrict socket policy loading to CAP_NET_ADMIN - CAN-2005-2555 Chris Wright
2005-08-26 19:17 ` Chris Wright [this message]
2005-08-26 19:17 ` [PATCH 3/7] [PATCH] Revert unnecessary zlib_inflate/inftrees.c fix Chris Wright
2005-08-26 19:17 ` [PATCH 4/7] [IPV4]: Fix DST leak in icmp_push_reply() Chris Wright
2005-08-26 19:18 ` [PATCH 5/7] [PATCH] fix gl_skb/skb type error in genelink driver in usbnet Chris Wright
2005-08-26 19:18 ` [PATCH 6/7] [PATCH] sg.c: fix a memory leak in devices seq_file implementation (2nd) Chris Wright
2005-08-27 2:19 ` James Bottomley
2005-09-25 3:50 ` Douglas Gilbert
2005-08-26 19:18 ` [PATCH 7/7] [IPV6]: Fix SKB leak in ip6_input_finish() Chris Wright
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=20050826191837.205011000@localhost.localdomain \
--to=chrisw@osdl.org \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=chuckw@quantumlinux.com \
--cc=jmforbes@linuxtx.org \
--cc=jrhodes@avaya.com \
--cc=kkglass@avaya.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=roland@redhat.com \
--cc=stable@kernel.org \
--cc=torvalds@osdl.org \
--cc=tytso@mit.edu \
--cc=zwane@arm.linux.org.uk \
/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