From: David Mosberger <davidm@hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] patch ia32 mode [Threads don't wake up in ia32 mode]
Date: Tue, 31 Jul 2001 01:28:38 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590693005963@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590693005927@msgid-missing>
This patch looks correct to me, so I applied. Don, speak up if you
object...
--david
>>>>> On Thu, 26 Jul 2001 19:34:47 +0200, "Jose Luu" <jluu@mainsoft.com> said:
Jose> This is the solution to the problem I described in june,
Jose> see test case there:
Jose> https://external-lists.valinux.com/archives//linux-ia64/2001-June/001792.htm
Jose> l
Jose> There was an oversight on the size of the long, which caused
Jose> an improper restoration of the real time signals blocking mask
Jose> of the 32 bit frame, 2 of these signals are used by the
Jose> pthreads library for wakeup or cancellation.
Jose> This patch can be applied to all 2.4.x series kernels
Jose> including 2.4.7, since the file has not changed.
Jose> Jose
Jose> --- 2.4.5/arch/ia64/ia32/ia32_signal.c Tue Oct 10 02:54:53
Jose> 2000 +++ new-2.4.5/arch/ia64/ia32/ia32_signal.c Thu Jul 26
Jose> 12:49:42 2001 @@ -279,7 +279,7 @@ err | Jose> setup_sigcontext_ia32(&frame->sc, &frame->fpstate, regs,
set-> sig[0]);
Jose> if (_IA32_NSIG_WORDS > 1) { - err | Jose> __copy_to_user(frame->extramask, &set->sig[1], + err | Jose> __copy_to_user(frame->extramask,(((char *) &set->sig) + 4) ,
Jose> sizeof(frame->extramask)); }
Jose> _______________________________________________ Linux-IA64
Jose> mailing list Linux-IA64@linuxia64.org
Jose> http://lists.linuxia64.org/lists/listinfo/linux-ia64
prev parent reply other threads:[~2001-07-31 1:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-26 17:34 [Linux-ia64] patch ia32 mode [Threads don't wake up in ia32 mode] Jose Luu
2001-07-31 1:28 ` David Mosberger [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=marc-linux-ia64-105590693005963@msgid-missing \
--to=davidm@hpl.hp.com \
--cc=linux-ia64@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.