summaryrefslogtreecommitdiff
path: root/drivers/bluetooth/hci_mrvl.c
diff options
context:
space:
mode:
authorIlya Dryomov <idryomov@gmail.com>2020-03-16 15:52:54 +0100
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2020-04-24 08:01:16 +0200
commitf463b1273df7624f9a8a5d4de53e42207061b90c (patch)
treed8040b7b0126fd6950a36aa3d9ebdbc1665b7b5f /drivers/bluetooth/hci_mrvl.c
parentfce4bd5793775570e461fc5d2da9b47e12a62c74 (diff)
rbd: call rbd_dev_unprobe() after unwatching and flushing notifies
[ Upstream commit 952c48b0ed18919bff7528501e9a3fff8a24f8cd ] rbd_dev_unprobe() is supposed to undo most of rbd_dev_image_probe(), including rbd_dev_header_info(), which means that rbd_dev_header_info() isn't supposed to be called after rbd_dev_unprobe(). However, rbd_dev_image_release() calls rbd_dev_unprobe() before rbd_unregister_watch(). This is racy because a header update notify can sneak in: "rbd unmap" thread ceph-watch-notify worker rbd_dev_image_release() rbd_dev_unprobe() free and zero out header rbd_watch_cb() rbd_dev_refresh() rbd_dev_header_info() read in header The same goes for "rbd map" because rbd_dev_image_probe() calls rbd_dev_unprobe() on errors. In both cases this results in a memory leak. Fixes: fd22aef8b47c ("rbd: move rbd_unregister_watch() call into rbd_dev_image_release()") Signed-off-by: Ilya Dryomov <idryomov@gmail.com> Reviewed-by: Jason Dillaman <dillaman@redhat.com> Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'drivers/bluetooth/hci_mrvl.c')
0 files changed, 0 insertions, 0 deletions