md/raid5: STRIPE_ACTIVE has lock semantics, add barriers
authorDan Williams <dan.j.williams@intel.com>
Tue, 8 Nov 2011 05:22:06 +0000 (16:22 +1100)
committerNeilBrown <neilb@suse.de>
Tue, 8 Nov 2011 05:22:06 +0000 (16:22 +1100)
commit257a4b42af7586fab4eaec7f04e6896b86551843
treeec65357b2320ba4e4341a2853245048889666f5c
parent9a3f530f39f4490eaa18b02719fb74ce5f4d2d86
md/raid5: STRIPE_ACTIVE has lock semantics, add barriers

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 <dan.j.williams@intel.com>
Signed-off-by: NeilBrown <neilb@suse.de>
Cc: stable@kernel.org
drivers/md/raid5.c