summaryrefslogtreecommitdiff
path: root/drivers/block
diff options
context:
space:
mode:
authorAlex Elder <elder@inktank.com>2012-08-30 00:16:37 -0500
committerAlex Elder <elder@inktank.com>2012-10-01 14:30:49 -0500
commit523f32582f30768ab4e56b71b276fc1ea71f48cc (patch)
tree1052828c0c8580c2a46cc763ecd1f7becdf92a3d /drivers/block
parent843a0d0879935742bb7270c9dc8d94abb8b39cee (diff)
rbd: add new snapshots at the tail
This fixes a bug that went in with this commit: commit f6e0c99092cca7be00fca4080cfc7081739ca544 Author: Alex Elder <elder@inktank.com> Date: Thu Aug 2 11:29:46 2012 -0500 rbd: simplify __rbd_init_snaps_header() The problem is that a new rbd snapshot needs to go either after an existing snapshot entry, or at the *end* of an rbd device's snapshot list. As originally coded, it is placed at the beginning. This was based on the assumption the list would be empty (so it wouldn't matter), but in fact if multiple new snapshots are added to an empty list in one shot the list will be non-empty after the first one is added. This addresses http://tracker.newdream.net/issues/3063 Signed-off-by: Alex Elder <elder@inktank.com> Reviewed-by: Josh Durgin <josh.durgin@inktank.com>
Diffstat (limited to 'drivers/block')
-rw-r--r--drivers/block/rbd.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/block/rbd.c b/drivers/block/rbd.c
index 14bf83ba45d3..2b40a4af4d17 100644
--- a/drivers/block/rbd.c
+++ b/drivers/block/rbd.c
@@ -2187,7 +2187,7 @@ static int __rbd_init_snaps_header(struct rbd_device *rbd_dev)
if (snap)
list_add_tail(&new_snap->node, &snap->node);
else
- list_add(&new_snap->node, head);
+ list_add_tail(&new_snap->node, head);
} else {
/* Already have this one */