All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josh Durgin <josh.durgin@inktank.com>
To: Alex Elder <elder@inktank.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: [PATCH] rbd: add new snapshots at the tail
Date: Tue, 04 Sep 2012 15:43:59 -0700	[thread overview]
Message-ID: <5046842F.7050804@inktank.com> (raw)
In-Reply-To: <50464390.3010107@inktank.com>

Reviewed-by: Josh Durgin <josh.durgin@inktank.com>

On 09/04/2012 11:08 AM, Alex Elder wrote:
> 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>
> ---
>   drivers/block/rbd.c |    2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/block/rbd.c b/drivers/block/rbd.c
> index 8e6e29e..fd51f9d 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 */
>


      reply	other threads:[~2012-09-04 22:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-04 18:08 [PATCH] rbd: add new snapshots at the tail Alex Elder
2012-09-04 22:43 ` Josh Durgin [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5046842F.7050804@inktank.com \
    --to=josh.durgin@inktank.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=elder@inktank.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.