summaryrefslogtreecommitdiffstats
path: root/include/linux/raid
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@woody.linux-foundation.org>2007-05-09 18:51:36 -0700
committerLinus Torvalds <torvalds@woody.linux-foundation.org>2007-05-09 18:51:36 -0700
commit44ce6294d07555c3d313757105fd44b78208407f (patch)
tree29659bee16a4d7111124c6f41289bc9c11669e70 /include/linux/raid
parent497f050c42e46a4b1f6a9bcd8827fa5d97fe1feb (diff)
downloadop-kernel-dev-44ce6294d07555c3d313757105fd44b78208407f.zip
op-kernel-dev-44ce6294d07555c3d313757105fd44b78208407f.tar.gz
Revert "md: improve partition detection in md array"
This reverts commit 5b479c91da90eef605f851508744bfe8269591a0. Quoth Neil Brown: "It causes an oops when auto-detecting raid arrays, and it doesn't seem easy to fix. The array may not be 'open' when do_md_run is called, so bdev->bd_disk might be NULL, so bd_set_size can oops. This whole approach of opening an md device before it has been assembled just seems to get more and more painful. I think I'm going to have to come up with something clever to provide both backward comparability with usage expectation, and sane integration into the rest of the kernel." Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'include/linux/raid')
-rw-r--r--include/linux/raid/md_k.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/include/linux/raid/md_k.h b/include/linux/raid/md_k.h
index a121f36..de72c49 100644
--- a/include/linux/raid/md_k.h
+++ b/include/linux/raid/md_k.h
@@ -201,6 +201,7 @@ struct mddev_s
struct mutex reconfig_mutex;
atomic_t active;
+ int changed; /* true if we might need to reread partition info */
int degraded; /* whether md should consider
* adding a spare
*/
OpenPOWER on IntegriCloud