summaryrefslogtreecommitdiffstats
path: root/drivers/md/Kconfig
diff options
context:
space:
mode:
authorNeilBrown <neilb@suse.de>2009-03-31 15:26:47 +1100
committerNeilBrown <neilb@suse.de>2009-03-31 15:26:47 +1100
commitab69ae12ceef7f23c578a3c230144e94a167a821 (patch)
tree01bee8e4c4a91a1714596c4f85769bfe72e328ce /drivers/md/Kconfig
parentd1a7c50369835f9ecbd7752016cd9302ecfae678 (diff)
downloadtalos-op-linux-ab69ae12ceef7f23c578a3c230144e94a167a821.tar.gz
talos-op-linux-ab69ae12ceef7f23c578a3c230144e94a167a821.zip
md/raid5: be more careful about write ordering when reshaping.
When we are reshaping an array, it is very important that we read the data from a particular sector offset before writing new data at that offset. In most cases when growing or shrinking an array we read long before we even consider writing. But when restriping an array without changing it size, there is a small possibility that we might have some data to available write before the read has happened at the same location. This would require some stripes to be in cache already. To guard against this small possibility, we check, before writing, that the 'old' stripe at the same location is not in the process of being read. And we ensure that we mark all 'source' stripes as such before allowing new 'destination' stripes to proceed. Signed-off-by: NeilBrown <neilb@suse.de>
Diffstat (limited to 'drivers/md/Kconfig')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud