NeilBrown 9910f16af3 [PATCH] md: fix up some rdev rcu locking in raid5/6 ... There is this "FIXME" comment with a typo in it!! that been annoying me for days, so I just had to remove it. conf->disks[i].rdev should only be accessed if - we know we hold a reference or - the mddev->reconfig_sem is down or - we have a rcu_readlock handle_stripe was referencing rdev in three places without any of these. For the first two, get an rcu_readlock. For the last, the same access (md_sync_acct call) is made a little later after the rdev has been claimed under and rcu_readlock, if R5_Syncio is set. So just use that access... However R5_Syncio isn't really needed as the 'syncing' variable contains the same information. So use that instead. Issues, comment, and fix are identical in raid5 and raid6. Signed-off-by: Neil Brown <neilb@suse.de> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>		2006-01-06 08:34:04 -08:00
..
bitmap.h	[PATCH] md: make md on-disk bitmaps not host-endian	2005-11-09 07:56:38 -08:00
linear.h	[PATCH] md: support md/linear array with components greater than 2 terabytes.	2005-09-09 16:39:10 -07:00
md.h	[PATCH] md: support BIO_RW_BARRIER for md/raid1	2005-11-09 07:56:38 -08:00
md_k.h	[PATCH] md: allow dirty raid[456] arrays to be started at boot	2006-01-06 08:34:02 -08:00
md_p.h	[PATCH] md: allow md to load a superblock with feature-bit '1' set	2005-09-09 16:39:11 -07:00
md_u.h
multipath.h
raid0.h
raid1.h	[PATCH] md: handle errors when read-only	2006-01-06 08:34:04 -08:00
raid5.h	[PATCH] md: fix up some rdev rcu locking in raid5/6	2006-01-06 08:34:04 -08:00
raid10.h	[PATCH] md: write intent bitmap support for raid10	2006-01-06 08:34:03 -08:00
xor.h