linux-kernel - Re: Strange read data corruption on ext4/LVM/md

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-prev] [day] [month] [year] [list]

Date:	Sun, 16 Jan 2011 15:01:54 +0100
From:	Pierre Ossman <pierre-list@...man.eu>
To:	linux-ide@...r.kernel.org
Cc:	Tejun Heo <tj@...nel.org>, linux-kernel@...r.kernel.org
Subject: Re: Strange read data corruption on ext4/LVM/md

On Thu, 15 Jul 2010 21:38:01 +0200
Pierre Ossman <pierre-list@...man.eu> wrote:

> 
> Status update:
> 
> 1. Putting the other sil3132 controller did not make any problems
> appear.
> 
> 2. Next I swapped that controller with the one next to it to test if
> this specific board design in combination with this specific slot was
> causing the issues. Still no corruption.
> 
> 3. Today I put the "bad" controller back in, but in a different slot.
> Still not seeing any issues.
> 
> I could move it back to the inital slot to see if the problem
> reappears, but I'm just happy the system is error free again so I'll
> write this off as a temporary glitch or a bad combination of card and
> slot.
> 

Time for an update to this somewhat old thread. The problem has
remained, but being so very rare that I cannot reproduce it often
enough for systematic testing. Both motherboard and the "bad"
controller have been swapped out with different (but identical) cards.

These days there are some controller cards based on Marvell's 88SE9128,
which seems to be a decent chip. So the next step is chucking all the
sil3132 stuff in favour of those...

Rgds
-- 
     -- Pierre Ossman

  WARNING: This correspondence is being monitored by FRA, a
  Swedish intelligence agency. Make sure your server uses
  encryption for SMTP traffic and consider using PGP for
  end-to-end encryption.

Download attachment "signature.asc" of type "application/pgp-signature" (231 bytes)