ACM Home Page
Please provide us with feedback. Feedback
AVIO: detecting atomicity violations via access interleaving invariants
Full text PdfPdf (394 KB)
Source Architectural Support for Programming Languages and Operating Systems archive
Proceedings of the 12th international conference on Architectural support for programming languages and operating systems table of contents
San Jose, California, USA
SESSION: Races and memory debugging I table of contents
Pages: 37 - 48  
Year of Publication: 2006
ISBN:1-59593-451-0
Also published in ...
Authors
Shan Lu  University of Illinois at Urbana Champaign
Joseph Tucek  University of Illinois at Urbana Champaign
Feng Qin  University of Illinois at Urbana Champaign
Yuanyuan Zhou  University of Illinois at Urbana Champaign
Sponsors
ACM: Association for Computing Machinery
SIGARCH: ACM Special Interest Group on Computer Architecture
SIGPLAN: ACM Special Interest Group on Programming Languages
SIGOPS: ACM Special Interest Group on Operating Systems
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 15,   Downloads (12 Months): 208,   Citation Count: 10
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues  

Tools and Actions: Review this Article  
Save this Article to a Binder    Display Formats: BibTex  EndNote ACM Ref   
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1168857.1168864
What is a DOI?

ABSTRACT

Concurrency bugs are among the most difficult to test and diagnose of all software bugs. The multicore technology trend worsens this problem. Most previous concurrency bug detection work focuses on one bug subclass, data races, and neglects many other important ones such as atomicity violations, which will soon become increasingly important due to the emerging trend of transactional memory models.This paper proposes an innovative, comprehensive, invariantbased approach called AVIO to detect atomicity violations. Our idea is based on a novel observation called access interleaving invariant, which is a good indication of programmers' assumptions about the atomicity of certain code regions. By automatically extracting such invariants and detecting violations of these invariants at run time, AVIO can detect a variety of atomicity violations.Based on this idea, we have designed and built two implementations of AVIO and evaluated the trade-offs between them. The first implementation, AVIO-S, is purely in software, while the second, AVIO-H, requires some simple extensions to the cache coherence hardware. AVIO-S is cheaper and more accurate but incurs much higher overhead and thus more run-time perturbation than AVIOH. Therefore, AVIO-S is more suitable for in-house bug detection and postmortem bug diagnosis, while AVIO-H can be used for bug detection during production runs.We evaluate both implementations of AVIO using large realworld server applications (Apache and MySQL) with six representative real atomicity violation bugs, and SPLASH-2 benchmarks. Our results show that AVIO detects more tested atomicity violations of various types and has 25 times fewer false positives than previous solutions on average.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
2
3
 
4
M. Burrows and K.R.M. Leino. Finding stale-value errors in concurrent programs. In Compaq SRC Technical Note 2002-04, 2002.
 
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
 
22
P.S. Magnusson, F. Dahlgren, H. Grahn, M. Karlsson, F. Larsson, F. Lundholm, A. Moestedt, J. Nilsson, P. Stenstrom, and B. Werner. Simics/sun4m: A virtual workstation. In Usenix Annual Technical Conference, 1998.
23
24
 
25
N. Nethercote and J. Seward. Valgrind: A program supervision framework. ENTCS, 2003.
26
27
28
29
 
30
M. Prvulovic. Cord:cost-effective (and nearly overhead-free) orderreordering and data race detection. In HPCA, 2006.
31
32
33
34
 
35
SecurityFocus. Software bug contributed to blackout.
 
36
37
38
39
40
41
42
43
 
44
45

CITED BY  10

Collaborative Colleagues:
Shan Lu: colleagues
Joseph Tucek: colleagues
Feng Qin: colleagues
Yuanyuan Zhou: colleagues