]> git.baikalelectronics.ru Git - kernel.git/commit
md: Push down data integrity code to personalities.
authorAndre Noll <maan@systemlinux.org>
Mon, 3 Aug 2009 00:59:47 +0000 (10:59 +1000)
committerNeilBrown <neilb@suse.de>
Mon, 3 Aug 2009 00:59:47 +0000 (10:59 +1000)
commit9747dafff95a6b4a0d25a42974d43a6875e9ccad
treedabce6a99c2af9f00b33660f6b2d906cce836764
parentebc6d3931df097c3cc54de7f867eca0753bf6132
md: Push down data integrity code to personalities.

This patch replaces md_integrity_check() by two new public functions:
md_integrity_register() and md_integrity_add_rdev() which are both
personality-independent.

md_integrity_register() is called from the ->run and ->hot_remove
methods of all personalities that support data integrity.  The
function iterates over the component devices of the array and
determines if all active devices are integrity capable and if their
profiles match. If this is the case, the common profile is registered
for the mddev via blk_integrity_register().

The second new function, md_integrity_add_rdev() is called from the
->hot_add_disk methods, i.e. whenever a new device is being added
to a raid array. If the new device does not support data integrity,
or has a profile different from the one already registered, data
integrity for the mddev is disabled.

For raid0 and linear, only the call to md_integrity_register() from
the ->run method is necessary.

Signed-off-by: Andre Noll <maan@systemlinux.org>
Signed-off-by: NeilBrown <neilb@suse.de>
drivers/md/linear.c
drivers/md/md.c
drivers/md/md.h
drivers/md/multipath.c
drivers/md/raid0.c
drivers/md/raid1.c
drivers/md/raid10.c