linux-kernel - Re: Strange write errors on FAT32 partition (maybe an FAT32 bug?!)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <45539366.7070809@scientia.net>
Date:	Thu, 09 Nov 2006 21:45:26 +0100
From:	Christoph Anton Mitterer <calestyo@...entia.net>
To:	Roger Heflin <rheflin@...pa.com>
CC:	linux-kernel@...r.kernel.org
Subject: Re: Strange write errors on FAT32 partition (maybe an FAT32 bug?!)

Roger Heflin wrote:
> Christoph,
>
> Install then edac_mc module, and make sure  through the
> sysctl command that pci parity checking is enabled.
>
> I have seen pci parity errors produce this sort of results,
> ie make 100 identical 50MB files, and cksum them and one
> will be wrong, do it a again, and the "wrong" one is now
> right, but someone else is "wrong".
Ah thx,... is it in the vanilla kernel?
And do you know of any possible results that this issue has? When I just
read data (see my original stuff with fat32) is it possible that this
had been modified or damaged?
Or are the only consequences that diff errors occur?

And what is responsible for that parity errors? Is it possible that any
hardware is damaged?

Thanks,
Chris.

View attachment "calestyo.vcf" of type "text/x-vcard" (156 bytes)