1 / 38

Runtime Mutation of Commodity Operating System Kernels or Please, No More Rebooting!

Runtime Mutation of Commodity Operating System Kernels or Please, No More Rebooting!. Kyung Dong Ryu <kryu@us.ibm.com> IBM T.J. Watson Research Center Kristis Makris <kristis.makris@asu.edu> Arizona State University. IBM Research Worldwide. 2700 Researchers in eight labs around the world.

imala
Download Presentation

Runtime Mutation of Commodity Operating System Kernels or Please, No More Rebooting!

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Runtime Mutation of Commodity Operating System KernelsorPlease, No More Rebooting! Kyung Dong Ryu <kryu@us.ibm.com> IBM T.J. Watson Research Center Kristis Makris <kristis.makris@asu.edu> Arizona State University DynAMOS -- KOCSEA '08

  2. IBM Research Worldwide 2700 Researchers in eight labs around the world DynAMOS -- KOCSEA '08

  3. Culture of InnovationExternal Recognition Scanning Tunneling Microscope Copper Chip Technology Silicon-on-Insulator SiGe DRAM First woman recipient in the history of this prestigious ACM award High Performance Computing Nuclear Magnetic Resonance Techniques Basis for MRI today High Temperature Superconductivity Electron Tunneling Effect 5 Nobel Laureates 8 National Medals of Technology 5 National Medals of Science 6 Turing Awards • AAAS • ACM • ACS • APS • AVS • ECS • IEEE • IOP • OSA 21 Members in National Academy of Sciences More than 300 Professional Society Fellows 59 Members in National Academy of Engineering 10 Inductees in National Inventors Hall of Fame DynAMOS -- KOCSEA '08

  4. IBM Patent Leadership – 2006 DynAMOS -- KOCSEA '08

  5. Overview • Motivation • Dynamic Kernel Updates Categorization • System Architecture • Adaptive Function Cloning • Synchronized Updates • Applications • Conclusion DynAMOS -- KOCSEA '08

  6. Motivation • Dynamic kernel updates are essential • Existing updating methods are inadequate • Two approaches • Build adaptable OS • Specially crafted (K42, VINO, Synthetix) • Require OS and application restructuring • Dynamic code instrumentation • No kernel source modification (KernInst, GILK) • Basic block code interposition • Currently limited • No procedure replacement • No autonomous kernel adaptability • No safe, complete subsystem update guarantees DynAMOS -- KOCSEA '08

  7. Dynamic Updates Categorization (1) • Updating variable values • Update an entry in system call table • Update owner (uid) of an inode • Needs synchronized update • Count number of system calls of a process • Needs state tracking • Updating datatypes • Add new fields in Linux PCB for process checkpointing • Update all functions that use the old datatype, or • Maintain new fields in separate data structure • Does not need state transfer DynAMOS -- KOCSEA '08

  8. Dynamic Updates Categorization (2) • Updating single function • Correct a defect • Updating kernel threads • Update memory paging subsystem • Needs update during infinite loop • Updating function groups • Update pipefs subsystem • Needs synchronized update DynAMOS -- KOCSEA '08

  9. Our Approach • DynAMOS • Prototype for i386 Linux 2.2-2.6 • Dynamic code instrumentation • No kernel source modification or reboot • Procedure replacement • Adaptive updates • Concurrent execution of multiple versions • State tracking • Autonomous kernel adaptability • Safe updates of complete subsystems • Quiescence detection • Update synchronization (non-quiescent subsystems) • Datatype updates • State transfer DynAMOS -- KOCSEA '08

  10. update source insert module gcc ld make vmlinux kernel source new function images original function images object file DynAMOS System Architecture Unmodified kernel in memory DynAMOS -- KOCSEA '08

  11. DynAMOS kernel module new function images original function images DynAMOS System Architecture Unmodified kernel in memory load DynAMOS DynAMOS -- KOCSEA '08

  12. DynAMOS kernel module new function images original function images version manager /dev/dynamos DynAMOS System Architecture Unmodified kernel in memory initiate update Update tool DynAMOS -- KOCSEA '08

  13. cloned new function images DynAMOS kernel module new function images original function images disassembler version manager /dev/dynamos DynAMOS System Architecture Unmodified kernel in memory prepare update copy image relocation Update tool DynAMOS -- KOCSEA '08

  14. cloned new function images DynAMOS kernel module cloned new function images new function images original function images version manager /dev/dynamos DynAMOS System Architecture Unmodified kernel in memory Update tool DynAMOS -- KOCSEA '08

  15. DynAMOS kernel module cloned new function images new function images original function images version manager /dev/dynamos DynAMOS System Architecture Unmodified kernel in memory redirection activate update Update tool DynAMOS -- KOCSEA '08

  16. caller ... call schedule ... Execution Flow Redirection • Apply Linger-Longer scheduler • Unobtrusive fine-grain cycle stealing • Implemented in schedule_LL as a scheduling policy schedule step 1 DynAMOS -- KOCSEA '08

  17. caller ... call schedule ... schedule trampoline Execution Flow Redirection • Trampoline installation • Disable processor interrupts • Flush I-cache • Indirect jump • Don’t modify page permissions redirection handler jmp * step 2 DynAMOS -- KOCSEA '08

  18. caller ... call schedule ... preserve state perform bookkeeping execute adaptation handler restore state trampoline Execution Flow Redirection • Bookkeeping • Maintain use counters • User-defined adaptation handler • Execute if available • Select active version of function redirection handler call schedule adaptation handler ret step 2 DynAMOS -- KOCSEA '08

  19. caller ... call schedule ... schedule adaptation handler jump to active function trampoline Execution Flow Redirection redirection handler jmp * schedule_clone schedule_LL_clone step 3 DynAMOS -- KOCSEA '08

  20. caller ... call schedule ... schedule adaptation handler jump to active function trampoline jump back jump back Execution Flow Redirection redirection handler jmp * schedule_clone schedule_LL_clone step 4 DynAMOS -- KOCSEA '08

  21. caller ... call schedule ... schedule adaptation handler jump to active function preserve state perform bookkeeping restore state return to caller trampoline jump back jump back Execution Flow Redirection redirection handler ret schedule_clone schedule_LL_clone step 5 DynAMOS -- KOCSEA '08

  22. Adaptive Function Cloning Benefits • No processor state saved on stack • Function arguments accessed directly • Autonomous kernel determination of update timeliness • Using adaptation handler • Function-level updates • Basic blocks can be bypassed (no control-flow graph needed) • Function modifications developed in original source language DynAMOS -- KOCSEA '08

  23. Function Relocation Issues • Replace ret (1-byte) with jmp * (6-byte) back to handler • Adjust inbound (jmp) and outbound (call) relative offsets • Safely detect • Backward branches: jmp to code overwritten by trampoline • Outbound branches: jmp to code outside function image • Indirect outbound branches: jmp * from indirection table • Data-in-code • Need user verification • Multiple entry-points: e.g. produced by Intel C Compiler DynAMOS -- KOCSEA '08

  24. Overhead • Small memory footprint (42k) • Indirect addressing (jmp *) hurts branch prediction • Can use direct addressing (jmp) • Overhead not correlated to path length • Mostly 1-8% DynAMOS -- KOCSEA '08

  25. Quiescence Detection • Needed to • Atomically update function groups • e.g. Count number of processes using a filesystem • Safely reverse updates • Implemented by • Usage counters • On entry and exit • Stack walk-through • For non-returning calls (do_exit in Linux; no ret instruction) • Examine stack and program counter of all processes • Default kernel compilation (works without frame pointers) DynAMOS -- KOCSEA '08

  26. wait for new data in buffer wait for more room in buffer Non-quiescent Subsystems pipe_read() { ... acquire Sem while (buffer_empty) { ... release Sem L1: sleep acquire Sem } read from data buffer release Sem return } reader and writer are synchronized with each other pipe_write() { ... acquire Sem while (buffer_full) { ... release Sem L2: sleep acquire Sem } write in data buffer release Sem return } Adaptively enlarge pipefs 4k copy buffer during large data transfers DynAMOS -- KOCSEA '08

  27. non-quiescent; sleeping quiescent Non-quiescent Subsystems pipe_read() { ... acquire Sem while (buffer_empty) { ... release Sem L1: sleep acquire Sem } read from data buffer release Sem return } pipe_write() { ... acquire Sem while (buffer_full) { ... release Sem L2: sleep acquire Sem } write in data buffer release Sem return } subsystem may never quiesce cannot update atomically DynAMOS -- KOCSEA '08

  28. Synchronized update of pipefs pipe_read() { acquire Sem while (4k_buffer_empty) { release Sem L1: sleep acquire Sem } read data from 4k_buffer release Sem return } pipe_read_v3() { acquire Sem while (1mb_buffer_empty) { release Sem L1: sleep acquire Sem } read data from 1mb_buffer release Sem return } Phase 1 DynAMOS -- KOCSEA '08

  29. Synchronized update of pipefs pipe_read() { acquire Sem while (4k_buffer_empty) { release Sem L1: sleep acquire Sem } read data from 4k_buffer release Sem return } pipe_read_v2() { acquire Sem while (4k_buffer_empty) { release Sem L1: sleep acquire Sem if (must_update) { phase = 3 STATE TRANSFER goto new } } read data from 4k_buffer release Sem return new: } pipe_read_v3() { acquire Sem while (1mb_buffer_empty) { release Sem L1: sleep acquire Sem } read data from 1mb_buffer release Sem return } Semantically equivalent version at source code level Wait for pipe_read to become inactive Phase 2 DynAMOS -- KOCSEA '08

  30. Synchronized update of pipefs pipe_read() { acquire Sem while (4k_buffer_empty) { release Sem L1: sleep acquire Sem } read data from 4k_buffer release Sem return } pipe_read_v2() { acquire Sem while (4k_buffer_empty) { release Sem L1: sleep acquire Sem if (must_update) { phase = 3 STATE TRANSFER goto new } } read data from 4k_buffer release Sem return while (1mb_buffer_empty) { release Sem sleep acquire Sem new: } read data from 1mb_buffer release Sem return } pipe_read_v3() { acquire Sem while (1mb_buffer_empty) { release Sem L1: sleep acquire Sem } read data from 1mb_buffer release Sem return } Inline updated version Phase 2 DynAMOS -- KOCSEA '08

  31. Synchronized update of pipefs pipe_read() { acquire Sem while (4k_buffer_empty) { release Sem L1: sleep acquire Sem } read data from 4k_buffer release Sem return } pipe_read_v2() { acquire Sem while (4k_buffer_empty) { release Sem L1: sleep acquire Sem if (must_update) { phase = 3 STATE TRANSFER goto new } } read data from 4k_buffer release Sem return while (1mb_buffer_empty) { release Sem sleep acquire Sem new: } read data from 1mb_buffer release Sem return } pipe_read_v3() { acquire Sem while (1mb_buffer_empty) { release Sem L1: sleep acquire Sem } read data from 1mb_buffer release Sem return } Phase 3 DynAMOS -- KOCSEA '08

  32. Synchronized update of pipefs pipe_read_adaptation_handler() { if (phase == 3) activate pipe_read_v3 else activate pipe_read_v2 if (this process read more than 64k) must_update = 1 } Adaptive update 30-90% improvement in Linux 2.6 3.2% overhead when not adapting pipe_read_v2() { acquire Sem while (4k_buffer_empty) { release Sem L1: sleep acquire Sem if (must_update) { phase = 3 STATE TRANSFER goto new } } read data from 4k_buffer release Sem return while (1mb_buffer_empty) { release Sem sleep acquire Sem new: } read data from 1mb_buffer release Sem return } pipe_read_v3() { acquire Sem while (1mb_buffer_empty) { release Sem L1: sleep acquire Sem } read data from 1mb_buffer release Sem return } Sleep in original version Awake in new version Multi-phase approach Phase 3 DynAMOS -- KOCSEA '08

  33. Adaptive Memory Paging For Efficient Gang Scheduling • Kernel thread update (kswapd), Linux 2.2 • Infinite loop • Awaken by other subsystems • Goes back to sleep • e.g. calls interruptible_sleep_on in Linux • To update • Activate interruptible_sleep_on_v2 • Save state, exit • Start new version of kernel thread, restore state DynAMOS -- KOCSEA '08

  34. Kernel-Assisted Process Checkpointing • Datatype update for EPCKPT in Linux 2.4 • Compact datatypes in commodity kernel. No extra room • struct task_struct: semaphores, pipes, memory mapped files • struct file: checkpoint filename • Shadow data structures • Instantiation (do_fork, sys_open): map memory address of original variable to shadow using hash table • Removal (do_exit, fput): free shadow too • Already instantiated variables • Shadow missing: idempotent use of new fields • Update only functions that use new fields • No state transfer needed DynAMOS -- KOCSEA '08

  35. Related Work • K42 • Specially designed with hot-swappable capabilities • Guarantees quiescence • Ginseng • User-level software updates; requires recompilation • KernInst, GILK, Detours, ATOM, EEL • Do not facilitate adaptive execution • Do not safely replace complete subsystems DynAMOS -- KOCSEA '08

  36. On-going and Future Work • Automatically produce updates given a patch • Apply MOSIX, Superpages: parallel applications • Apply Nooks: OS reliability • Upgrade Linux kernel • Multiprocessor support • Safely install trampoline: freeze other processors using single-byte trap instruction (ud2) • Kernel module port • FreeBSD, OpenSolaris DynAMOS -- KOCSEA '08

  37. Conclusion • Dynamic Kernel Updates • Dynamic code instrumentation • Commodity operating system (prototype for i386 Linux 2.2-2.6) • Adaptive function cloning • Concurrent execution of multiple function versions • Safe updates of non-quiescent subsystems • Scheduler, kernel threads, synchronized updates • Datatype updates • Demonstrated updates • Synchronized pipefs adaptation, process checkpointing, adaptive memory paging for efficient gang-scheduling, unobtrusive fine-grain cycle stealing, public security fixes • Small memory footprint (42k), 1-8% overhead DynAMOS -- KOCSEA '08

  38. Questions ? DynAMOS -- KOCSEA '08

More Related