linux-kernel - Re: data corruption with stex (Promise HW-Raid) driver and device-mapper

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: <201011160937.15432@Mail-Followup-To>
Date:	Tue, 16 Nov 2010 09:37:14 +0100
From:	Markus Schulz <msc@...zsystem.de>
To:	"Ed Lin - PTU" <ed.lin@...mise.com>
Cc:	"Dan Carpenter" <error27@...il.com>, linux-kernel@...r.kernel.org
Subject: Re: data corruption with stex (Promise HW-Raid) driver and device-mapper

Am Dienstag, 16. November 2010 schrieb Ed Lin - PTU:
> Hello,
> 
> We found similar problem during test.
> 
> The stex driver sets sg_tablesize as 32 (for st_yel it's 38) in the
> probe entry. It seems that this value was overridden by the system
> if using dm/lvm, for unknown reason. The driver received requests
> with more sg items than registered. Sg item number could be as high
> as 64. This is completely unexpected. The firmware could not handle
> such requests, and error occurred.
> 
> The problem can be easily reproduced using a minimum test that only
> requires copying files from system usr directory to stex dm volume
> (ext2). The stex dm volume was created using the command
> "echo 0 51200000 linear /dev/sdb1 0 | dmsetup create sdb".
> The problem should exist on every kernel since 2.6.32. The problem
> did not occur on 2.6.31 using similar minimum test.

ok, but this would not explain why all my tests with ext3 are working? 
Until now  i've found no way to generate errors on stex-disk + dm + 
ext3.
I will try your simple test now.

regards,
msc
--
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/