CEPH filesystem development
 help / color / mirror / Atom feed
From: Josh Durgin <josh.durgin@inktank.com>
To: Alex Elder <elder@inktank.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: [PATCH 2/2] rbd: don't leak rbd_req for rbd_req_sync_notify_ack()
Date: Mon, 03 Dec 2012 13:07:55 -0800	[thread overview]
Message-ID: <50BD14AB.30207@inktank.com> (raw)
In-Reply-To: <50B8D937.5060600@inktank.com>

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

On 11/30/2012 08:05 AM, Alex Elder wrote:
> When rbd_req_sync_notify_ack() calls rbd_do_request() it supplies
> rbd_simple_req_cb() as its callback function.  Because the callback
> is supplied, an rbd_req structure gets allocated and populated so it
> can be used by the callback.  However rbd_simple_req_cb() is not
> freeing (or even using) the rbd_req structure, so it's getting
> leaked.
>
> Since rbd_simple_req_cb() has no need for the rbd_req structure,
> just avoid allocating one for this case.  Of the three calls to
> rbd_do_request(), only the one from rbd_do_op() needs the rbd_req
> structure, and that call can be distinguished from the other two
> because it supplies a non-null rbd_collection pointer.
>
> So fix this leak by only allocating the rbd_req structure if a
> non-null "coll" value is provided to rbd_do_request().
>
> Signed-off-by: Alex Elder <elder@inktank.com>
> ---
>   drivers/block/rbd.c |    4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/block/rbd.c b/drivers/block/rbd.c
> index 78493e7..fca0ebf 100644
> --- a/drivers/block/rbd.c
> +++ b/drivers/block/rbd.c
> @@ -1182,7 +1182,7 @@ static int rbd_do_request(struct request *rq,
>   		bio_get(osd_req->r_bio);
>   	}
>
> -	if (rbd_cb) {
> +	if (coll) {
>   		ret = -ENOMEM;
>   		rbd_req = kmalloc(sizeof(*rbd_req), GFP_NOIO);
>   		if (!rbd_req)
> @@ -1193,7 +1193,7 @@ static int rbd_do_request(struct request *rq,
>   		rbd_req->pages = pages;
>   		rbd_req->len = len;
>   		rbd_req->coll = coll;
> -		rbd_req->coll_index = coll ? coll_index : 0;
> +		rbd_req->coll_index = coll_index;
>   	}
>
>   	osd_req->r_callback = rbd_cb;
>


      reply	other threads:[~2012-12-03 21:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-30 16:03 [PATCH 0/2] rbd: fix two memory leaks Alex Elder
2012-11-30 16:04 ` [PATCH 1/2] rbd: don't leak rbd_req on synchronous requests Alex Elder
2012-12-03 21:06   ` Josh Durgin
2012-11-30 16:05 ` [PATCH 2/2] rbd: don't leak rbd_req for rbd_req_sync_notify_ack() Alex Elder
2012-12-03 21:07   ` 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=50BD14AB.30207@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox