mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@osdl.org>
To: "Bhavesh P. Davda" <bhavesh@avaya.com>
Cc: linux-kernel@vger.kernel.org, torvalds@osdl.org, "Glass,
	Kathleen K (Kathy)" <kkglass@avaya.com>,
	"Rhodes, James E (James)" <jrhodes@avaya.com>,
	Roland McGrath <roland@redhat.com>
Subject: Re: [PATCH 2.6.12.5] NPTL signal delivery deadlock fix
Date: Wed, 17 Aug 2005 12:00:20 -0700	[thread overview]
Message-ID: <20050817190020.GO7991@shell0.pdx.osdl.net> (raw)
In-Reply-To: <1124303193.11458.16.camel@cof110earth.dr.avaya.com>

* Bhavesh P. Davda (bhavesh@avaya.com) wrote:
> 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.

Nice catch, also looks like something for -stable series.  Roland, any
issue with this patch?

thanks,
-chris

> diff -Naur linux-2.6.12.5/kernel/signal.c linux-2.6.12.5-sigfix/kernel/signal.c
> --- linux-2.6.12.5/kernel/signal.c	2005-08-14 18:20:18.000000000 -0600
> +++ linux-2.6.12.5-sigfix/kernel/signal.c	2005-08-17 11:36:20.547600092 -0600
> @@ -686,7 +686,7 @@
>  {
>  	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.
>  		 */

  reply	other threads:[~2005-08-17 19:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-17 18:26 Bhavesh P. Davda
2005-08-17 19:00 ` Chris Wright [this message]
2005-08-17 19:18   ` Roland McGrath

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=20050817190020.GO7991@shell0.pdx.osdl.net \
    --to=chrisw@osdl.org \
    --cc=bhavesh@avaya.com \
    --cc=jrhodes@avaya.com \
    --cc=kkglass@avaya.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roland@redhat.com \
    --cc=torvalds@osdl.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

all inboxes | Powered by JetHome®