Re: [PATCH 0/2] patches addresses problem with memory corruption

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, 31 Jan 2011 16:25:08 +0100 Adam Kwolek <adam.kwolek@xxxxxxxxx> wrote:

> When for raid0 metadata is updated outside mdmon it can happen that
> memory corruption occurs due to too amount of memory is allocated 
> for imsm device structure.
> 
> 1. imsm: FIX: mdmon crash during 2 raid0 arrays expansion
>   this patch is almost the same to sent earlier except 2 changes:
>    a) compilation problem
>    b) size should affect anchor size also
>       (added calculation changes extends space_needed variable also
>        this variable is used for anchor allocation)
>   so it replaces previous one.
> 2.  imsm: FIX: sizeof_imsm_dev() can return too small value
> 	size returned by sizeof_imsm_dev() describes minimum size of device
>         This is correct when both device maps has the same length
>         When device expands or shrinks we should return size that allows
>         for storing larger device information to avoid memory corruption.
> 

Both applied (replacing the previous one)..

Thanks.

NeilBrown


> BR
> Adam
> 
> ---
> 
> Adam Kwolek (2):
>       imsm: FIX: sizeof_imsm_dev() can return too small value
>       imsm: FIX: mdmon crash during 2 raid0 arrays expansion
> 
> 
>  super-intel.c |   20 +++++++++++++++-----
>  1 files changed, 15 insertions(+), 5 deletions(-)
> 

--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux