KEDR is an extensible system for dynamic analysis of Linux kernel modules (device drivers, file system modules, etc.). KEDR tools operate on the modules chosen by the user and can detect memory leaks, perform fault simulation and more.
This release provides several enhancements and various fixes compared to version 0.3. The most significant changes in this version:
- KEDR now supports kernel versions 3.3-3.6.
- LeakCheck has been redesigned: the analysis engine has been separated from data collection which makes the tool easier to maintain and to extend. The API it provides allows to use the memory leak detector in more cases than before.
- Handling of the information about signatures of the processed functions has been revisited to remove duplicate code and make the components involved easier to configure and to maintain.
- 12 more functions that allocate or deallocate memory are now processed, so are the functions kfree_rcu() expands to.
- Many fixes have been made in LeakCheck, fault simulation and other subsystems.
- Support for kernel version 2.6.31 has been dropped. The minimum supported kernel version is now 2.6.32.
KEDR is an extensible system for dynamic analysis of kernel modules (device drivers, file system modules, etc.) in Linux. KEDR tools operate on the modules chosen by the user and can detect memory leaks, perform fault simulation and more.
This release provides several enhancements and various fixes compared to version 0.2.1. The most significant changes:
- Handling of intercepted function calls has been revisited to allow doing several kinds of analysis at the same time (e.g. performing fault simulation and memory leak detection simultaneously).
- The components responsible for fault simulation are now decoupled from call monitoring (call tracing) facilities and can be used independently if necessary.
- Several enhancements and fixes have been applied to the trace capturing utility.
- Stack trace-related API has been revisited and simplified. If the kernel provides reliable stack traces, the API works now even if save_stack_trace() is not available.
- Handling of allocations and frees in the memory leak detector is now deferred via a work queue. This allows to significantly reduce the time spent with locks held.
KEDR is an extensible system for dynamic analysis of kernel modules (device drivers, file system modules, etc.) in Linux. KEDR tools operate on the modules chosen by the user and can detect memory leaks, perform fault simulation and more.
In version 0.2.1, the build system was enhanced. Now it allows building KEDR for a kernel different from the one running on the build machine. It is also possible to build KEDR for a different system (e.g. for Chromium OS, x86-generic). The details are in the Wiki:
http://openfacts2.berlios.de/wikien/index.php/BerliosProject:KEDR
KEDR is an extensible system for dynamic analysis of kernel modules (device drivers, file system modules, etc.) in Linux. KEDR tools operate on the modules chosen by the user and can detect memory leaks, perform fault simulation and more.
Version 0.2 brings several enhancements and various bug fixes.
Most significant changes:
- Tracing subsystem has been completely rewritten to be more versatile
and reliable even on SMP systems.
- A memory leak detector (LeakCheck) has been implemented.
- It is now possible to restrict fault simulation to particular areas
in the target module (if the kernel provides reliable stack traces).
- Several fixes have been made for KEDR to be able to work on the
versions 2.6.37 and 2.6.38 of the kernel.
- Call monitoring for 20 more functions is now supported. Support for
fault simulation for many of these functions as well as for vmalloc() group
has also been provided.
- The issues concerning parallel builds (make -j N) have been fixed.