Instructor: Ashvin Goel
Course Number: ECE1724H
Course Time: Mon, 2-4 pm (note the change in time)
Course Room: BA4164 (note the change in room)
Start Date: Sept 10, 2012

Accessing Papers
Presentation Format
Project Format
Project Ideas

Special Topics in Software Engineering: Dependable Systems

ECE1724, Fall 2012
University of Toronto

Course Description

Modern computer systems have become tightly intertwined with our daily lives. However, they are failure-prone and difficult to manage and thus hardly dependable. Today, these problems dominate total cost of ownership of computer systems, and unfortunately they have no simple solutions. There is a realization that these problems cannot be decisively solved but are ongoing facts of life that must be dealt with regularly. To do so, systems should be designed to detect, isolate and recover from these problems.

This advanced graduate-level course focuses on dependability in software systems and examines current research that aims to address challenges caused by software and hardware bugs and software misconfiguration. Students are expected to read and critique recent research papers in operating systems that cover these areas. They are also expected to work on a research project and make class presentations. While there are no specific prerequisites for this course, students who have taken undergraduate or graduate courses in operating systems, networks and distributed systems will have an edge.


There are no required textbooks for this course. The optional textbooks are

  • Modern Operating Systems (Third Edition), by Andrew S. Tanenbaum. Published by Prentice Hall, 2008.
  • Distributed Systems: Concepts and Design (Fourth Edition), by George Coulouris, Jean Dollimore and Tim Kindberg. Published by Addison Wesley, 2005.

Mailing List

Please subscribe to the class mailing list by joining the UofT ECE1724 Google group. Subscribing to the group may require the instructor's approval.

The instructor will use this group to send instructions and reminders. You can send email to the class by sending mail to this list. If you have a specific question for the instructor, please send an email to the instructor directly.

Grading Policy

Grades will be based on class presentations, a class project, and class participation. There will be no final exam in this course. The grading breakup is as follows:

  • Class presentation: 30%
  • Class project: 50%
  • Class participation: 20%

Note: If a student is unable to attend a class, he or she will lose 2% for non-participation.

Class Presentation

Each week this class will cover a group of papers that focuses on a specific aspect of the course. Students are expected to read all the papers in the group that will be presented. At the beginning of the term, each paper will be assigned to a student who will be presenting the paper. Presentations will be limited to roughly 20 minutes.

More details about the presentation format. Please read very carefully.


There will be no assignments in this course.

Class Project

A major component of this course is devoted to a term-long project. The topic of the project is largely up to you, but to help you choose a project, a sample list of projects is provided below. This list should help students determine whether their own projects are of reasonable size and scope.

More details about the project format. Please read very carefully.

Project Ideas

Here is a list of project ideas.


This is a tentative list. Most of these papers can be accessed from the ACM web site. If you cannot access ACM articles directly, please read the following instructions for accessing the papers.

Week 1: Introduction (Sept 10)

  1. Why Do Computers Stop and What Can Be Done About It? SRDS 1986.
  2. Broad New OS Research: Challenges and Opportunities. HOTOS 2005.
  3. Introduction to Dependable Software Systems by Instructor.
  4. Efficient Readings of Papers in Science and Technology.
  5. How (and How Not) to Write a Good Systems Paper. Operating Systems Review 1983.

Week 2: Detecting Races (Sept 17)

  1. Eraser: A Dynamic Data Race Detector for Multi-Threaded Programs. SOSP 1997. Dhaval
  2. Effective Data-Race Detection for the Kernel. OSDI 2010. Bozhidar

     Optional reading:

  1. RacerX: Effective, Static Detection of Race Conditions and Deadlocks. SOSP 2003.
  2. Bypassing Races in Live Applications with Execution Filters. OSDI 2010.
  3. Detecting and Surviving Data Races using Complementary Schedules. SOSP 2011.
  4. Pervasive Detection of Process Races in Deployed Systems. SOSP 2011.
  5. Automated Concurrency-Bug Fixing. OSDI 2012.

Week 3: More Races (Sept 24)

  1. Ad Hoc Synchronization Considered Harmful. OSDI 2010. Kush
  2. Data Races vs. Data Race Bugs: Telling the Difference with Portend. ASPLOS 2012. Shahriar
  3. Applying Transactional Memory to Concurrency Bugs. ASPLOS 2012. Bozhidar

     Optional reading:

  1. Finding and Reproducing Heisenbugs in Concurrent Programs. OSDI 2008.
  2. Deadlock Immunity: Enabling Systems to Defend Against Deadlocks. OSDI 2008.
  3. CTrigger: Exposing Atomicity Violation Bugs from Their Hiding Places. ASPLOS 2009.
  4. Operating Systems Transactions. SOSP 2009.
  5. A Randomized Scheduler with Probabilistic Guarantees of Finding Bugs. ASPLOS 2010.

Week 4: Detecting Bugs (Oct 1 - first report due)

  1. Bugs as Deviant Behavior: A General Approach to Inferring Errors in Systems Code. SOSP 2001. Miro
  2. Recon: Verifying File System Consistency at Runtime. FAST 2012. Venkatesh

     Optional reading:

  1. Using Model Checking to Find Serious File System Errors. OSDI 2004.
  2. eXplode: A lightweight, general system for finding serious storage system errors. OSDI 2006.
  3. Triage: Diagnosing Production Run Failures at the User's Site. SOSP 2007.
  4. Hang Analysis: Fighting Responsiveness Bugs. Eurosys 2008.

Week 5: No Class (Oct 8)

Instructor is at a conference.

Week 6: Testing and Debugging (Oct 15)

  1. ODR: Output-Deterministic Replay for Multicore Debugging. SOSP 2009. Jason
  2. Execution Synthesis: A Technique for Automated Software Debugging. Eurosys 2010. Rafat

     Optional reading:

  1. KLEE: Unassisted and Automatic Generation of High-Coverage Tests for Complex Systems Programs. OSDI 2008.
  2. R2: An Application-Level Kernel for Record and Replay. OSDI 2008.
  3. Anomaly-Based Bug Prediction, Isolation, and Validation: An Automated Approach for Software Debugging. ASPLOS 2009.
  4. SymDrive: Who Needs a Device to Test a Driver?. OSDI 2012.

Week 7: Fault Isolation (Oct 22)

  1. Efficient Software-Based Fault Isolation. SOSP 1993. Kush
  2. Fast Byte-granularity Software Fault Isolation. SOSP 2009. Alton
  3. Software fault isolation with API integrity and multi-principal modules. SOSP 2011. Khaled

      Optional reading:

  1. Hive: Fault Containment for Shared-Memory Multiprocessors. SOSP 1995.
  2. Dealing With Disaster: Surviving Misbehaved Kernel Extensions. OSDI 1996.
  3. Improving the Reliability of Commodity Operating Systems. SOSP 2003.
  4. CuriOS: Improving Reliability through Operating System Structure. OSDI 2008.

Week 8: Generic Failure Recovery (Oct 29 - second report due)

  1. Exploring Failure Transparency and the Limits of Generic Recovery. OSDI 2000. Miro
  2. Rx: Treating Bugs As Allergies---A Safe Method to Survive Software Failures. SOSP 2005. Hao
  3. ASSURE: Automatic Software Self-healing Using REscue points. ASPLOS 2009. Jason

      Optional reading:

  1. Enhancing Server Availability and Security Through Failure-Oblivious Computing. OSDI 2004.

Week 9: Storage Failure Recovery (Nov 5)

  1. Improving File System Reliability with I/O Shepherding. SOSP 2007. Henry
  2. Membrane: Operating System Support for Restartable File Systems. FAST 2010. Tianzheng

     Optional reading:

  1. Iron File Systems. SOSP 2005.
  2. Analyzing the effects of disk-pointer corruption. DSN 2008.
  3. Fast Crash Recovery in RAMCloud. SOSP 2011. Eunbyung

Week 10: Application and OS Failure Recovery (Nov 12)

  1. Undo for Operators: Building an Undoable E-mail Store. Usenix 2003. Hao
  2. Microreboot - A Technique for Cheap Recovery. OSDI 2004. Alton
  3. Recovery Domains: An Organizing Principle for Recoverable Operating Systems. ASPLOS 2009. Rafat

Week 11: Hardware Fault Tolerance (Nov 19)

  1. Hypervisor-based Fault-tolerance. SOSP 1995. Henry
  2. Remus: High Availability via Asynchronous Virtual Machine Replication. NSDI 2008. Venkatesh
  3. Tolerating Hardware Device Failures in Software. SOSP 2009. Tianzheng

Week 12: Updating Software (Nov 26)

  1. Dynamic and Adaptive Updates to Non-Quiescent Subsystems in Commodity Operating System Kernels. Eurosys 2007. Jack
  2. Ksplice: Automatic rebootless kernel updates. Eurosys 2009. Dhaval
  3. Automatically Patching Errors in Deployed Software. SOSP 2009. Shahriar

      Optional reading:

  1. DeVirtualizable Virtual Machines: Enabling General, Single-Node, Onine Maintenance. ASPLOS 2004.

Week 13: System Misconfiguration (Dec 3)

  1. Automating Configuration Troubleshooting with Dynamic Information Flow Analysis. OSDI 2010. Khaled
  2. Automatic Root-Cause Diagnosis of Performance Anomalies in Production Software. OSDI 2012. Jack

     Optional reading:

  1. Understanding and Dealing with Operator Mistakes in Internet Services. OSDI 2004.
  2. Configuration Debugging as Search: Finding the Needle in the Haystack. OSDI 2004.
  3. Automatic Misconfiguration Troubleshooting with PeerPressure. OSDI 2004.
  4. Staged Deployment in Mirage, an Integrated Software Upgrade Testing and Distribution System. SOSP 2007.
  5. AutoBash: Improving Configuration Management with Operating System Causality Analysis. SOSP 2007.
  6. Barricade: Defending Systems Against Operator Mistakes. Eurosys 2010.
  7. Fingerprinting the Datacenter: Automated Classification of Performance Crises. Eurosys 2010.
  8. An Empirical Study on Configuration Errors in Commercial and Open Source Systems. SOSP 2011.
  9. Enabling Configuration-Independent Automation by Non-Expert Users. OSDI 2010.
  10. Be Conservative: A Little Effort Now Can Save a Big Time Later in Failure Diagnosis. OSDI 2012.

Week 14: Project Presentations (Dec 10 - final report due)