rbd: fix image request leak on parent read
authorAlex Elder <elder@inktank.com>
Thu, 2 May 2013 02:37:07 +0000 (21:37 -0500)
committerAlex Elder <elder@inktank.com>
Thu, 2 May 2013 17:15:28 +0000 (12:15 -0500)
commitb5b09be30cf99f9c699e825629f02e3bce555d44
treee0fde7c77f9d6d2c5acbae75bb03004cbd9aaf46
parent5522ae0b68421e2645303ff010e27afc5292e0ab
rbd: fix image request leak on parent read

When a read for a layered image object finds the target object
doesn't exist, a read image request for the parent image is created
and submitted.  When that completes, the callback routine was
not releasing that parent image request.  Fix that.

The slab allocation stuff just added has greatly simplified the
search for the source of this memory leak.

This resolves:
    http://tracker.ceph.com/issues/4803

Signed-off-by: Alex Elder <elder@inktank.com>
Reviewed-by: Josh Durgin <josh.durgin@inktank.com>
drivers/block/rbd.c