Prev: Staging: otus: fix coding style issues in ioctl.c
Next: linux-next: Tree for June 28
From: Neil Brown on 28 Jun 2010 00:10

Hi Linus,
Please consider pulling the following changes for 2.6.35.
They are:

- fixes for regressions introduced in -rc1 (Restore partition....)
- fixes for enhancements added in -rc1 which were not yet perfect
(mostly relating to 'takeover' of one level by another)
- fixes for bugs of longer standing.
One of these was poor handling of multiple device failure when converting
a RAID5 to a RAID6 with several more devices. This bug exposed
several issues and covers the "md/raid5:*" patches.

Thanks,
NeilBrown



The following changes since commit 7e27d6e778cd87b6f2415515d7127eba53fe5d02:

Linux 2.6.35-rc3 (2010-06-11 19:14:04 -0700)

are available in the git repository at:
git://neil.brown.name/md/ for-linus

Maciej Trela (3):
md: fix raid10 takeover: use new_layout for setup_conf
md: clear layout after ->raid0 takeover
md: enable raid4->raid0 takeover

NeilBrown (8):
Restore partition detection of newly created md arrays.
md: fix handling of array level takeover that re-arranges devices.
md/raid5: avoid oops when number of devices is reduced then increased.
md: Don't update ->recovery_offset when reshaping an array to fewer devices.
md/raid5: More careful check for "has array failed".
md/raid5: Allow recovered part of partially recovered devices to be in-sync
md/raid5: add a missing 'continue' in a loop.
md/raid5: don't include 'spare' drives when reshaping to fewer devices.

Prasanna S. Panchamukhi (1):
md: raid10: Fix null pointer dereference in fix_read_error()

drivers/md/md.c | 38 +++++++++++--
drivers/md/md.h | 3 +
drivers/md/raid0.c | 21 ++++----
drivers/md/raid0.h | 3 -
drivers/md/raid10.c | 46 ++++++----------
drivers/md/raid10.h | 5 --
drivers/md/raid5.c | 150 +++++++++++++++++++++++++++++++++++++++++----------
7 files changed, 187 insertions(+), 79 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 | 
Pages: 1
Prev: Staging: otus: fix coding style issues in ioctl.c
Next: linux-next: Tree for June 28