From: Alex Elder <elder@inktank.com>
To: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: [PATCH 0/2] rbd: snap context references
Date: Fri, 09 Nov 2012 21:05:23 -0600 [thread overview]
Message-ID: <509DC473.805@inktank.com> (raw)
These two patches are related to how snapshot context
reference counting is handled in rbd_do_op().
-Alex
[PATCH 1/2] rbd: fix reference leak in rbd_do_op()
[PATCH 2/2] rbd: only get snap context for write requests
next reply other threads:[~2012-11-10 3:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-10 3:05 Alex Elder [this message]
2012-11-10 3:06 ` [PATCH 1/2] rbd: fix reference leak in rbd_do_op() Alex Elder
2012-11-10 3:06 ` [PATCH 2/2] rbd: only get snap context for write requests 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=509DC473.805@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox