tree a615ed26cf1476e0af7c52f2f7c52e803619c151
parent 6945c01f1ab27f820ca822fc8cc53e09d6ab344b
author Rambo Wang <rambowang@google.com> 1583982024 -0700
committer Rambo Wang <rambowang@google.com> 1584125703 +0000

CellularDataService: mCallbackMap is not thread safe

The HashMap object mCallbackMap in CellularDataService is a shared
resource between DataService's handler thread and CellularDataService's
handler thread. The update operations (put and remove) has
synchronization issue.

This CL fixes the issue by letting CellularDataService shares the
looper/handler thread of DataService (but keeping its own handler). And
thus all the operations of mCallbackMap are handled serializally in
DataService's handler thread.

One alternative solution is to  move all operations of the mCallbackMap
into
CellularDataService's handler thread to make it thread-safe. But it's
difficult for close() method which need to clear mCallbackMap and
shutdown the handler thread.

The other alternative solution is to replace HashMap with
ConcurrentHashMap
for mCallbackMap. This do make mCallbackMap thread-safe but do not
change the fact that it is still a shared resource between two threads.

Bug: 151103522
Test: atest FrameworksTelephonyTests
Merged-In: I7f5a507c2a79c7c77c5c2d7d3be147af80dc9f69
Change-Id: I7f5a507c2a79c7c77c5c2d7d3be147af80dc9f69
(cherry picked from commit ccf29801e2cbd48842ea91194453e50ae14125a3)