linux-toradex.git/drivers/md, branch tegra

Merge branch 'linux-3.1.y' into android-tegra-nv-3.1

2012-01-24T11:35:20+00:00

Linux 3.1.10

Change-Id: I465d184c492e8041dd0cd90f2cb70fde17ba7118
Signed-off-by: Varun Wadekar

md/raid1: perform bad-block tests for WriteMostly devices too.

2012-01-18T15:31:57+00:00

commit 307729c8bc5b5a41361af8af95906eee7552acb1 upstream.

We normally try to avoid reading from write-mostly devices, but when
we do we really have to check for bad blocks and be sure not to
try reading them.

With the current code, best_good_sectors might not get set and that
causes zero-length read requests to be send down which is very
confusing.

This bug was introduced in commit d2eb35acfdccbe2 and so the patch
is suitable for 3.1.x and 3.2.x

Reported-and-tested-by: Michał Mirosław 
Reported-and-tested-by: Art -kwaak- van Breemen 
Signed-off-by: NeilBrown 
Signed-off-by: Greg Kroah-Hartman

Revert "dm crypt: scale to multiple cpus"

2012-01-06T12:35:43+00:00

This reverts commit c029772125594e31eb1a5ad9e0913724ed9891f2.

Change-Id: Id9ad9be437cd79db20362e1cc4b81b7380ee7f3d
Reviewed-on: http://git-master/r/72237
Reviewed-by: Automatic_Commit_Validation_User
Reviewed-by: Mallikarjun Kasoju 
Tested-by: Mallikarjun Kasoju 
Tested-by: Ahung Cheng 
Reviewed-by: Venkat Moganty

Revert "dm crypt: use io thread for reads only if mempool exhausted"

2012-01-06T12:35:06+00:00

This reverts commit 20c82538e4f5ede51bc2b4795bc6e5cae772796d.

Conflicts:

	drivers/md/dm-crypt.c

Change-Id: Id6c1f774c735836652c07ee279fb81093e732372
Reviewed-on: http://git-master/r/72236
Reviewed-by: Automatic_Commit_Validation_User
Reviewed-by: Mallikarjun Kasoju 
Tested-by: Mallikarjun Kasoju 
Tested-by: Ahung Cheng 
Reviewed-by: Venkat Moganty

Revert "dm crypt: add post iv call to iv generator"

2012-01-06T12:34:47+00:00

This reverts commit 2dc5327d3acb3340ab6fa3981401b076b78a51f4.

Change-Id: I58ed3f6e8f9d053cb2ae9cfb0ae57528055a902b
Reviewed-on: http://git-master/r/72235
Reviewed-by: Automatic_Commit_Validation_User
Reviewed-by: Mallikarjun Kasoju 
Tested-by: Mallikarjun Kasoju 
Tested-by: Ahung Cheng 
Reviewed-by: Venkat Moganty

Revert "dm crypt: add multi key capability"

2012-01-06T12:33:39+00:00

This reverts commit d1f9642381847e2b94caa34c3533211cf36ffcf4.

Change-Id: If1879b331c1f0e3dea7433c5de53ac653743d9c2
Reviewed-on: http://git-master/r/72234
Reviewed-by: Automatic_Commit_Validation_User
Reviewed-by: Mallikarjun Kasoju 
Tested-by: Mallikarjun Kasoju 
Tested-by: Ahung Cheng 
Reviewed-by: Venkat Moganty

Revert "dm crypt: add loop aes iv generator"

2012-01-06T12:32:46+00:00

This reverts commit 34745785937a2003c144c0d4802fa637470d87af.

Change-Id: Ic1ee80202b92a5ceb4e04ceb041adfbb40274ca0
Reviewed-on: http://git-master/r/72233
Reviewed-by: Automatic_Commit_Validation_User
Reviewed-by: Mallikarjun Kasoju 
Tested-by: Mallikarjun Kasoju 
Tested-by: Ahung Cheng 
Reviewed-by: Venkat Moganty

Revert "dm crypt: wipe keys string immediately after key is set"

2012-01-06T12:32:35+00:00

This reverts commit de8be5ac70f50a2340f24fd769a1aafa5a51ae34.

Change-Id: I4d2788550ab382ec248c7a2fa10b4cb4e2766283
Reviewed-on: http://git-master/r/72232
Reviewed-by: Automatic_Commit_Validation_User
Reviewed-by: Mallikarjun Kasoju 
Tested-by: Mallikarjun Kasoju 
Tested-by: Ahung Cheng 
Reviewed-by: Venkat Moganty

md/raid5: STRIPE_ACTIVE has lock semantics, add barriers

2011-11-11T17:44:50+00:00

commit 257a4b42af7586fab4eaec7f04e6896b86551843 upstream.

All updates that occur under STRIPE_ACTIVE should be globally visible
when STRIPE_ACTIVE clears.  test_and_set_bit() implies a barrier, but
clear_bit() does not.

This is suitable for 3.1-stable.

Signed-off-by: Dan Williams 
Signed-off-by: NeilBrown 
Signed-off-by: Greg Kroah-Hartman

md/raid5: abort any pending parity operations when array fails.

2011-11-11T17:44:49+00:00

commit 9a3f530f39f4490eaa18b02719fb74ce5f4d2d86 upstream.

When the number of failed devices exceeds the allowed number
we must abort any active parity operations (checks or updates) as they
are no longer meaningful, and can lead to a BUG_ON in
handle_parity_checks6.

This bug was introduce by commit 6c0069c0ae9659e3a91b68eaed06a5c6c37f45c8
in 2.6.29.

Reported-by: Manish Katiyar 
Tested-by: Manish Katiyar 
Acked-by: Dan Williams 
Signed-off-by: NeilBrown 
Signed-off-by: Greg Kroah-Hartman