From: Alex Elder <elder@inktank.com>
To: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: [PATCH REPOST 0/2] rbd: fix two leaks
Date: Fri, 04 Jan 2013 08:57:18 -0600 [thread overview]
Message-ID: <50E6EDCE.8050608@inktank.com> (raw)
When certain special osd requests are processed, they have data
structures allocated that are not properly freed when the request
is completed. This series fixes that.
-Alex
[PATCH REPOST 1/2] rbd: don't leak rbd_req on synchronous requests
[PATCH REPOST 2/2] rbd: don't leak rbd_req for rbd_req_sync_notify_ack()
next reply other threads:[~2013-01-04 14:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-04 14:57 Alex Elder [this message]
2013-01-04 14:58 ` [PATCH REPOST 1/2] rbd: don't leak rbd_req on synchronous requests Alex Elder
2013-01-04 14:58 ` [PATCH REPOST 2/2] rbd: don't leak rbd_req for rbd_req_sync_notify_ack() Alex Elder
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=50E6EDCE.8050608@inktank.com \
--to=elder@inktank.com \
--cc=ceph-devel@vger.kernel.org \
/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.