From: Rik van Riel <riel@nl.linux.org>
To: Patrick Mau <patrick@oscar.prima.de>
Cc: Linux Kernel <linux-kernel@vger.rutgers.edu>,
Linux MM <linux-mm@kvack.org>
Subject: Re: 2.3.42: Strange memory corruption
Date: Wed, 2 Feb 2000 14:41:02 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.10.10002021439170.462-100000@mirkwood.dummy.home> (raw)
In-Reply-To: <20000202051433.A298@tony.dorf.wh.uni-dortmund.de>
On Wed, 2 Feb 2000, Patrick Mau wrote:
> I have a really strange memory corruption problem with
> 2.3.42. My system configuration is as follows:
> After a few md5sums I get different checksums.
> Now I check the file with bzip2 and get a CRC error.
>
> Now I make a copy (plain 'cp') of that file.
>
> Then I repeat the above with the copy and get different
> checksums and also CRC errors from bzip2. (I expected that).
>
> --> Here comes the strange part <---
>
> Now I reboot into 2.3.30. Same config.
> And BOTH files, even the 'corrupt' copy, are
> correct. I can run the md5sum test AND can uncompress
> BOTH of them. I can always reproduce that.
This looks a bit like there might be a race with the
pagetable mapping or read()ing of the file. It would
explain the three `suspicious' segfaults I've seen in
the last few days...
regards,
Rik
--
The Internet is not a network of computers. It is a network
of people. That is its real strength.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/
next parent reply other threads:[~2000-02-02 13:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20000202051433.A298@tony.dorf.wh.uni-dortmund.de>
2000-02-02 13:41 ` Rik van Riel [this message]
2000-02-02 17:43 ` Manfred Spraul
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=Pine.LNX.4.10.10002021439170.462-100000@mirkwood.dummy.home \
--to=riel@nl.linux.org \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
--cc=patrick@oscar.prima.de \
/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