2011 IEEE/IFIP 41st International Conference on Dependable Systems and Networks Workshops (DSN-W) 2011
DOI: 10.1109/dsnw.2011.5958814
|View full text |Cite
|
Sign up to set email alerts
|

Platform-wide deadlock immunity for mobile phones

Abstract: Abstract-We present an implementation of our deadlock immunity system, Dimmunix, for mobile phone software. Within Android 2.2 OS, we modified Dalvik VM, the JVM running all the Android applications, to provide platform-wide deadlock immunity. We successfully ran the Dimmunix-enabled Android 2.2 OS on a Nexus One phone. On the phone, we reproduced a real deadlock involving Android's NotificationManagerService and StatusBarService classes, which froze the entire phone's interface. Android Dimmunix successfully … Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
4
0

Year Published

2014
2014
2016
2016

Publication Types

Select...
3
1

Relationship

0
4

Authors

Journals

citations
Cited by 4 publications
(4 citation statements)
references
References 3 publications
0
4
0
Order By: Relevance
“…Dimmunix (Jula et al 2008(Jula et al , 2011 is such a tool for Android applications. Also, RacerX (Engler and Ashcraft 2003), Jlint (Artho and Biere 2001), and EPAJ (Agarwal et al 2006) Static code analyzers test applications from many different angles.…”
Section: Static Checking Toolsmentioning
confidence: 99%
“…Dimmunix (Jula et al 2008(Jula et al , 2011 is such a tool for Android applications. Also, RacerX (Engler and Ashcraft 2003), Jlint (Artho and Biere 2001), and EPAJ (Agarwal et al 2006) Static code analyzers test applications from many different angles.…”
Section: Static Checking Toolsmentioning
confidence: 99%
“…The highest number of threads were created by the Flipkart application (36 of them without task queues and 3 with queues). These numbers do not include the count of binder threads and other system threads created by the Android runtime for the applications (usually about [10][11][12][13][14][15]. The applications also made many asynchronous calls (see the column "Async.…”
Section: Discussionmentioning
confidence: 99%
“…Therefore, the asynchronous tasks executing the read and write operations 16 and 21 also are not ordered and give rise to another potential data race but this time between two operations on the same thread. As operation 21 (line 15 in Figure 1) sets isActivityDestroyed to true, if the operations in any of the two racey pairs (12,21) and (16,21) are reordered then the corresponding assertions at lines 41 and 53 in Figure 1 would fail. …”
Section: Data Races and Happens-before Reasoningmentioning
confidence: 99%
See 1 more Smart Citation