Ceph » rbd

This is very old. And--provided I understand it--it is resolved
in the current rbd code.

When a mapped rbd image is created it sets up rbd_dev_release
as the function to call when the last reference to the device
is dropped. That gets called when the last reference to a
block device gets dropped.

The first thing rbd_dev_release() does is synchronously drop
the watch request on the header object. So before any other
of this final teardown activity proceeds the watch request
will be gone.

And I think any incoming notify requests that might have
been sent prior to that will be done by then, and we won't
get them thereafter.

So... I'm going to call this resolved.