diff options
author | NeilBrown <neilb@suse.de> | 2009-02-06 18:02:46 +1100 |
---|---|---|
committer | NeilBrown <neilb@suse.de> | 2009-02-06 18:02:46 +1100 |
commit | de01dfadf25bf83cfe3d85c163005c4320532658 (patch) | |
tree | dc1cca5a6aa10ecc0fea2fb9f13534685ba8ff61 /drivers/md/dm-delay.c | |
parent | 852c8bf484a0e17ee27f413ef26e87f522af5607 (diff) | |
download | op-kernel-dev-de01dfadf25bf83cfe3d85c163005c4320532658.zip op-kernel-dev-de01dfadf25bf83cfe3d85c163005c4320532658.tar.gz |
md: Ensure an md array never has too many devices.
Each different metadata format supported by md supports a
different maximum number of devices.
We really should be enforcing this maximum in the kernel, but
we aren't quite doing that properly.
We currently only enforce it at the 'hot_add' point, which is an
older interface which is not used by current userspace.
We need to also enforce it at 'add_new_disk' time for active arrays
and at 'do_md_run' time when starting a new array.
So move the test from 'hot_add' into 'bind_rdev_to_array' which is
called from both 'hot_add' and 'add_new_disk, and add a new
test in 'analyse_sbs' which is called from 'do_md_run'.
This bug (or missing feature) has been around "forever" and so
the patch is suitable for any -stable that is currently maintained.
Cc: stable@kernel.org
Signed-off-by: NeilBrown <neilb@suse.de>
Diffstat (limited to 'drivers/md/dm-delay.c')
0 files changed, 0 insertions, 0 deletions