diff options
author | Dmitry Torokhov <dtor@chromium.org> | 2015-12-14 17:34:08 -0800 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2019-04-03 06:23:20 +0200 |
commit | 119dbcde59da0d44c6f39a4d83b01577910303d4 (patch) | |
tree | e9eea63b7119efc6d0f186086800283ed7fb145f /mm | |
parent | 7276c3fbd3b680df29732e443780de6117546b9e (diff) |
android: unconditionally remove callbacks in sync_fence_free()
[ Upstream commit 699f685569434510d944e419f4048c4e3ba8d631 ]
Using fence->status to determine whether or not there are callbacks
remaining on the sync_fence is racy since fence->status may have been
decremented to 0 on another CPU before fence_check_cb_func() has
completed. By unconditionally calling fence_remove_callback() for each
fence in the sync_fence, we guarantee that each callback has either
completed (since fence_remove_callback() grabs the fence lock) or been
removed.
Signed-off-by: Andrew Bresticker <abrestic@chromium.org>
Signed-off-by: Dmitry Torokhov <dtor@chromium.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'mm')
0 files changed, 0 insertions, 0 deletions