From: Paul Mackerras <paulus@linuxcare.com.au>
To: tom_gall@vnet.ibm.com
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: 2.4.0-test1 linux/sched.h
Date: Mon, 19 Jun 2000 12:26:14 +1000 (EST) [thread overview]
Message-ID: <14669.33990.581970.248299@argo.linuxcare.com.au> (raw)
In-Reply-To: <39478BE8.3B6E6157@vnet.ibm.com>
tom_gall@vnet.ibm.com writes:
> Anyone notice that on
>
> 2.4.0-test1-ac18 that sched.h was changed to remove
>
> #define PF_PTRACED 0x00000010
> #define PF_TRACESYS 0x00000020
Yes, this was part of a fix for a race condition in accessing the
tsk->flags field. Initially only ix86 was updated with the necessary
changes but I have since sent in a patch to Alan and it should be
fixed in the latest -ac version.
Paul.
--
Paul Mackerras, Senior Open Source Researcher, Linuxcare, Inc.
+61 2 6262 8990 tel, +61 2 6262 8991 fax
paulus@linuxcare.com.au, http://www.linuxcare.com.au/
Linuxcare. Support for the revolution.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2000-06-19 2:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-14 13:43 2.4.0-test1 linux/sched.h tom_gall
2000-06-19 2:26 ` Paul Mackerras [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=14669.33990.581970.248299@argo.linuxcare.com.au \
--to=paulus@linuxcare.com.au \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=tom_gall@vnet.ibm.com \
/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;
as well as URLs for NNTP newsgroup(s).