reproducing concurrency failures from crash stacks
play

Reproducing Concurrency Failures from Crash Stacks Francesco A. - PowerPoint PPT Presentation

Reproducing Concurrency Failures from Crash Stacks Francesco A. Bianchi* Mauro Pezz* Valerio Terragni * Universit di Milano Bicocca, * USI Universit della Svizzera italiana, Switzerland Italy ESEC/FSE 2017 Introduction


  1. Reproducing Concurrency Failures from Crash Stacks Francesco A. Bianchi* Mauro Pezzè* ◇ Valerio Terragni * ◇ Università di Milano Bicocca, * USI Università della Svizzera italiana, Switzerland Italy ESEC/FSE 2017

  2. Introduction Concurrent Programs are OUR GOAL everywhere, difficult to write and test Automated reproduction of concurrency failures manifested in the field Many concurrency bugs manifest in the field

  3. Reproducing Concurrency Failures Why is it important? Ease understanding and fixing the related concurrency fault Difficult problem! What is needed? A failure-inducing test code and thread interleaving runnable piece of code temporal order of that exercises the program shared memory under test accesses

  4. State of The Art Output Technique Input Test code Interleaving ODR [Altekar SOSP ’09] LEAP [Huang FSE ’10] CLAP [Huang PLDI ’13] CARE [Jiang ICSE ’14] Execution Cortex [Machado PPoPP ’16] trace STRIDE [Zhou ICSE ’12] ESD [Zamfir EuroSys ’10] Memory Weeratunge ASPLOS ‘10 core-dumps Privacy concerns Overhead issues Hard to obtain in the field

  5. State of The Art Output Technique Input Test code Interleaving ODR [Altekar SOSP ’09] LEAP [Huang FSE ’10] CLAP [Huang PLDI ’13] CARE [Jiang ICSE ’14] Execution Cortex [Machado PPoPP ’16] trace STRIDE [Zhou ICSE ’12] ESD [Zamfir EuroSys ’10] Memory Weeratunge ASPLOS ‘10 core-dumps ConCrash Crash stack (our contribution) Less privacy concerns No overhead issues Easily obtainable in the field

  6. ConCrash Targets Thread-safe Classes “A class that encapsulates synchronizations that ensure a correct behavior when the same instance of the class is accessed from multiple threads”

  7. Crash Stack type of exception Point Of Failure (POF) java.lang.NullPointerException at java.util.logging.Logger.log(Logger.java:421) at java.util.logging.Logger.doLog(Logger.java:458) at java.util.Logging.Logger.log(Logger.java:482) at java.util.logging.Logger.info(Logger.java:996)

  8. Example of Thread-safety Violation Thread 1 Thread 2 public void setFilter(Filter f) { public void log(LogRecord r) { this.filter = f; synchronized(this) { if(filter != null) { } if(!filter.isLoggable(r)) { = null return; } Point Of Failure (POF) } } } failure-inducing interleaving

  9. Concurrent Test Code Logger sout = Logger.getAnonymousLogger(); Sequential MyFilter myFilter0 = new MyFilter(); Prefix sout.setFilter(myFilter0); Thread 2 Thread 1 Concurrent sout.info(""); sout.setFilter(null); Suffixes Set of method call sequences that exercise the public interface of a class from multiple threads.

  10. Challenge Crash Stacks provides only limited information on how to generate a failure-inducing test code Crash Stack java.lang.NullPointerException at java.util.logging.Logger.log(Logger.java:421) at java.util.logging.Logger.doLog(Logger.java:458) at java.util.Logging.Logger.log(Logger.java:482) at java.util.logging.Logger.info(Logger.java:996) Crashing method and Class Under Test (CUT) Failure-inducing Test Code Logger sout = Logger.getAnonymousLogger(); Sequential MyFilter myFilter0 = new MyFilter(); Prefix sout.setFilter(myFilter0); CUT Thread 1 Thread 2 sout.info(""); sout.setFilter(null); Input Interfering Crashing Parameter Method Method

  11. Challenge Crash Stacks provides only limited information on how to generate a failure-inducing test code Crash Stack java.lang.NullPointerException at java.util.logging.Logger.log(Logger.java:421) at java.util.logging.Logger.doLog(Logger.java:458) at java.util.Logging.Logger.log(Logger.java:482) at java.util.logging.Logger.info(Logger.java:996) Implication: The search space of candidate Crashing method and Class Under Test (CUT) failure-inducing test codes is very huge Failure-inducing Test Code Logger sout = Logger.getAnonymousLogger(); Sequential MyFilter myFilter0 = new MyFilter(); Prefix sout.setFilter(myFilter0); CUT Thread 1 Thread 2 sout.info(""); sout.setFilter(null); Input Interfering Crashing Parameter Method Method

  12. ConCrash Failure-Inducing Test Code Crash Interleaving Test Code Concurrent & Stack Explorer Generator Test Code Interleaving [if failure not found] Pruning Strategies Avoid exploring the interleaving space of redundant and irrelevant test codes

  13. Test Code Generator Failure-Inducing Test Code Crash Interleaving Test Code Concurrent & Stack Explorer Generator Test Code Interleaving [if failure not found] • Build on top of AutoConTest [Terragni and Cheung ICSE ‘16] • Systematically explores test codes with fixed pool of input parameters • It performs state matching to prune redundant test codes.

  14. Pruning Strategies Failure-Inducing Test Code Crash Interleaving Test Code Concurrent & Stack Explorer Generator Test Code Interleaving [if failure not found] Pruning Strategies

  15. Pruning Strategies Rely on information obtained by executing the call sequences of a test code sequentially Low computational cost Good proxy Sequential Coverage (Terragni and Cheung ICSE ‘16) - write W(x) and read R(x) of shared memory x - lock acquire ACQ(l) and lock release REL(l) - method enter ENTER(m) and exit EXIT(m)

  16. Pruning Strategies (cont.) candidate test code CUT sout = new CUT(); sout.m1(); sout.m2(“hi”); Thread 2 Thread 1 Interfering Crashing Method Method sout.m3(5); sout.m4(10); CUT sout = new CUT(); CUT sout = new CUT(); sout.m1(); sout.m1(); sout.m2(“hi”); sout.m2(“hi”); sout.m3(5); sout.m4(10); … … REL(lock) REL(lock) EXIT(m2) EXIT(m2) ENTER(m4) ENTER(m3) Sequential Coverage ACQ(l) W(x) R(k) R(k) REL(l) EXIT(m3) EXIT(m4)

  17. Pruning Strategy : PS-Exception Prunes a candidate test code if one of its method call sequences throws an exception sequentially CUT sout = new CUT(); CUT sout = new CUT(); sout.m1(); sout.m1(); sout.m2(“hi”); sout.m2(“hi”); Crashing sout.m9(null); sout.m4(10); Method … … REL(lock) REL(lock) EXIT(m2) EXIT(m2) ENTER(m4) ENTER(m9) ACQ(l) R(x) R(k) java.lang.NullPointerException REL(l) EXIT(m4) Our focus are concurrent (not sequential) failures!

  18. Pruning Strategy : PS-Stack Prunes a candidate test code if the sequential coverage of the crashing method does not match the crash stack CUT sout = new CUT(); CUT sout = new CUT(); sout.m1(); sout.m1(); sout.m2(“hi”); sout.m2(“hi”); Crashing sout.m3(); sout.m4(10); Method … … REL(lock) REL(lock) EXIT(m2) EXIT(m2) Stack Trace ENTER(m4) ENTER(m3) MyException ACQ(l) ENTER(m8) at cut.m6() R(k) ENTER(m12) at cut.m8() REL(l) … at cut.m3() EXIT(m4)

  19. Pruning Strategy : PS-Redundant Prunes a candidate test code if the sequential coverages of the concurrent suffixes are redundant CUT sout = new CUT(); CUT sout = new CUT(); sout.m1(); sout.m1(); sout.m2(“hi”); sout.m2(“hi”); Interfering Crashing sout.m3(); sout.m4(10); Method Method … … REL(lock) REL(lock) EXIT(m2) EXIT(m2) Redundant? ENTER(m3) ENTER(m4) W(x) ACQ(l) R(k) R(k) EXIT(m3) REL(l) EXIT(m4) repository

  20. Pruning Strategy : PS-Interfere Prunes a candidate test code if the concurrent suffixes do not access (at least one write) the same shared memory location CUT sout = new CUT(); CUT sout = new CUT(); sout.m1(); sout.m1(); sout.m2(“hi”); sout.m2(“hi”); Interfering Crashing sout.m3(); sout.m4(10); Method Method … … REL(lock) REL(lock) EXIT(m2) EXIT(m2) ENTER(m4) ENTER(m3) ACQ(l) Shared memory accessed W(x) W(x) R(y) R(y) EXIT(m3) x y REL(l) EXIT(m4)

  21. Pruning Strategy : PS-Interleave Prunes a candidate test code if the concurrent suffixes are mutually exclusive CUT sout = new CUT(); CUT sout = new CUT(); sout.m1(); sout.m1(); sout.m2(“hi”); sout.m2(“hi”); Interfering Crashing sout.m1(); sout.m4(10); Method Method … … REL(lock) REL(lock) EXIT(m2) EXIT(m2) ENTER(m4) ENTER(m1) ACQ(l) ACQ(l) ACQ(l) ACQ(l ) Cannot interleave! R(x) R(x) W(x) REL(l) REL(l) REL(l) REL(l) EXIT(m4) EXIT(m1)

  22. Interleaving Explorer Failure-Inducing Test Code Crash Interleaving Test Code Concurrent & Stack Explorer Generator Test Code Interleaving [if failure not found] • Relies on Cortex [Machado et al. PPoPP’16] • Uses symbolic execution and constraint solving to identify failure inducing interleavings

  23. Evaluation RQ1: ConCrash effectiveness RQ2 : Contribution of each Pruning Strategy RQ3: Comparison with Testing Approaches

  24. Subjects 10 real, known and fixed concurrency faults of thread- safe classes in 5 popular codebases Crash Stack Class Under Test Code Base SLOC # Methods Type of Except. Depth PerUserPoolDataSource 719 68 ConcurrentModif. 4 Commons DBCP SharedPoolDataSource 546 44 ConcurrentModif. 4 IntRange Commons Math 278 44 AssertionError 1 BufferedInputStream 304 12 NullPointerExc. 2 Logger Java JDK 528 45 NullPointerExc. 4 PushbackReader 143 13 NullPointerExc. 1 NumberAxis 1,662 119 IllegalArgumentExc. 2 JFreeChart XYSeries 200 28 ConcurrentModif. 4 Category 387 43 NullPointerExc. 1 Log4j FileAppender 185 13 NullPointerExc. 2

Download Presentation
Download Policy: The content available on the website is offered to you 'AS IS' for your personal information and use only. It cannot be commercialized, licensed, or distributed on other websites without prior consent from the author. To download a presentation, simply click this link. If you encounter any difficulties during the download process, it's possible that the publisher has removed the file from their server.

Recommend


More recommend