The existing concurrency model for Java (or C) requires programmers to design and implement thread-safe classes by explicitly acquiring locks and releasing locks. Such a model is error-prone and is the reason for many concurrency bugs. While there are alternative models like transactional memory, manually writing locks remains prevalent in practice. In this work, we propose AutoLock, which aims to solve the problem by fully automatically generating thread-safe classes. Given a class which is assumed to be correct with sequential clients, AutoLock automatically generates a thread-safe class which is linearizable and does it in a way without requiring a specification of the class. AutoLock takes three steps: (1) infer access annotations (i.e., abstract information on how variables are accessed and aliased), (2) synthesize a locking policy based on the access annotations, and (3) consistently implement the locking policy. AutoLock has been evaluated on a set of benchmark programs and the results show that AutoLock generates thread-safe classes effectively and could have prevented existing concurrency bugs.
Thu 24 SepDisplayed time zone: (UTC) Coordinated Universal Time change
02:20 - 03:20
|CCGraph: a PDG-based code clone detector with approximate graph matching|
|Towards Generating Thread-Safe Classes Automatically|
Yi Liu Southern University of Science and Technology, Jinhui Xie Tencent Inc., Jianbo Yang Tencent Inc., Shiyu Guo Tencent Inc., Yuetang Deng Tencent, Inc., Shuqing Li Southern University of Science and Technology, Yechang Wu Southern University of Science and Technology, Yepang Liu Southern University of Science and Technology