linux.git/drivers/md, branch v3.4-rc2

md/raid1,raid10: don't compare excess byte during consistency check.

2012-04-03T05:39:23+00:00

When comparing two pages read from different legs of a mirror, only
compare the bytes that were read, not the whole page.

In most cases we read a whole page, but in some cases with
bad blocks or odd sizes devices we might read fewer than that.

This bug has been present "forever" but at worst it might cause
a report of two many mismatches and generate a little bit
extra resync IO, so there is no need to back-port to -stable
kernels.

Reported-by: majianpeng 
Signed-off-by: NeilBrown

md/raid5: Fix a bug about judging if the operation is syncing or replacing

2012-04-03T05:37:38+00:00

When create a raid5 using assume-clean and echo check or repair to
sync_action.Then component disks did not operated IO but the raid
check/resync faster than normal.
Because the judgement in function analyse_stripe():
		if (do_recovery ||
		    sh->sector >= conf->mddev->recovery_cp)
			s->syncing = 1;
		else
			s->replacing = 1;
When check or repair,the recovery_cp == MaxSectore,so syncing equal zero
not one.

This bug was introduced by commit 9a3e1101b827
    md/raid5:  detect and handle replacements during recovery.
so this patch is suitable for 3.3-stable.

Cc: stable@vger.kernel.org
Signed-off-by: majianpeng 
Signed-off-by: NeilBrown

md/raid1:Remove unnecessary rcu_dereference(conf->mirrors[i].rdev).

2012-04-03T05:37:33+00:00

Because rde->nr_pending > 0,so can not remove this disk.
And in any case, we aren't holding rcu_read_lock()

Signed-off-by: majianpeng 
Signed-off-by: NeilBrown

md: Avoid OOPS when reshaping raid1 to raid0

2012-04-03T05:37:26+00:00

raid1 arrays do not have the notion of chunk size. Calculate the
largest chunk sector size we can use to avoid a divide by zero OOPS
when aligning the size of the new array to the chunk size.

Signed-off-by: Jes Sorensen 
Signed-off-by: NeilBrown

md/raid5: fix handling of bad blocks during recovery.

2012-04-03T05:36:17+00:00

1/ We can only treat a known-bad-block like a read-error if we
   have the data that belongs in that block.  So fix that test.

2/ If we cannot recovery a stripe due to insufficient data,
   don't tell "md_done_sync" that the sync failed unless we really
   did fail something.  If we successfully record bad blocks,
   that is success.

Reported-by: "majianpeng" 
Signed-off-by: NeilBrown

md/raid1: If md_integrity_register() failed,run() must free the mem

2012-04-01T23:48:38+00:00

Signed-off-by: majianpeng 
Signed-off-by: NeilBrown

md/raid0: If md_integrity_register() fails, raid0_run() must free the mem.

2012-04-01T23:48:37+00:00

Signed-off-by: majianpeng 
Signed-off-by: NeilBrown

md/linear: If md_integrity_register() fails, linear_run() must free the mem.

2012-04-01T23:48:37+00:00

Signed-off-by: majianpeng 
Signed-off-by: NeilBrown

dm: add verity target

2012-03-28T17:43:38+00:00

This device-mapper target creates a read-only device that transparently
validates the data on one underlying device against a pre-generated tree
of cryptographic checksums stored on a second device.

Two checksum device formats are supported: version 0 which is already
shipping in Chromium OS and version 1 which incorporates some
improvements.

Signed-off-by: Mikulas Patocka 
Signed-off-by: Mandeep Singh Baines 
Signed-off-by: Will Drewry 
Signed-off-by: Elly Jones 
Cc: Milan Broz 
Cc: Olof Johansson 
Cc: Steffen Klassert 
Cc: Andrew Morton 
Signed-off-by: Alasdair G Kergon

dm bufio: prefetch

2012-03-28T17:41:29+00:00

This patch introduces a new function dm_bufio_prefetch. It prefetches
the specified range of blocks into dm-bufio cache without waiting
for i/o completion.

Signed-off-by: Mikulas Patocka 
Signed-off-by: Alasdair G Kergon