]> git-server-git.apps.pok.os.sepia.ceph.com Git - ceph.git/commit
projects / ceph.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: af9152f) | patch
journal: don't hold future lock during assignment 13033/head
authorJason Dillaman <dillaman@redhat.com>
Fri, 20 Jan 2017 19:26:43 +0000 (14:26 -0500)
committerJason Dillaman <dillaman@redhat.com>
Sat, 21 Jan 2017 14:48:14 +0000 (09:48 -0500)
commit0f21ceef8336e35ca16148a9d58f511037911418
treee1466eb8fd8ba8a74bb56fcf0630f07943457916tree | snapshot
parentaf9152f34a416a46bbf96b14b1416ca004c80f84commit | diff
journal: don't hold future lock during assignment

It's possible that the future raced with its owner and reaches
an empty reference count. This was resulting in the future being
destructed while its lock was still held.

Fixes: http://tracker.ceph.com/issues/18618
Signed-off-by: Jason Dillaman <dillaman@redhat.com>
src/journal/FutureImpl.cc diff | blob | history
src/journal/FutureImpl.h diff | blob | history
Unnamed repository; edit this file 'description' to name the repository.