]> git.apps.os.sepia.ceph.com Git - ceph.git/commit
projects / ceph.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: eb84959) | patch
journal: don't hold future lock during assignment 14538/head
authorJason Dillaman <dillaman@redhat.com>
Fri, 20 Jan 2017 19:26:43 +0000 (14:26 -0500)
committerNathan Cutler <ncutler@suse.com>
Thu, 13 Apr 2017 21:06:26 +0000 (23:06 +0200)
commitbafa2b0c83d32b97a6dd85e681f2344384c539ac
tree8f3071c8fdf8d8805315768f6114e215c4564b31tree | snapshot
parenteb84959bac369dbb86674f9e4225ba1c836c104ccommit | 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>
(cherry picked from commit 0f21ceef8336e35ca16148a9d58f511037911418)
src/journal/FutureImpl.cc diff | blob | history
src/journal/FutureImpl.h diff | blob | history
Unnamed repository; edit this file 'description' to name the repository.