summaryrefslogtreecommitdiff
path: root/drivers/md/bitmap.c
diff options
context:
space:
mode:
authorNeilBrown <neilb@suse.de>2007-01-26 00:57:02 -0800
committerLinus Torvalds <torvalds@woody.linux-foundation.org>2007-01-26 13:50:59 -0800
commit1031be7a5fafd3a858dfaabb74d98f9ca20744a8 (patch)
treeb111bc6880571e3ad0720da828a029ecae066c8a /drivers/md/bitmap.c
parent3eda22d19b76b15ef3420b251bd47a0ba0127589 (diff)
[PATCH] md: make sure the events count in an md array never returns to zero
Now that we sometimes step the array events count backwards (when transitioning dirty->clean where nothing else interesting has happened - so that we don't need to write to spares all the time), it is possible for the event count to return to zero, which is potentially confusing and triggers and MD_BUG. We could possibly remove the MD_BUG, but is just as easy, and probably safer, to make sure we never return to zero. Signed-off-by: Neil Brown <neilb@suse.de> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'drivers/md/bitmap.c')
0 files changed, 0 insertions, 0 deletions