mirror of
https://github.com/edk2-porting/linux-next.git
synced 2024-12-24 13:13:57 +08:00
e93f68a1fc
Most array level changes leave the list of devices largely unchanged, possibly causing one at the end to become redundant. However conversions between RAID0 and RAID10 need to renumber all devices (except 0). This renumbering is currently being done in the ->run method when the new personality takes over. However this is too late as the common code in md.c might already have invalidated some of the devices if they had a ->raid_disk number that appeared to high. Moving it into the ->takeover method is too early as the array is still active at that time and wrong ->raid_disk numbers could cause confusion. So add a ->new_raid_disk field to mdk_rdev_s and use it to communicate the new raid_disk number. Now the common code knows exactly which devices need to be renumbered, and which can be invalidated, and can do it all at a convenient time when the array is suspend. It can also update some symlinks in sysfs which previously were not be updated correctly. Reported-by: Maciej Trela <maciej.trela@intel.com> Signed-off-by: NeilBrown <neilb@suse.de>
21 lines
455 B
C
21 lines
455 B
C
#ifndef _RAID0_H
|
|
#define _RAID0_H
|
|
|
|
struct strip_zone
|
|
{
|
|
sector_t zone_end; /* Start of the next zone (in sectors) */
|
|
sector_t dev_start; /* Zone offset in real dev (in sectors) */
|
|
int nb_dev; /* # of devices attached to the zone */
|
|
};
|
|
|
|
struct raid0_private_data
|
|
{
|
|
struct strip_zone *strip_zone;
|
|
mdk_rdev_t **devlist; /* lists of rdevs, pointed to by strip_zone->dev */
|
|
int nr_strip_zones;
|
|
};
|
|
|
|
typedef struct raid0_private_data raid0_conf_t;
|
|
|
|
#endif
|