kernel/git/stable/linux-stable.git/drivers/md/md.c, branch linux-2.6.30.y

md: Handle growth of v1.x metadata correctly.

2009-08-16T21:18:57+00:00

commit 70471dafe3390243c598a3165dfb86b8b8b3f4fe upstream. The v1.x metadata does not have a fixed size and can grow when devices are added. If it grows enough to require an extra sector of storage, we need to update the 'sb_size' to match. Without this, md can write out an incomplete superblock with a bad checksum, which will be rejected when trying to re-assemble the array. Signed-off-by: NeilBrown Signed-off-by: Greg Kroah-Hartman

md: when a level change reduces the number of devices, remove the excess.

2009-08-16T21:18:46+00:00

commit 3a981b03f38dc3b8a69b77cbc679e66c1318a44a upstream. When an array is changed from RAID6 to RAID5, fewer drives are needed. So any device that is made superfluous by the level conversion must be marked as not-active. For the RAID6->RAID5 conversion, this will be a drive which only has 'Q' blocks on it. Signed-off-by: NeilBrown Signed-off-by: Greg Kroah-Hartman

md: avoid dereferencing NULL pointer when accessing suspend_* sysfs attributes.

2009-07-20T03:38:53+00:00

commit b8d966efd9a46a9a35beac50cbff6e30565125ef upstream. If we try to modify one of the md/ sysfs files suspend_lo or suspend_hi when the array is not active, we dereference a NULL. Protect against that. Signed-off-by: NeilBrown Signed-off-by: Greg Kroah-Hartman

md: fix error path when duplicate name is found on md device creation.

2009-07-20T03:38:53+00:00

commit 1ec22eb2b4a2e1a763106bce36b11c02eaa84e61 upstream. When an md device is created by name (rather than number) we need to check that the name is not already in use. If this check finds a duplicate, we return an error without dropping the lock or freeing the newly create mddev. This patch fixes that. Found-by: Jiri Slaby Signed-off-by: NeilBrown Signed-off-by: Greg Kroah-Hartman

md: don't use locked_ioctl.

2009-05-26T02:57:36+00:00

md has no need for the BKL - it does its own locking. So md_ioctl doesn't need to be a locked_ioctl. Signed-off-by: NeilBrown

md: don't update curr_resync_completed without also updating reshape_position.

2009-05-26T02:57:21+00:00

In order for the metadata to always be consistent, we mustn't updated curr_resync_completed without also updating reshape_position. The reshape code updates both at the same time. However since commit 97e4f42d62badb0f9fbc27c013e89bc1336a03bc the common md_do_sync will sometimes update curr_resync_completed but is not in a position to update reshape_position. So if MD_RECOVERY_RESHAPE is set (indicating that a reshape is happening, so reshape_position might change), don't update curr_resync_completed in md_do_sync, leave it to the per-personality reshape code. Signed-off-by: NeilBrown

md: export 'frozen' resync state through sysfs

2009-05-25T23:41:17+00:00

The md resync engine has a 'frozen' state which ensures that no resync/recovery. This is used to avoid races. Export this state through the 'sync_action' sysfs attribute so that user-space can benefit and also avoid some races. Signed-off-by: NeilBrown

md: improve errno return when setting array_size

2009-05-25T23:41:17+00:00

Instead of always returns EINVAL if anything goes wrong when setting the array size, add the option of E2BIG if the size requested is too large. This makes it easier for user-space to be sure what went wrong. Signed-off-by: NeilBrown

md: always update level / chunk_size / layout when writing v1.x metadata.

2009-05-25T23:40:59+00:00

We previously didn't update these fields when writing the metadata because they could never change. They can now, so we better write them. v0.90 metadata always updated these fields. Signed-off-by: NeilBrown

md: remove rd%d links immediately after stopping an array.

2009-05-07T02:51:06+00:00

md maintains link in sys/mdXX/md/ to identify which device has which role in the array. e.g. rd2 -> dev-sda indicates that the device with role '2' in the array is sda. These links are only present when the array is active. They are created immediately after ->run is called, and so should be removed immediately after ->stop is called. However they are currently removed a little bit later, and it is possible for ->run to be called again, thus adding these links, before they are removed. So move the removal earlier so they are consistently only present when the array is active. Signed-off-by: NeilBrown