Proceedings of the Twenty-Fifth International Conference on Architectural Support for Programming Languages and Operating Syste 2020
DOI: 10.1145/3373376.3378452
|View full text |Cite
|
Sign up to set email alerts
|

Cross-Failure Bug Detection in Persistent Memory Programs

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
4
1

Citation Types

0
28
0
1

Year Published

2021
2021
2024
2024

Publication Types

Select...
3
2
2

Relationship

0
7

Authors

Journals

citations
Cited by 45 publications
(29 citation statements)
references
References 40 publications
0
28
0
1
Order By: Relevance
“…It is important but challenging to identify crash-consistency bugs, especially for concurrent PM programs. Existing PM-based debugging tools record the PM accesses [36,37] or track the persistency states [45] to detect the violation of consistency rules. However, these debugging tools fail to efficiently detect the bugs in concurrent PM programs due to the following two reasons: (1) existing PM-specific debugging tools do not consider the thread interleavings in concurrent programs, thus overlooking the inconsistency hidden in specific interleavings and (2) the input space of programs can be so huge that it is almost impossible to efficiently trigger bugs using exhaustive testing.…”
Section: Motivationmentioning
confidence: 99%
See 1 more Smart Citation
“…It is important but challenging to identify crash-consistency bugs, especially for concurrent PM programs. Existing PM-based debugging tools record the PM accesses [36,37] or track the persistency states [45] to detect the violation of consistency rules. However, these debugging tools fail to efficiently detect the bugs in concurrent PM programs due to the following two reasons: (1) existing PM-specific debugging tools do not consider the thread interleavings in concurrent programs, thus overlooking the inconsistency hidden in specific interleavings and (2) the input space of programs can be so huge that it is almost impossible to efficiently trigger bugs using exhaustive testing.…”
Section: Motivationmentioning
confidence: 99%
“…We refer to concurrency bugs that only occur in PM programs (not triggered in non-PM programs) as PM concurrency bugs. Many PM-specific testing tools have been proposed to detect the violations of crash consistency in PM programs by leveraging various mechanisms, e.g., programmer-annotated assertions [37], crashconsistency bug patterns [15,35,36], symbolic execution [45], model checking [20,29], and likely-correctness conditions with output equivalence checking [19], but none targets PM concurrency bugs. In fact, the concurrency bugs triggered only in specific interleavings are known to be more difficult to detect [33,38].…”
Section: Introductionmentioning
confidence: 99%
“…Emerging Non-Volatile Random-Access Memories (NVRAM) provide the best of two worlds, namely the efficiency of DRAM, and the data persistency across failures of a non-volatile store [Intel 2019c;Liu et al 2020]. In particular, NVRAMs offer byte addressability, i.e., they can be addressed directly by the CPU through read and write operations, thus giving programs direct and low-latency access to persistent data, without any assistance from the operating system.…”
Section: Introductionmentioning
confidence: 99%
“…This is why NVRAMs are often referred to as Persistent Memories (PMs). The combination of efficiency and persistency is a very attractive feature, breeding interest in PMs, and spurring research both in industry and academia [ARM 2018;Intel 2019b;Liu et al 2020;Raad et al 2020. Leading chip manufacturers such as Intel and ARM have started to integrate the technology in their chips [ARM 2018;Intel 2019b].…”
Section: Introductionmentioning
confidence: 99%
See 1 more Smart Citation