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

Message-ID: <4BF50405.4070706@kernel.org>
Date:	Thu, 20 May 2010 11:42:29 +0200
From:	Tejun Heo <tj@...nel.org>
To:	Pierre Ossman <pierre-list@...man.eu>
CC:	linux-ide@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: Strange read data corruption on ext4/LVM/md

Hello,

On 05/20/2010 11:29 AM, Pierre Ossman wrote:
> The machine is rather crammed right now, with one controller in each of
> the three available pci-e slots (5 disks). I am running continuous tests
> on the disks right now though to see if the problems is on all disks or
> just some. If just one slot is causing problems then we should see some
> results there.

I see.

> When you say FIS corruption, do you mean corruption in the sense of

Oh, not FIS, FIS is the name for SATA packets.  I meant the PCI-e
packets.  How were they called... yeap TLPs.

> randomly flipped bits? I don't know if you saw the first couple of
> mails (before linux-ide was added), but the problem is data being moved
> around, not just randomly changed.

I ony saw your previous posting.  TLP corruption can happen during
command setup phase and bit flipping in the command address part is
definitely possible, so reads and writes can be headed at wrong places
in both memory and disk.  I don't know whether this would fit your
symptom tho.

> Another note is that the problem seems to worsen under load. I'm
> running the dd thing in the background, which seems to make read errors
> more common on my test files on the filesystem level.

It would be great if you can try a different controller in similar
setup.  But please keep trying to narrow down the problem and if
possible please remove filesystem from the stack and test against the
block device directly.

Thanks.

-- 
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/