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:	Mon, 29 Nov 2010 11:35:37 -0800
From:	"Ed Lin - PTU" <ed.lin@...mise.com>
To:	"Milan Broz" <mbroz@...hat.com>
Cc:	"Dan Carpenter" <error27@...il.com>,
	"Markus Schulz" <msc@...zsystem.de>,
	<linux-kernel@...r.kernel.org>,
	"device-mapper development" <dm-devel@...hat.com>
Subject: RE: data corruption with stex (Promise HW-Raid) driver and device-mapper



>-----Original Message-----
>From: Milan Broz [mailto:mbroz@...hat.com] 
>Sent: 2010年11月25日 1:57
>To: Ed Lin - PTU
>Cc: Dan Carpenter; Markus Schulz; 
>linux-kernel@...r.kernel.org; device-mapper development
>Subject: Re: data corruption with stex (Promise HW-Raid) 
>driver and device-mapper
>
>
>On 11/16/2010 02:35 AM, Ed Lin - PTU wrote:
>> 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.
>
>Device-mapper respects hw restrictions, so it must be bug somewhere.
>
>Please cc dm-devel if you think that problem is there.
>

Hello,

This problem is fixed. Martin Petersen proposed a thorough cleaning at
http://marc.info/?l=dm-devel&m=129070330506836&w=2 .
My original patch is at
http://marc.info/?l=dm-devel&m=129067980708110&w=2 ,
which is a simplified minimum version.

Thanks,
Ed Lin
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ