linux-kernel - Re: dm stripe: Fix bounds

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]

Date:	Thu, 12 Oct 2006 11:31:28 -0400
From:	Phillip Susi <psusi@....rr.com>
To:	Alasdair G Kergon <agk@...hat.com>,
	Phillip Susi <psusi@....rr.com>, Andrew Morton <akpm@...l.org>,
	linux-kernel@...r.kernel.org,
	Heinz Mauelshagen <mauelshagen@...hat.com>
Subject: Re: dm stripe: Fix bounds

Define 'handle it correctly'?  The correct thing to do is for dm to 
accept the values and work properly.  dmraid only passes the parameters 
to dm from the on disk data structure created by the bios.

Alasdair G Kergon wrote:
> On Thu, Oct 12, 2006 at 12:01:21AM -0400, Phillip Susi wrote:
>> now dmraid fails to configure the dm 
>> table because this patch rejects it.
>  
>> I believe the correct thing to do is to special case the last stripe in 
>> 0-31    64-67
>> 32-63   68-71
>  
> AFAIK current versions of dmraid handle this correctly - Heinz?
> 
> Alasdair

-
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/