• NeilBrown's avatar
    md/raid0: update queue parameter in a safer location. · 199dc6ed
    NeilBrown authored
    When a (e.g.) RAID5 array is reshaped to RAID0, the updating
    of queue parameters (e.g. max number of sectors per bio) is
    done in the wrong place.
    It should be part of ->run, but it is actually part of ->takeover.
    This means it happens before level_store() calls:
    
    	blk_set_stacking_limits(&mddev->queue->limits);
    
    and so it ineffective.  This can lead to errors from underlying
    devices.
    
    So move all the relevant settings out of create_stripe_zones()
    and into raid0_run().
    
    As this can lead to a bug-on it is suitable for any -stable
    kernel which supports reshape to RAID0.  So 2.6.35 or later.
    As the bug has been present for five years there is no urgency,
    so no need to rush into -stable.
    
    Fixes: 9af204cf ("md: Add support for Raid5->Raid0 and Raid10->Raid0 takeover")
    Cc: stable@vger.kernel.org (v2.6.35+ - please delay until after -final release).
    Reported-by: default avatarYi Zhang <yizhan@redhat.com>
    Signed-off-by: default avatarNeilBrown <neilb@suse.com>
    199dc6ed
raid0.c 19.9 KB