CEPH filesystem development
 help / color / mirror / Atom feed
From: Josh Durgin <jdurgin@redhat.com>
To: Ilya Dryomov <idryomov@gmail.com>, ceph-devel@vger.kernel.org
Subject: Re: [PATCH] rbd: don't put snap_context twice in rbd_queue_workfn()
Date: Tue, 1 Dec 2015 13:04:51 -0800	[thread overview]
Message-ID: <565E0B73.2060106@redhat.com> (raw)
In-Reply-To: <1449000269-27732-1-git-send-email-idryomov@gmail.com>

On 12/01/2015 12:04 PM, Ilya Dryomov wrote:
> Commit 4e752f0ab0e8 ("rbd: access snapshot context and mapping size
> safely") moved ceph_get_snap_context() out of rbd_img_request_create()
> and into rbd_queue_workfn(), adding a ceph_put_snap_context() to the
> error path in rbd_queue_workfn().  However, rbd_img_request_create()
> consumes a ref on snapc, so calling ceph_put_snap_context() after
> a successful rbd_img_request_create() leads to an extra put.  Fix it.
>
> Cc: stable@vger.kernel.org # 3.18+
> Signed-off-by: Ilya Dryomov <idryomov@gmail.com>

Whoops!

Reviewed-by: Josh Durgin <jdurgin@redhat.com>

>   drivers/block/rbd.c | 1 +
>   1 file changed, 1 insertion(+)
>
> diff --git a/drivers/block/rbd.c b/drivers/block/rbd.c
> index 24a757e97d56..4a876785b68c 100644
> --- a/drivers/block/rbd.c
> +++ b/drivers/block/rbd.c
> @@ -3442,6 +3442,7 @@ static void rbd_queue_workfn(struct work_struct *work)
>   		goto err_rq;
>   	}
>   	img_request->rq = rq;
> +	snapc = NULL; /* img_request consumes a ref */
>
>   	if (op_type == OBJ_OP_DISCARD)
>   		result = rbd_img_request_fill(img_request, OBJ_REQUEST_NODATA,
>


      reply	other threads:[~2015-12-01 21:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-01 20:04 [PATCH] rbd: don't put snap_context twice in rbd_queue_workfn() Ilya Dryomov
2015-12-01 21:04 ` 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=565E0B73.2060106@redhat.com \
    --to=jdurgin@redhat.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=idryomov@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox