From: Jan Niehusmann <jan@gondor.com>
To: Steffen Persvold <sp@scali.no>
Cc: Petr Vandrovec <vandrove@vc.cvut.cz>,
linux-kernel@vger.kernel.org, VDA@port.imtp.ilyichevsk.odessa.ua,
alan@lxorguk.ukuu.org.uk
Subject: Re: Athlon: Try this (was: Re: Athlon bug stomping #2)
Date: Sun, 16 Sep 2001 10:08:34 +0200 [thread overview]
Message-ID: <20010916100834.A590@gondor.com> (raw)
In-Reply-To: <1292125035.20010914214303@port.imtp.ilyichevsk.odessa.ua> <E15i2Bp-00017m-00@the-village.bc.nu> <20010916035207.C7542@ppc.vc.cvut.cz> <3BA4530D.A3378F41@scali.no>
In-Reply-To: <3BA4530D.A3378F41@scali.no>
On Sun, Sep 16, 2001 at 09:21:49AM +0200, Steffen Persvold wrote:
> I also have a question; if "movntq; sfence" type of memory copy can cause data
> corruption in kernel space, it can in theory also do so in user space right ?
> So, if I'm right this bug could also be on machines running a 2.2 kernel with
> userspace programs using 3DNow (or SSE even) instructions.
Sure. I did crash a computer running an old kernel (not 2.2 but
2.4.0-testX without the optimised fast_copy_page) from a non-privileged
user space program containing the same code as the optimised fast_copy_page.
Jan
next prev parent reply other threads:[~2001-09-16 8:08 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <372BFCD7961@vcnet.vc.cvut.cz>
2001-09-14 18:43 ` Athlon: Try this (was: Re: Athlon bug stomping #2) VDA
2001-09-14 23:16 ` Alan Cox
2001-09-15 17:44 ` Nicholas Knight
2001-09-15 18:02 ` Jonathan Morton
2001-09-15 23:23 ` Alan Cox
2001-09-16 1:52 ` Petr Vandrovec
2001-09-16 7:21 ` Steffen Persvold
2001-09-16 8:08 ` Jan Niehusmann [this message]
2001-09-19 3:47 ` Albert D. Cahalan
2001-09-16 11:02 ` Vojtech Pavlik
2001-09-16 13:53 ` Alan Cox
2001-09-16 13:50 ` Vojtech Pavlik
2001-09-16 14:47 ` Alan Cox
2001-09-16 17:01 ` Vojtech Pavlik
2001-09-16 16:52 ` Roberto Jung Drebes
2001-09-17 0:58 ` Petr Vandrovec
2001-09-17 1:37 ` Ignacio Vazquez-Abrams
2001-09-17 14:59 ` Jonathan Morton
2001-09-18 11:27 ` jury gerold
2001-09-20 23:38 ` bill davidsen
2001-09-14 7:34 Athlon bug stomping #2 Roberto Jung Drebes
2001-09-14 8:27 ` Athlon: Try this (was: Re: Athlon bug stomping #2) Roberto Jung Drebes
2001-09-14 9:26 ` Jeff Lightfoot
2001-09-14 18:19 ` Byron Stanoszek
2001-09-15 18:00 ` Liakakis Kostas
2001-09-15 20:28 ` VDA
2001-09-15 7:15 ` brian
2001-09-19 1:30 ` brian
2001-09-16 21:53 ` Carsten Leonhardt
2001-09-19 3:55 ` Dan Hollis
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=20010916100834.A590@gondor.com \
--to=jan@gondor.com \
--cc=VDA@port.imtp.ilyichevsk.odessa.ua \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=sp@scali.no \
--cc=vandrove@vc.cvut.cz \
/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.