Following are three patches that fixes bugs in raid5 that could conceivable cause data corruption (1 and 3) or and oops (2). Bugs 1 and 3 can cause a 'resync' to mistakenly think the partiy block is correct when infact it isn't (it looks at a parity block that was generated rather than read from disk). If this happens to leave a parity block wrong, and a device then fails, data regenerated based on that parity block will be wrong. Once a patched kernel is installed, running a repair pass (echo repair > .../sync_action) will fix any incorrect parity. The Oops (patch 2) can only happen if you right to a partucular sysfs file that only root has access to and only developer (currently) have any reason to write to. NeilBrown [PATCH 001 of 3] md: md: fix prexor vs sync_request race [PATCH 002 of 3] md: fix uninitialized use of mddev->recovery_wait [PATCH 003 of 3] md: Do not compute parity unless it is on a failed drive -- 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
