From: Michal Jaegermann <michal@harddata.com>
To: linux-kernel@vger.kernel.org
Subject: Re: BUG: Global FPU corruption in 2.2
Date: Tue, 24 Apr 2001 14:15:25 -0600 [thread overview]
Message-ID: <20010424141525.A1066@mail.harddata.com> (raw)
In-Reply-To: <cpx7l0g3mfk.fsf@goat.cs.wisc.edu> <20010423161148.6465.qmail@theseus.mathematik.uni-ulm.de> <9c48gv$fbk$1@penguin.transmeta.com> <20010424165632.3728.qmail@theseus.mathematik.uni-ulm.de>
In-Reply-To: <20010424165632.3728.qmail@theseus.mathematik.uni-ulm.de>; from ehrhardt@mathematik.uni-ulm.de on Tue, Apr 24, 2001 at 06:56:32PM +0200
On Tue, Apr 24, 2001 at 06:56:32PM +0200, Christian Ehrhardt wrote:
> On Tue, Apr 24, 2001 at 09:10:07AM -0700, Linus Torvalds wrote:
> > ptrace only operates on processes that are stopped. So there are no
> > locking issues - we've synchronized on a much higher level than a
> > spinlock or semaphore.
>
> This is only true for requests other than PTRACE_ATTACH and
> PTRACE_ATTACH is exactly what I'm worried about.
May I remind everybody that at the beginning of this thread I posted
another example, from an SMP Alpha, of FPU problems. It certainly
was not exactly like the one under discussion but it looked that
it had a similar "smell" to it.
It looks like that to reproduce this Alpha example one needs processors
with a rather fast clock and this hardware version is not yet very
widely available.
Michal
next prev parent reply other threads:[~2001-04-24 20:15 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-19 16:05 BUG: Global FPU corruption in 2.2 Victor Zandy
2001-04-19 20:18 ` Michal Jaegermann
2001-04-20 18:50 ` Victor Zandy
2001-04-20 19:07 ` Richard B. Johnson
2001-04-20 19:20 ` Victor Zandy
2001-04-20 19:44 ` Richard B. Johnson
2001-04-20 19:23 ` Ulrich Drepper
2001-04-20 19:37 ` Richard B. Johnson
2001-04-20 20:20 ` Victor Zandy
2001-04-20 21:44 ` Ulrich Drepper
2001-04-22 1:46 ` Richard B. Johnson
2001-04-22 2:18 ` Alan Cox
2001-04-22 2:30 ` Richard B. Johnson
2001-04-22 18:39 ` David Konerding
2001-04-22 18:59 ` Alan Cox
2001-04-22 20:59 ` kees
2001-04-23 16:11 ` Christian Ehrhardt
2001-04-24 16:10 ` Linus Torvalds
2001-04-24 16:25 ` Alan Cox
2001-04-24 16:56 ` Christian Ehrhardt
2001-04-24 20:15 ` Michal Jaegermann [this message]
2001-04-24 19:49 ` BUG: USB/Reboot Collectively Unconscious
2001-04-24 21:41 ` Alan Cox
2001-04-25 12:37 ` Collectively Unconscious
2001-04-30 22:46 ` Alan Cox
2001-04-27 12:18 ` Collectively Unconscious
2001-04-23 18:44 ` BUG: Global FPU corruption in 2.2 Erik Paulson
2001-04-24 5:33 alad
2001-04-24 7:56 alad
2001-04-24 8:56 alad
2001-04-24 13:05 Victor Zandy
2001-04-24 16:24 ` Linus Torvalds
2001-04-24 16:47 ` Christian Ehrhardt
2001-04-24 18:09 ` Victor Zandy
2001-04-24 18:21 Victor Zandy
2001-04-24 18:37 ` Alan Cox
2001-04-24 19:17 ` Victor Zandy
2001-04-24 19:51 ` Alan Cox
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=20010424141525.A1066@mail.harddata.com \
--to=michal@harddata.com \
--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 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).