All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Love <rml@tech9.net>
To: Justin A <justin@bouncybouncy.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.10/Preemt STOP bug
Date: 02 Oct 2001 21:19:07 -0400	[thread overview]
Message-ID: <1002071952.864.141.camel@phantasy> (raw)
In-Reply-To: <20011002205856.A19554@bouncybouncy.net>
In-Reply-To: <20011002205856.A19554@bouncybouncy.net>

On Tue, 2001-10-02 at 20:58, Justin A wrote:
> It seems there is a bug in 2.4.10 or the preemptable patch that causes the STOP
> signal to not work right 19 times out of 20 or so.
>
> This is most easily seen by running 'seq 1 100000' in a terminal and pressing
> control Z or using kill -STOP the proccess stops, but the parent process never
> comes back, kill -CONT has to be used in order to get the proccess back.
> 
> CPU usage my be a factor in this, yes(1) backgrounds correctly more often then
> seq does.
> 
> There are no problems with fg/CONT.

The problem is with the preemptible kernel patch...

You need to be using a recent patch, this bug was fixed awhile back in
an explicit patch (patch-rml-2.4.xx-preempt-ptrace-signal-fix-1).

It was merged into the 2.4.10 patch with revision 5, and it is in all
newer patches.

You can get patches for 2.4.10, 2.4.11-pre2, and 2.4.10-ac3 (soon -ac4)
at http://tech9.net/rml/linux

They all fix this problem.

-- 
Robert M. Love
rml at ufl.edu
rml at tech9.net


      reply	other threads:[~2001-10-03  1:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-03  0:58 2.4.10/Preemt STOP bug Justin A
2001-10-03  1:19 ` Robert Love [this message]

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=1002071952.864.141.camel@phantasy \
    --to=rml@tech9.net \
    --cc=justin@bouncybouncy.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.