From: Florian Lohoff <flo@rfc822.org>
To: Ralf Baechle <ralf@oss.sgi.com>
Cc: linux-mips@oss.sgi.com
Subject: atomic.h changes fixed bug Was: CVS Update@oss.sgi.com: linux
Date: Sun, 29 Oct 2000 17:25:17 +0100 [thread overview]
Message-ID: <20001029172517.C2663@paradigm.rfc822.org> (raw)
In-Reply-To: <20001026235921Z553785-493+346@oss.sgi.com>; from ralf@oss.sgi.com on Thu, Oct 26, 2000 at 04:59:17PM -0700
On Thu, Oct 26, 2000 at 04:59:17PM -0700, Ralf Baechle wrote:
> CVSROOT: /home/pub/cvs
> Module name: linux
> Changes by: ralf@oss.sgi.com 00/10/26 16:59:17
>
> Modified files:
> include/asm-mips: atomic.h
> include/asm-mips64: atomic.h
>
> Log message:
> Add memory clobbers to the atomic_*_return functions. I hope this
> fixes the file corruption / `D' state processes people observe.
This at least fixes the file corruption stuff i have been seeing
(Never The Same Checksum aka NTSC)
remake:/home/flo# md5sum xfree86_4.0.1.orig.tar.gz
590767187e145407bcda582facf5afc0 xfree86_4.0.1.orig.tar.gz
remake:/home/flo# md5sum xfree86_4.0.1.orig.tar.gz
590767187e145407bcda582facf5afc0 xfree86_4.0.1.orig.tar.gz
remake:/home/flo# md5sum xfree86_4.0.1.orig.tar.gz
590767187e145407bcda582facf5afc0 xfree86_4.0.1.orig.tar.gz
remake:/home/flo# md5sum xfree86_4.0.1.orig.tar.gz
590767187e145407bcda582facf5afc0 xfree86_4.0.1.orig.tar.gz
remake:/home/flo# md5sum xfree86_4.0.1.orig.tar.gz
590767187e145407bcda582facf5afc0 xfree86_4.0.1.orig.tar.gz
Flo
--
Florian Lohoff flo@rfc822.org +49-5201-669912
Why is it called "common sense" when nobody seems to have any?
next parent reply other threads:[~2000-10-29 16:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20001026235921Z553785-493+346@oss.sgi.com>
2000-10-29 16:25 ` Florian Lohoff [this message]
2000-10-29 16:47 ` atomic.h changes fixed bug Was: CVS Update@oss.sgi.com: linux Florian Lohoff
2000-10-30 1:17 ` Ralf Baechle
2000-10-30 6:35 ` Klaus Naumann
2000-10-30 21:14 ` Ralf Baechle
2000-10-30 10:39 ` Florian Lohoff
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=20001029172517.C2663@paradigm.rfc822.org \
--to=flo@rfc822.org \
--cc=linux-mips@oss.sgi.com \
--cc=ralf@oss.sgi.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