From: Alex Elder <elder@inktank.com>
To: ceph-devel@vger.kernel.org
Subject: [PATCH 0/5] rbd: avoid snapshot update race
Date: Sat, 27 Apr 2013 14:37:56 -0500 [thread overview]
Message-ID: <517C2914.8030400@inktank.com> (raw)
This series ends with a patch that avoids a race involving the
initial read of an rbd image header and a change to the snapshot
context. The problem occurs because the rbd client sets up its
watch request on the header object *after* the initial header
read, and if the snapshot context changes between them the
kernel client snapshot context will not be up-to-date.
The fix is to set up the watch before doing the initial
header read. The recent patches, along with the patches
in this series, make doing things in this order possible.
-Alex
[PATCH 1/5] rbd: move more initialization into rbd_dev_probe_image()
[PATCH 2/5] rbd: define rbd_header_name()
[PATCH 3/5] rbd: don't clean up watch in device release function
[PATCH 4/5] rbd: don't bother checking whether order changes
[PATCH 5/5] rbd: set up watch in rbd_dev_probe_image()
next reply other threads:[~2013-04-27 19:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-27 19:37 Alex Elder [this message]
2013-04-27 19:39 ` [PATCH 1/5] rbd: move more initialization into rbd_dev_probe_image() Alex Elder
2013-04-27 19:39 ` [PATCH 2/5] rbd: define rbd_header_name() Alex Elder
2013-04-27 19:39 ` [PATCH 3/5] rbd: don't clean up watch in device release function Alex Elder
2013-04-27 19:39 ` [PATCH 4/5] rbd: don't bother checking whether order changes Alex Elder
2013-04-27 19:40 ` [PATCH 5/5] rbd: set up watch in rbd_dev_probe_image() Alex Elder
2013-04-27 19:42 ` [PATCH 0/5] rbd: avoid snapshot update race Alex Elder
2013-04-29 17:52 ` Alex Elder
2013-04-30 19:13 ` Josh Durgin
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=517C2914.8030400@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.