rbd: don't mess with a page vector in rbd_notify_op_lock()
rbd_notify_op_lock() isn't interested in a notify reply. Instead of accepting that page vector just to free it, have watch-notify code take care of it. Signed-off-by: Ilya Dryomov <idryomov@gmail.com> Reviewed-by: Jason Dillaman <dillaman@redhat.com>
This commit is contained in:
parent
b877605152
commit
8ae0299a4b
|
@ -3754,11 +3754,7 @@ static int __rbd_notify_op_lock(struct rbd_device *rbd_dev,
|
|||
static void rbd_notify_op_lock(struct rbd_device *rbd_dev,
|
||||
enum rbd_notify_op notify_op)
|
||||
{
|
||||
struct page **reply_pages;
|
||||
size_t reply_len;
|
||||
|
||||
__rbd_notify_op_lock(rbd_dev, notify_op, &reply_pages, &reply_len);
|
||||
ceph_release_page_vector(reply_pages, calc_pages_for(0, reply_len));
|
||||
__rbd_notify_op_lock(rbd_dev, notify_op, NULL, NULL);
|
||||
}
|
||||
|
||||
static void rbd_notify_acquired_lock(struct work_struct *work)
|
||||
|
|
Loading…
Reference in New Issue