pub/scm/linux/kernel/git/rostedt/linux-trace.git  about / heads / tags
Ftrace and kernel tracing repo
# tags:
$ git for-each-ref --sort=-creatordate refs/tags \
	--format='%(refname:short) %(subject) (%(creatordate:short))'
add-timer-shutdown As discussed here: (2022-11-06) tar.gz
trace-v6.0-rc4 Tracing fixes and updates for 6.0: (2022-09-08) tar.gz
trace-v6.0-rc2 Tracing: Fix for 6.0-rc2 (2022-08-23) tar.gz
trace-v6.0-rc1-2 Various fixes for tracing: (2022-08-21) tar.gz
trace-v6.0-rc1 Various fixes for tracing: (2022-08-21) tar.gz
trace-rtla-v6.0 Fixes for the RTLA tooling: (2022-08-18) tar.gz
trace-v6.0   Tracing updates for 5.20 / 6.0 (2022-08-05) tar.gz
trace-rtla-v5.20 Real Time Analysis Tool updates for 5.20 / 6.0 (2022-08-03) tar.gz
trace-v5.19-rc5 Fixes and minor clean ups for tracing: (2022-07-12) tar.gz
trace-v5.19-rc1 Tracing fixes: (2022-06-22) tar.gz
trace-tools-v5.19 Updates to Real Time Linux Analysis tool for 5.19: (2022-05-29) tar.gz
trace-v5.19  tracing updates for 5.19: (2022-05-29) tar.gz
trace-v5.18-2 Updates to Tracing: (2022-04-03) tar.gz
trace-v5.18-1 Trace event fix of string verifier (2022-03-24) tar.gz
trace-v5.18  Tracing updates for 5.18: (2022-03-21) tar.gz
trace-rtla-v5.18 Real Time Analysis Tool updates for 5.18 (2022-03-21) tar.gz
trace-v5.17-rc6 Minor tracing fixes: (2022-03-10) tar.gz
trace-v5.17-rc5 Two tracing fixes: (2022-03-05) tar.gz
trace-v5.17-rc4 Tracing fixes for 5.17: (2022-02-26) tar.gz
trace-v5.17-rc2 Tracing fixes: (2022-02-10) tar.gz
trace-v5.17-rc1 Tracing fixes for 5.17-rc1: (2022-01-28) tar.gz
trace-v5.17-3 ftrace: Fix s390 breakage from sorting mcount tables (2022-01-23) tar.gz
trace-v5.17-2 tracing/scripts: Possible uninitialized variable (2022-01-18) tar.gz
trace-v5.17  Tracing updates for 5.17: (2022-01-14) tar.gz
trace-v5.16-rc8 Three minor tracing fixes: (2022-01-06) tar.gz
trace-v5.16-rc4 tracing, ftrace and tracefs fixes: (2021-12-10) tar.gz
trace-v5.16-rc3 Three tracing fixes: (2021-12-01) tar.gz
trace-v5.16-rc2-3 tracing: Fix the fix of pid filtering (2021-11-28) tar.gz
trace-v5.16-rc2-2 Two fixes to event pid filtering: (2021-11-27) tar.gz
trace-v5.16-rc2 tracing: Fix wrong uprobe variable in iterator (2021-11-24) tar.gz
trace-v5.16-6 Tracing fixes: (2021-11-19) tar.gz
trace-v5.16-rc1 Fix double free bug in tracing histograms (2021-11-17) tar.gz
trace-v5.16-5 Update to tracing histogram variable string copy (2021-11-14) tar.gz
trace-v5.16-4 Three tracing fixes: (2021-11-13) tar.gz
trace-v5.16-3 Two tracing fixes: (2021-11-11) tar.gz
trace-v5.16-2 Second set of tracing updates for 5.16: (2021-11-03) tar.gz
trace-v5.16  Tracing updates for 5.16: (2021-11-01) tar.gz
trace-v5.15-rc6-3 Tracing comment fixes: (2021-10-29) tar.gz
trace-v5.15-rc6-2 Do not WARN when attaching event probe to non-existent event (2021-10-27) tar.gz
trace-v5.15-rc6 Fix nds32le build when DYNAMIC_FTRACE is disabled (2021-10-27) tar.gz
trace-v5.15-rc5 tracing recursion fix: (2021-10-19) tar.gz
trace-v5.15-rc3 Tracing fixes for 5.15: (2021-10-15) tar.gz
trace-v5.15-rc1 A couple of memory management fixes to the bootconfig code (2021-09-14) tar.gz
trace-v5.15-3 Minor fixes to the processing of the bootconfig tree. (2021-09-10) tar.gz
trace-v5.15-2 More tracing updates for 5.15: (2021-09-09) tar.gz
trace-v5.15  Tracing updates for 5.15: (2021-09-03) tar.gz
trace-v5.14-rc6 tracing: Limit the shooting in the foot of tp_printk (2021-08-17) tar.gz
trace-v5.14-rc5-2 Fixes and clean ups to tracing: (2021-08-12) tar.gz
trace-v5.14-rc5 Fixes and clean ups to tracing: (2021-08-12) tar.gz
trace-v5.14-rc4-2 Fix tracepoint race between static_call and callback data (2021-08-06) tar.gz
trace-v5.14-rc4 Various tracing fixes: (2021-08-05) tar.gz
trace-v5.14-rc2 Tracing fixes for 5.14-rc2: (2021-07-23) tar.gz
trace-v5.14-5 tracing: Fix the histogram logic from possibly crashing the kernel (2021-07-16) tar.gz
trace-v5.14-4 tracing: One fix in the histogram code and another take at the __string_len() macro (2021-07-15) tar.gz
trace-v5.14-3 tracing: Add __string_len() and __assign_str_len() helpers (2021-07-13) tar.gz
trace-v5.14-2 Tracing fix for histograms and a clean up in ftrace (2021-07-09) tar.gz
trace-v5.14  Tracing updates for 5.14: (2021-07-02) tar.gz
trace-v5.13-rc6 Tracing fixes for 5.13: (2021-06-18) tar.gz
trace-v5.13-rc5-2 Tracing fixes for 5.13: (2021-06-11) tar.gz
trace-v5.13-rc5 Tracing fixes for 5.13: (2021-06-09) tar.gz
trace-v5.13-rc1 tracing: Fix trace_check_vprintf() for %.*s (2021-05-14) tar.gz
trace-v5.13-2 tracing: Fix probes written to the set_ftrace_filter file (2021-05-06) tar.gz
trace-v5.13  tracing updates for 5.13 (2021-05-03) tar.gz
trace-v5.12-rc8 tracing: Fix tp_printk command line and trace events (2021-04-20) tar.gz
trace-v5.12-rc7 tracing/dynevent: Fix a memory link in dyn_event_release() (2021-04-13) tar.gz
trace-v5.12-rc5-2 Fix stack trace entry size to stop showing garbage (2021-04-02) tar.gz
trace-v5.12-rc5 Add check of order < 0 before calling free_pages() (2021-03-31) tar.gz
trace-v5.12-rc3 Fix workqueue trace event unsafe string reference (2021-03-19) tar.gz
trace-v5.12-rc1 Functional fixes: (2021-03-05) tar.gz
trace-v5.12-2 Tracing: Fixes for 5.12 (2021-02-25) tar.gz
trace-v5.12  Tracing updates for 5.12 (2021-02-21) tar.gz
trace-v5.11-rc7-2 tracing: Fix buffer overflow in trace event filter (2021-02-12) tar.gz
trace-v5.11-rc7 tracing: Fix output of top level event "enable" file (2021-02-08) tar.gz
trace-v5.11-rc5 Tracing fixes: (2021-02-02) tar.gz
trace-v5.11-rc3 Update bootconf scripts for tracing_on option (2021-01-14) tar.gz
trace-v5.11-rc2 Blacklist properly on all archs (2021-01-11) tar.gz
trace-v5.11  Tracing updates for 5.11 (2020-12-17) tar.gz
trace-v5.10-rc7 Fix userstacktrace option for instances (2020-12-07) tar.gz
trace-v5.10-rc6-bootconfig Have bootconfig size and checksum be little endian (2020-12-01) tar.gz
trace-v5.10-rc6 Tracing fixes for 5.10-rc6 (2020-12-01) tar.gz
trace-v5.10-rc3 Fix alignment of bootconfig (2020-11-13) tar.gz
trace-v5.10-rc2 Tracing fixes: (2020-11-05) tar.gz
trace-v5.10-rc1 Fix synthetic event "strcat" overrun (2020-10-28) tar.gz
trace-v5.10-3 ring-buffer fix (2020-10-23) tar.gz
trace-v5.10-2 Tracing: Fix mismatch section of adding early trace events (2020-10-16) tar.gz
trace-v5.10  Updates for tracing and bootconfig: (2020-10-15) tar.gz
trace-v5.9-rc6 Two tracing fixes: (2020-09-30) tar.gz
trace-v5.9-rc5-2 A couple of fixes for bootconfig (2020-09-23) tar.gz
trace-v5.9-rc5 Tracing fixes: (2020-09-21) tar.gz
trace-v5.9   Tracing updates for 5.9 (2020-08-07) tar.gz
trace-v5.8-rc2 tracing: Four small fixes (2020-06-25) tar.gz
trace-v5.8-rc1 A few fixes and small cleanups for tracing: (2020-06-19) tar.gz
trace-v5.8   Tracing updates for 5.8: (2020-06-09) tar.gz
trace-v5.7-rc5 Various tracing fixes: (2020-05-14) tar.gz
trace-v5.7-rc4 Tracing fixes to previous fixes: (2020-05-12) tar.gz
trace-v5.7-rc3 This includes the following tracing fixes: (2020-05-07) tar.gz
trace-v5.7-rc2 A few tracing fixes: (2020-04-23) tar.gz
trace-v5.7-rc1 This fixes a small race between allocating a snapshot buffer and setting the snapshot trigger. On a slow machine, the trigger can occur before the snapshot is allocated causing a warning to be displayed in the ring buffer, and no snapshot triggering. Reversing the allocation and the enabling of the trigger fixes the problem. (2020-04-15) tar.gz
trace-v5.7   New tracing features: (2020-04-04) tar.gz
trace-v5.6-rc4 Have ftrace lookup_rec() return a consistent record otherwise it can break live patching. (2020-03-11) tar.gz
trace-v5.6-rc2 Tracing updates: (2020-02-25) tar.gz
trace-v5.6-rc1 Various fixes: (2020-02-11) tar.gz
trace-v5.6-2 Tracing updates: (2020-02-05) tar.gz
trace-v5.5-rc7 Kprobe events added "ustring" to distinguish reading strings from kernel space or user space. But the creating of the event format file only checks for "string" to display string formats. "ustring" must also be handled. (2020-01-27) tar.gz
trace-v5.5-rc6-2 Various tracing fixes: (2020-01-23) tar.gz
trace-v5.5-rc5 Various tracing fixes: (2020-01-06) tar.gz
trace-v5.5-rc2 Various tracing fixes: (2019-12-21) tar.gz
trace-v5.5-3 This contains 3 changes: (2019-12-11) tar.gz
trace-v5.5-2 Two fixes and one patch that was missed: (2019-12-04) tar.gz
trace-v5.5   New tracing features: (2019-11-25) tar.gz
trace-v5.4-rc3-3 Two minor fixes: (2019-10-21) tar.gz
trace-v5.4-rc2 A few tracing fixes: (2019-10-13) tar.gz
trace-v5.4-3 A few more tracing fixes: (2019-09-29) tar.gz
trace-v5.4-2 Srikar Dronamraju fixed a bug in the newmulti probe code. (2019-09-25) tar.gz
trace-v5.4   Tracing updates: (2019-09-19) tar.gz
trace-v5.3-rc6 Small fixes and minor cleanups for Tracing (2019-08-31) tar.gz
trace-v5.3-rc2 Two minor fixes: (2019-07-31) tar.gz
trace-v5.3-2 Eiichi Tsukata found a small bug from the fixup of the stack code (2019-07-19) tar.gz
trace-v5.3   The main changes in this release include: (2019-07-17) tar.gz
trace-v5.2-rc5 This includes three fixes: (2019-07-03) tar.gz
trace-v5.2-rc4 This includes the following fixes: (2019-06-15) tar.gz
trace-v5.2-rc2 This fixes a memory leak from the error path in the event filter logic. (2019-05-28) tar.gz
trace-v5.2-rc1-2 Make the GCC 9 warning for sub struct memset go away. (2019-05-26) tar.gz
trace-v5.2-rc1 Tom Zanussi sent me some small fixes and cleanups to the histogram code and I forgot to incorporate them. (2019-05-24) tar.gz
trace-v5.2   The major changes in this tracing update includes: (2019-05-15) tar.gz
trace-v5.1-rc6 There tracing fixes: (2019-04-26) tar.gz
trace-5.1-rc3 Andy Lutomirski approached me to tell me that the syscall_get_arguments() implementation in x86 was horrible and gcc  certainly gets it wrong. He said that since the tracepoints only pass in 0 and 6 for i and n repectively, it should be optimized for that case. Inspecting the kernel, I discovered that all users pass in 0 for i and only one file passing in something other than 6 for the number of arguments. That code happens to be my own code used for the special syscall tracing. That can easily be converted to just using 0 and 6 as well, and only copying what is needed. Which is probably the faster path anyway for that case. (2019-04-05) tar.gz
trace-v5.1-rc2 Three small fixes: (2019-03-26) tar.gz
trace-v5.1-2 This contains a series of last minute clean ups, small fixes and error checks. (2019-03-15) tar.gz
trace-v5.1   The biggest change for this release is in the histogram code. (2019-03-10) tar.gz
trace-v5.0-pre One small fix and one clean up (2019-03-04) tar.gz
trace-v5.0-rc4-3 Two more tracing fixes (2019-02-15) tar.gz
trace-v5.0-rc4-2 Two more tracing fixes (2019-02-15) tar.gz
trace-v5.0-rc4 This fixes kprobes/uprobes dynamic processing of strings, where it processes the args but does not update the remaining length of the buffer that the string arguments will be placed in. It constantly passes in the total size of buffer used instead of passing in the remaining size of the buffer used. This could cause issues if the strings are larger than the max size of an event which could cause the strings to be written beyond what was reserved on the buffer. (2019-02-12) tar.gz
trace-v5.0-rc3 This has two fixes for uprobe code. (2019-02-06) tar.gz
trace-v5.0-rc1 Andrea Righi fixed a NULL pointer dereference in trace_kprobe_create() (2019-01-15) tar.gz
trace-v4.21-1 It appears that the zero-day bot did find a bug in my sh build. And that I didn't have the bad code in my config file when I cross compiled it, although there are a few other errors in sh that makes it not build for me, I missed that I added one more. (2019-01-03) tar.gz
trace-v4.21  Tracing changes for v4.21: (2018-12-28) tar.gz
trace-v4.20-rc6 While running various ftrace tests on new development code, the kmemleak detector found some allocations that were not freed correctly. (2018-12-11) tar.gz
trace-v4.20-rc5 This is a single commit that fixes a bug in uprobes SDT code due to a missing mutex protection. (2018-12-06) tar.gz
trace-v4.20-rc4 This includes two more fixes: (2018-11-29) tar.gz
trace-v4.20-rc3 While rewriting the function graph tracer, I discovered a design flaw that was introduced by a patch that tried to fix one bug, but by doing so created another bug. As both bugs corrupt the output (but they do not crash the kernel), I decided to fix the design such that it could have both bugs fixed. The original fix, fixed time reporting of the function graph tracer when doing a max_depth of one. This was code that can test how much the kernel interferes with userspace. But in doing so, it could corrupt the time keeping of the function profiler. (2018-11-27) tar.gz
trace-v4.20-rc1 Masami found a slight bug in his code where he transposed the arguments of a call to strpbrk. (2018-11-05) tar.gz
trace-v4.20  The biggest change here is the updates to kprobes (2018-10-30) tar.gz
trace-v4.19-rc8-3 Masami had a couple more fixes to the synthetic events. One was a proper error return value, and the other is for the self tests. (2018-10-30) tar.gz
trace-v4.19-rc8-2 Masami found some issues with the creation of synthetic events. The first two patches fix handling of unsigned type, and handling of a space before an ending semi-colon. (2018-10-19) tar.gz
trace-v4.19-rc8 This fixes two bugs: (2018-10-17) tar.gz
trace-v4.19-rc5 It was reported that trace_printk() was not reporting properly values that came after a dereference pointer. (2018-10-10) tar.gz
trace-v4.19-rc4 Vaibhav Nagarnaik found that modifying the ring buffer size could cause a huge latency in the system because it does a while loop to free pages without releasing the CPU (on non preempt kernels). In a case where there are hundreds of thousands of pages to free it could actually cause a system stall. A properly place cond_resched() solves this issue. (2018-09-18) tar.gz
trace-v4.19-rc3 This fixes an issue with the build system caused by a change that modifies CC_FLAGS_FTRACE. The issue is that it breaks the dependencies and causes "make targz-pkg" to rebuild the entire world. (2018-09-14) tar.gz
trace-v4.19-rc2 This fixes two bugs: (2018-09-06) tar.gz
trace-v4.19-1 Masami found an off by one bug in the code that keeps "notrace" functions from being traced by kprobes. During my testing, I found that there's places that we may want to add kprobes to notrace, thus we may end up changing this code before 4.19 is released. The history behind this change is that we found that adding kprobes to various notrace functions caused the kernel to crashed. We took the safe route and decided not to allow kprobes to trace any notrace function. But because notrace is added to functions that just cause weird side effects to the function tracer, but are still safe, preventing kprobes for all notrace functios may be too much of a big hammer. One such place is __schedule() is marked notrace, to keep function tracer from doing strange recursive loops when it gets traced with NEED_RESCHED set. With this change, one can not add kprobes to the scheduler. (2018-08-22) tar.gz
trace-v4.19  Updates for v4.19: (2018-08-20) tar.gz
trace-v4.18-rc6 Various fixes to the tracing infrastructure: (2018-07-26) tar.gz
trace-v4.18-rc3-3 Joel Fernandes asked to add a feature in tracing that Android had its own patch internally for. I took it back in 4.13. Now he realizes that he had a mistake, and swapped the values from what Android had. This means that the old Android tools will break when using a new kernel that has the new feature on it. (2018-07-13) tar.gz
trace-v4.18-rc3-2 This fixes a memory leak in the kprobe code. (2018-07-11) tar.gz
trace-v4.18-rc3 While cleaning out my INBOX, I found a few patches that were lost in the noise. These are minor bug fixes and clean ups. Those include: (2018-07-05) tar.gz
trace-v4.18-rc1 This contains a few fixes and a clean up. (2018-06-22) tar.gz
trace-v4.18  One new feature was added to ftrace, which is the trace_marker now supports triggers. For example: (2018-06-06) tar.gz
trace-v4.17-rc4-3 While writing selftests for a new feature, I triggered two existing bugs that deal with triggers and instances. (2018-05-29) tar.gz
trace-v4.17-rc5-vsprintf The memory barrier usage in updating the random ptr hash for %p in vsprintf is incorrect. Instead of adding the read memory barrier into vsprintf() which will cause a slight degradation to a commonly used function in the kernel just to solve a very unlikely race condition that can only happen at boot up, change the code from using a variable branch to a static_branch. Not only does this solve the race condition, it actually will improve the performance of vsprintf() by removing the conditional branch that is only needed at boot. (2018-05-16) tar.gz
trace-v4.17-rc4-2 Some of the ftrace internal events use a zero for a data size of a field event. This is increasingly important for the histogram trigger work that is being extended. (2018-05-15) tar.gz
trace-v4.17-rc4 Working on some new updates to trace filtering, I noticed that the regex_match_front() test was updated to be limited to the size of the pattern instead of the full test string. But as the test string is not guaranteed to be nul terminated, it still needs to consider the size of the test string. (2018-05-11) tar.gz
trace-v4.17-rc1-3 Some of the files in the tracing directory show file mode 0444 when they are writable by root. To fix the confusion, they should be 0644. Note, either case root can still write to them. (2018-05-04) tar.gz
trace-v4.17-rc1-2 Various fixes in tracing: (2018-05-02) tar.gz
trace-v4.17-rc1 Following tracing fixes: (2018-04-26) tar.gz
trace-v4.17-2 A few clean ups and bug fixes (2018-04-12) tar.gz
trace-v4.17  New features: (2018-04-09) tar.gz
trace-v4.16-rc4 The documentation for kprobe events says that symbol offets can take both a + and - sign to get to befor and after the symbol address. But in actuality, the code does not support the minus. This fixes that issue, and adds a few more selftests to kprobe events. (2018-03-23) tar.gz
trace-v4.16-rc1 Al Viro discovered some breakage with the parsing of the set_ftrace_filter as well as the removing of function probes. (2018-02-09) tar.gz
trace-v4.16  Mostly clean ups and small fixes (2018-02-01) tar.gz
trace-v4.15-rc9 With the new ORC unwinder, ftrace stack tracing became disfunctional. (2018-01-24) tar.gz
trace-v4.15-rc4-3 Two more small fixes (2018-01-19) tar.gz
trace-v4.15-rc4-2 This includes two fixes (2018-01-15) tar.gz
trace-v4.15-rc4 While doing tests on tracing over the network, I found that the packets were getting corrupted. In the process I found three bugs. One was the culprit, but the other two scared me. After deeper investigation, they were not as major as I thought they were, due to a signed compared to an unsigned that prevented a negative number from doing actual harm. (2017-12-27) tar.gz
trace-v4.15-rc1 Various fix ups. (2017-12-14) tar.gz
trace-v4.15  Tracing updates for 4.15: (2017-11-17) tar.gz
trace-v4.14-rc3 Testing a new trace event format, I triggered a bug by doing: (2017-10-17) tar.gz
trace-v4.14-rc1-3 Two updates. (2017-10-04) tar.gz
trace-v4.14-rc1-2 Stack tracing and RCU has been having issues with each other and lockdep has been pointing out constant problems. The changes have been going into the stack tracer, but it has been discovered that the problem isn't with the stack tracer itself, but it is with calling save_stack_trace() from within the internals of RCU. The stack tracer is the one that can trigger the issue the easiest, but examining the problem further, it could also happen from a WARN() in the wrong place, or even if an NMI happened in this area and it did an rcu_read_lock(). (2017-09-23) tar.gz
trace-v4.14-rc1 This includes 3 minor fixes. (2017-09-20) tar.gz
trace-v4.14  Nothing new in development for this release. These are mostly fixes that were found during development of changes for the next merge window and fixes that were sent to me late in the last cycle. (2017-09-08) tar.gz
trace-v4.13-rc3 Various bug fixes: (2017-08-24) tar.gz
trace-v4.13-rc1 Three minor updates (2017-07-21) tar.gz
trace-v4.13-2 A few more minor updates: (2017-07-13) tar.gz
trace-v4.13  The new features of this release: (2017-07-06) tar.gz
trace-v4.12-rc5 Two fixes: (2017-06-30) tar.gz
trace-v4.12-rc2 There's been a few memory issues found with ftrace. (2017-05-26) tar.gz
trace-v4.12-rc1 This fixes a bug caused by not cleaning up the new instance unique triggers when deleting an instance. It also creates a selftest that triggers that bug. (2017-05-20) tar.gz
trace-v4.12-3 This is a trivial patch that changes a check for a cpumask from a NULL pointer to using cpumask_available(), which will do the check. This is because cpumasks when not allocated are always set, and clang complains about it. (2017-05-09) tar.gz
trace-v4.12-2 These are three simple changes. (2017-05-08) tar.gz
trace-v4.12  New features for this release: (2017-05-02) tar.gz
trace-v4.11-rc5-5 While continuing my development, I uncovered two more small bugs. (2017-04-20) tar.gz
trace-v4.11-rc5-4 While testing my development branch, without the fix for the pid use after free bug, the selftest that Namhyung added triggers it. I figured it would be good to add the test for the bug after the fix, such that it does not exist without the fix. (2017-04-18) tar.gz
trace-v4.11-rc5-3 Namhyung Kim discovered a use after free bug. It has to do with adding a pid filter to function tracing in an instance, and then freeing the instance. (2017-04-18) tar.gz
trace-v4.11-rc5-2 While rewriting the function probe code, I stumbled over a long standing bug. This bug has been there sinc function tracing was added way back when. But my new development depends on this bug being fixed, and it should be fixed regardless as it causes ftrace to disable itself when triggered, and a reboot is required to enable it again. (2017-04-15) tar.gz
trace-v4.11-rc5 Wei Yongjun fixed a long standing bug in the ring buffer startup test. If for some unknown reason, the kthread that is created fails to be created, the return from kthread_create() is an PTR_ERR and not a NULL. The test incorrectly checks for NULL instead of an error. (2017-04-06) tar.gz
trace-v4.11-rc1 There was some breakage with the changes for jump labels in the 4.11 merge window. Namely powerpc broke as jump labels uses the two LSB bits as flags in initialization. A check was added to make sure that all jump label entries were 4 bytes aligned, but powerpc didn't work that way for modules. Adding an alignment in the module linker script appeared to be the best solution. (2017-03-05) tar.gz
trace-v4.11-2 Commit 79c6f448c8b79c ("tracing: Fix hwlat kthread migration") fixed a bug that was caused by a race condition in initializing the hwlat thread. When fixing this code, I realized that it should have been done differently. Instead of doing the rewrite and sending that to stable, I just sent the above commit to fix the bug that should be back ported. (2017-02-27) tar.gz
trace-v4.11  This release has no new tracing features, just clean ups, minor fixes and small optimizations. (2017-02-27) tar.gz
trace-v4.10-rc2-2 Simple fix of s/static struct __init/static __init struct/ (2017-02-02) tar.gz
trace-4.10-rc2 It was reported to me that the thread created by the hwlat tracer does not migrate after the first instance. I found that there was as small bug in the logic, and fixed it. It's minor, but should be fixed regardless. There's not much impact outside the hwlat tracer. (2017-01-31) tar.gz
trace-v4.10  This release has a few updates: (2016-12-15) tar.gz
trace-v4.9-rc5 Alexei discovered a race condition in modules failing to load that can cause a ftrace check to trigger and disable ftrace. This is because of the way modules are registered to ftrace. Their functions are loaded in the ftrace function tables but set to "disabled" since they are still in the process of being loaded by the module. After the module is finished, it calls back into the ftrace infrastructure to enable it. Looking deeper into the locations that access all the functions in the table, I found more locations that should ignore the disabled ones. (2016-11-15) tar.gz
trace-v4.9   This release cycle is rather small. Just a few fixes to tracing. (2016-10-05) tar.gz
trace-v4.8-rc7 Al Viro has been looking at the tracefs code, and has pointed out some issues. This contains one fix by me and one by Al. I'm sure that he'll come up with more but for now I tested these patches and they don't appear to have any negative impact on tracing. (2016-09-25) tar.gz
trace-v4.8-2 Luiz Capitulino noticed that the tick_stop tracepoint wasn't being parsed properly by the tracing user space tools. This was due to the TRACE_DEFINE_ENUM() being set to a define, when it should have been set to the enum itself. The define was of the MASK that used the BIT to shift. The BIT was the enum and by adding that, everything gets converted nicely. The MASK is still kept just in case it gets converted to an enum in the future. (2016-08-09) tar.gz
trace-v4.8-1 A few updates and fixes: (2016-08-03) tar.gz
trace-v4.8   This is mostly clean ups and small fixes. Some of the more visible changes are: (2016-07-26) tar.gz
trace-v4.7-rc3 Two fixes for the tracing system. (2016-06-20) tar.gz
trace-v4.7-3 Reviewing the selftest I recently submitted, I realize that the second part of it uses my old hack to get the PID of the spawned background tasks, which doesn't work for all shells, instead of the common use of $!. (2016-05-23) tar.gz
trace-v4.7-2 Three more changes. (2016-05-22) tar.gz
trace-v4.7   This includes two new updates for the ftrace infrastructure. (2016-05-18) tar.gz
trace-fixes-v4.6-rc7 Hao Qin reported an integer overflow possibility with signed and unsigned numbers in the ring-buffer code. (2016-05-16) tar.gz
trace-fixes-v4.6-rc6 Chunyu Hu noticed that if one writes into the trigger files within the ftrace subsystem of events that it can cause an oops. This file is only writable by root, but still is a bug that needs to be fixed. (2016-05-03) tar.gz
trace-v4.6   Nothing major this round. Mostly small clean ups and fixes. (2016-03-24) tar.gz
trace-fixes-v4.5-rc7 I previously sent a fix that prevents all trace events from being called if the current cpu is offline. But I forgot that in 3.18, we added lockdep checks to test RCU usage even when the event is disabled. Although there cannot be any bug when a cpu is going offline, we now get false warnings triggered by the added checks of the event being disabled. (2016-03-09) tar.gz
trace-fixes-v4.5-rc6 A feature was added in 4.3 that allowed users to filter trace points on a tasks "comm" field. But this prevented filtering on a comm field that is within a trace event (like sched_migrate_task). (2016-03-04) tar.gz
trace-fixes-v4.5-rc5-2 Another small bug reported to me by Chunyu Hu. (2016-02-25) tar.gz
trace-fixes-v4.5-rc5 Two more small fixes. (2016-02-22) tar.gz
trace-fixes-v4.5-rc4 This includes two fixes. (2016-02-16) tar.gz
trace-v4.5-rc1-2 A cleanup to the stack tracer broke stack tracing on s390. Here's a simple fix to correct that issue. (2016-02-01) tar.gz
trace-v4.5-rc1 This includes three minor fixes, mostly due to cut-and-paste issues. (2016-01-28) tar.gz
trace-v4.5   Not much new with tracing for this release. Mostly just clean ups and minor fixes. (2016-01-12) tar.gz
trace-v4.4-rc4-4 PeiyangX Qiu reported that if a module fails to load between calling ftrace_module_init() and do_init_module() that the allocations made in ftrace_module_init() will not be freed, resulting in a memory leak. (2016-01-07) tar.gz
trace-v4.4-rc4-3 Two more fixes. (2016-01-05) tar.gz
trace-v4.4-rc4-2 Russell King was reporting lots of warnings when he compiled his kernel with ftrace enabled. With some investigation it was discovered that it was his compile setup. He was using ccache with hard links, which allowed recordmcount to process the same .o twice. When this happens, recordmcount will detect that it was already done and give a warning about it. (2015-12-23) tar.gz
trace-v4.4-rc4 Russell King was reporting lots of warnings when he compiled his kernel with ftrace enabled. With some investigation it was discovered that it was his compile setup. He was using ccache with hard links, which allowed recordmcount to process the same .o twice. When this happens, recordmcount will detect that it was already done and give a warning about it. (2015-12-15) tar.gz
trace-v4.4-rc3 During the merge window I added a new file that is used to filter trace events on pids. It filters all events where only tasks with their pid in that file exists. It also handles the sched_switch and sched_wakeup trace events where the current task does not have its pid in the file, but the task either being switched to or awaken does. (2015-12-02) tar.gz
trace-v4.4-rc2 Found two minor bugs while doing development on the ring buffer code. (2015-11-25) tar.gz
trace-v4.4-2 This contains three more clean up patches. (2015-11-12) tar.gz
trace-v4.4   Most of the changes are clean ups and small fixes. Some of them have stable tags to them. I searched through my INBOX just as the merge window opened and found lots of patches to pull. I ran them through all my tests and they were in linux-next for a few days. (2015-11-06) tar.gz
trace-fixes-v4.3-rc6 Running tests on other changes, the system locked up due to lots of warnings. It was caused by the stack tracer triggering a warning about using rcu_dereference() when RCU was not watching. This can happen due to the fact that the stack tracer uses the function tracer to check each function, and there's functions that may be called and traced when RCU stopped watching. Namely when a function is called just before going idle or to userspace and after RCU stopped watching that current CPU. (2015-10-22) tar.gz
trace-v4.3   Mostly this is just clean ups and micro optimizations. (2015-09-04) tar.gz
trace-v4.2-rc2-fix3 Back in 3.16 the ftrace code was redesigned and cleaned up to remove the double iteration list (one for registered ftrace ops, and one for registered "global" ops), to just use one list. That simplified the code but also broke the function tracing filtering on pid. (2015-07-24) tar.gz
trace-v4.2-rc2-fix2 He Kuang noticed that the sample code using the trace_event helper function __get_dynamic_array_len() is broken. This only changes the sample code, and I'm pushing this now instead of later because I don't want others using the broken code as an example when using it for real. (2015-07-21) tar.gz
trace-v4.2-rc1-fix Fengguang Wu discovered a crash that happened to be because of the branch tracer (traces unlikely and likely branches) when enabled with certain debug options. (2015-07-12) tar.gz
trace-fixes-4.1 After fixing the previous filter issue reported by Vince Weaver, I could not come up with a situation where the operand counter (cnt) could go below zero, so I added a WARN_ON_ONCE(cnt < 0). Vince was able to trigger that warn on with his fuzzer test, but didn't have a filter input that caused it. (2015-06-26) tar.gz
trace-v4.2   This patch series contains several clean ups and even a new trace clock "monitonic raw". Also some enhancements to make the ring buffer even faster. But the biggest and most noticeable change is the renaming of the ftrace* files, structures and variables that have to deal with trace events. (2015-06-23) tar.gz
trace-fix-filter-4.1-rc8 Vince Weaver reported a warning when he added perf event filters into his fuzzer tests. There's a missing check of balanced operations when parenthesis are used, and this triggers a WARN_ON() and when reading the failure, the filter reports no failure occurred. (2015-06-17) tar.gz
trace-rb-bm-fix-4.1-rc7 Wang Long fixed a minor bug in the module parameter for the ring buffer benchmark, where the produce_fifo was being ignored and the producer thread's priority was being set with the consumer_fifo parameter. (2015-06-11) tar.gz
trace-fixes-v4.1-rc2 The newly added ftrace_print_array_seq() function had a bug in it. Luckily, the only user of it didn't make the 4.1 merge window. But the helper function should be fixed before 4.2 when the users start coming in. (2015-05-07) tar.gz
trace-v4.1-2 This adds three fixes for the tracing code. (2015-04-22) tar.gz
trace-v4.1   Some clean ups and small fixes, but the biggest change is the addition of the TRACE_DEFINE_ENUM() macro that can be used by tracepoints. (2015-04-13) tar.gz
trace-4.1-tracefs This adds the new tracefs file system. This has been in linux-next for more than one release, as I had it ready for the 4.0 merge window, but a last minute thing that needed to go into Linux first had to be done. That was that perf hard coded the file system number when reading /sys/kernel/debugfs/tracing directory making sure that the path had the debugfs mount # before it would parse the tracing file. This broke other use cases of perf, and the check is removed. (2015-04-13) tar.gz
trace-fixes-v4.0-rc4 The recursion code in the internals of the ftrace ring buffer requires using "preempt_disable_notrace". But it has been discovered that preempt_disable() is being used by this_cpu_read() in some architectures and trace_cpu_read() is part of the recursion protection of the ring buffer. The only reason this did not crash was due to the recursion protection in other parts of ftrace. But if there's a path that does some kind of function tracing without that protection, it will crash the kernel. (2015-03-19) tar.gz
trace-fixes-v4.0-rc2-2 This includes fixes for seq_buf_bprintf() truncation issue. It also contains fixes to ftrace when /proc/sys/kernel/ftrace_enabled and function tracing are started. Doing the following causes some issues: (2015-03-09) tar.gz
trace-fixes-v4.0-rc2 While working on merging seq_file and seq_buf code, I hit a bug and came down to a bug in seq_buf_printf(). This is suppose to be a all or nothing function. That is, either all of the string passed in is saved to the seq_buf buffer, or none of it. But due to the way vsnprintf() works in the kernel, if the line is truncated, the return value is the amount written to the buffer, including the '\0'. Then the test in seq_buf_printf() uses the returned length to see if it would fit in the buffer. It will, but it will also fill the buffer. The test to see if vsnprintf() overflowed or not is to see if the length returned is equal to or greater than the length of the buffer passed to it. Not just greater than. (2015-03-04) tar.gz
trace-v3.20  The updates included in this pull request for ftrace are: (2015-02-12) tar.gz
trace-fixes-v3.19-rc7 During testing Sedat Dilek hit a "suspicious RCU usage" splat that pointed out a real bug. During suspend and resume the tlb_flush tracepoint is called when the CPU is going offline. As the CPU has been noted as offline, RCU is ignoring that CPU, which means that it can not use RCU protected locks. When tracepoints are activated, they require RCU locking, and if RCU is ignoring a CPU that runs a tracepoint, there is a chance that the tracepoint could cause corruption. (2015-02-07) tar.gz
trace-sh-3.19 It's been reported that function tracing does not work on the sh architecture because gcc 4.8 for superH does not support -m32, and the script adds "-m32" when re-compiling the object files with the mcount locations. (2015-01-21) tar.gz
trace-fixes-v3.19-rc3 This holds a few fixes to the ftrace infrastructure as well as the mixture of function graph tracing and kprobes. (2015-01-15) tar.gz
trace-3.19-2 As the merge window is still open, and this code was not as complex as I thought it might be. I'm pushing this in now. (2014-12-15) tar.gz
trace-seq-buf-3.19-v2 This code is a fork from the trace-3.19 pull as it needed the trace_seq clean ups from that branch. (2014-12-12) tar.gz
trace-fixes-v3.18 Here's two fixes: (2014-12-12) tar.gz
trace-seq-buf-3.19 This code is a fork from the trace-3.19 pull as it needed the trace_seq clean ups from that branch. (2014-12-08) tar.gz
ftracetest-3.19 Updates for the ftrace self tests: (2014-12-08) tar.gz
trace-3.19   There was a lot of clean ups and minor fixes. One of those clean ups was to the trace_seq code. It also removed the return values to the trace_seq_*() functions and use trace_seq_has_overflowed() to see if the buffer filled up or not. This is similar to work being done to the seq_file code as well in another tree. (2014-12-08) tar.gz
trace-fixes-v3.18-rc5 While testing function triggers, I noticed that the stack trace trigger for functions was missing the function that caused the trigger as well as the parent function that called the triggered function. I use this feature a lot and never noticed this before. Then I realized that the difference was that I had CONFIG_FRAME_POINTERS enabled, which I don't on the production machines I'm debugging. (2014-11-21) tar.gz
trace-fixes-v3.18-rc4 Rabin Vincent found a way that tracing could cause an infinite loop in the kernel. The splice logic wants a full page from the ring buffer but the ring_buffer_wait() returns when there's any data in the ring buffer. The splice code would then continue the loop waiting for a full page. But if a full page never happens, the splice code will never sleep and just continue to loop. (2014-11-11) tar.gz
trace-seq-file-cleanup I'm looking to clean up the seq_file code and to eventually merge the trace_seq code with seq_file as well, since they basically do the same thing. (2014-11-05) tar.gz
ftracetest-3.18-rc1 Running the ftracetests on a machine that had the debugfs file system mounted in two locations caused the ftracetests to fail. This is because the ftracetests script does a grep of the /proc/mounts file to find where the debugfs file system is mounted. If it is mounted twice, then the grep returns two lines instead of just one. This causes the ftracetests to get confused and fail. (2014-11-03) tar.gz
trace-fixes-v3.18-rc1-2 ARM has system calls outside the NR_syscalls range, and the generic tracing system does not support that and without checks, it can cause an oops to be reported. (2014-10-30) tar.gz
trace-fixes-v3.18-rc1 Adding the new code for 3.19, I discovered a couple of minor bugs with the accounting of the ftrace_ops trampoline logic. One was that the old hash was not updated before calling the modify code for an ftrace_ops. The second bug was what let the first bug go unnoticed, as the update would check the current hash for all ftrace_ops (where it should only check the old hash for modified ones). This let things work when only one ftrace_ops was registered to a function, but could break if more than one was registered depending on the order of the look ups. (2014-10-27) tar.gz
trace-3.18-2 Seems that Peter Zijlstra added a new check that is making old code screem nasty warnings: (2014-10-09) tar.gz
ftracetest-3.18 This patch series starts a new selftests section in the tools/testing/selftest directory called "ftrace" that holds tests aimed at testing ftrace and subsystems that use ftrace (like kprobes). (2014-10-08) tar.gz
trace-3.18   This set has a few minor updates, but the big change is the redesign of the trampoline logic. (2014-10-06) tar.gz
trace-fixes-v3.17-rc7 While testing some new changes for 3.18, I kept hitting a bug every so often in the ring buffer. At first I thought it had to do with some of the changes I was working on, but then testing something else I realized that the bug was in 3.17 itself. I ran several bisects as the bug was not very reproducible, and finally came up with the commit that I could reproduce easily within a few minutes, and without the change I could run the tests over an hour without issue. The change fit the bug and I figured out a fix. That bad commit was: (2014-10-03) tar.gz
trace-fixes-v3.17-rc1-2 Josef Bacik found a bug in the ring_buffer_poll_wait() where the condition variable (waiters_pending) was set before being added to the poll queue via poll_wait(). This allowed for a small race window to happen where an event could come in, check the condition variable see it set to true, clear it, and then wake all the waiters. But because the waiter set the variable before adding itself to the queue, the waker could have cleared the variable after it was set and then miss waking it up as it wasn't added to the queue yet. (2014-08-26) tar.gz
trace-fixes-v3.17-rc1 The rewrite of the ftrace code that makes it possible to allow for separate trampolines had a design flaw with the interaction between the function and function_graph tracers. (2014-08-24) tar.gz
trace-ipi-tracepoints Nicolas Pitre added generic tracepoints for tracing IPIs and updated the arm and arm64 architectures. It required some minor updates to the generic tracepoint system, so it had to wait for me to implement them. (2014-08-08) tar.gz
trace-fixes-3.16 This contains a fix for two long standing bugs. Both of which are rarely ever hit, and requires the user to do something that users rarely do. It took a few special test cases to even trigger this bug, and one of them was just one test in the process of finishing up as another one started. (2014-08-07) tar.gz
trace-3.17-2 Oleg Nesterov did several clean ups with the tracing filter code. As he found some small bugs that went into 3.16, and these changes were based on that, I had to apply his changes to a separate branch than my main development branch. (2014-08-04) tar.gz
trace-3.17   This pull request has a lot of work done. The main thing is the changes to the ftrace function callback infrastructure. It's introducing a way to allow different functions to call directly different trampolines instead of all calling the same "mcount" one. (2014-08-04) tar.gz
trace-fixes-v3.16-rc6 Tony Luck found that using the "uptime" trace clock that uses jiffies as a counter was converted to nanoseconds (silly), and after 1 hour 11 minutes and 34 seconds, this monotonic clock would wrap, causing havoc with the tracing system and making the clock useless. (2014-07-21) tar.gz
trace-fixes-v3.16-rc5-v2 A few more fixes for ftrace infrastructure. (2014-07-15) tar.gz
trace-fixes-v3.16-rc5 Oleg Nesterov fixed a memory leak that happens if a user creates a tracing instance, sets up a filter in an event, and then removes that instance. The filter allocates memory that is never freed when the instance is destroyed. (2014-07-15) tar.gz
trace-fixes-v3.16-rc3 Oleg Nesterov found and fixed a bug in the perf/ftrace/uprobes code where running: (2014-07-02) tar.gz
trace-fixes-v3.16-rc1-v2 This includes three patches from Oleg Nesterov. The first is a fix to a race condition that happens between enabling/disabling syscall tracepoints and new process creations (the check to go into the ptrace path for a process can be set when it shouldn't, or not set when it should). Not a major bug but one that should be fixed and even applied to stable. (2014-06-22) tar.gz
trace-fixes-v3.16-rc1 This includes three patches from Oleg Nesterov. The first is a fix to a race condition that happens between enabling/disabling syscall tracepoints and new process creations (the check to go into the ptrace path for a process can be set when it shouldn't, or not set when it should). Not a major bug but one that should be fixed and even applied to stable. (2014-06-19) tar.gz
trace-3.16-2 One bug fix that goes back to 3.10. Accessing a non existent buffer if "possible cpus" is greater than actual CPUs (including offline CPUs). (2014-06-12) tar.gz
trace-3.16   Lots of tweaks, small fixes, optimizations, and some helper functions to help out the rest of the kernel to ease their use of trace events. (2014-06-09) tar.gz
trace-fixes-v3.15-rc4-v2 This contains two fixes. (2014-05-08) tar.gz
trace-fixes-v3.15-rc4 This is a long standing bug that causes bogus data to show up in the refcnt field of the module_refcnt tracepoint. It was introduced by a merge conflict resolution back in 2.6.35-rc days. (2014-05-08) tar.gz
trace-fixes-v3.15-rc3 This is a small fix where the trigger code used the wrong rcu_dereference(). It required rcu_dereference_sched() instead of the normal rcu_dereference(). It produces a nasty RCU lockdep splat due to the incorrect rcu notation. (2014-05-02) tar.gz
trace-fixes-v3.15-rc2 Takao Indoh reported that he was able to cause a ftrace bug while loading a module and enabling function tracing at the same time. (2014-04-28) tar.gz
trace-fixes-v3.15-rc1 This contains two fixes. (2014-04-17) tar.gz
trace-3.15-v2 This includes the final patch to clean up and fix the issue with the design of tracepoints and how a user could register a tracepoint and have that tracepoint not be activated but no error was shown. (2014-04-11) tar.gz
trace-3.15   Most of the changes were largely clean ups, and some documentation. But there were a few features that were added. (2014-04-01) tar.gz
trace-fixes-v3.14-rc7-v2 While on my flight to Linux Collaboration Summit, I was working on my slides for the event trigger tutorial. I booted a 3.14-rc7 kernel to perform what I wanted to teach and cut and paste it into my slides. When I tried the traceon event trigger with a condition attached to it (turns tracing on only if a field of the trigger event matches a condition set by the user), nothing happened. Tracing would not turn on. I stopped working on my presentation in order to find what was wrong. (2014-03-26) tar.gz
trace-fixes-v3.14-rc7 Vaibhav Nagarnaik discovered that since 3.10 a clean up patch made the array index in the trace event format bogus. He supplied an elegant solution that uses __stringify() and also removes the need for the event_storage and event_storage_mutex and also cuts off a few K of overhead from the trace events. (2014-03-20) tar.gz
trace-fixes-v3.14-rc5 In the past, I've had lots of reports about trace events not working. Developers would say they put a trace_printk() before and after the trace event but when they enable it (and the trace event said it was enabled) they would see the trace_printks but not the trace event. (2014-03-04) tar.gz
trace-fixes-v3.14-rc2 Two fixes in the tracing utility. (2014-02-15) tar.gz
trace-fixes-3.14 The first two patches fix the debugfs README file to reflect better the new features added to 3.14. (2014-01-27) tar.gz
trace-3.14   This pull request has a new feature to ftrace, namely the trace event triggers by Tom Zanussi. A trigger is a way to enable an action when an event is hit. The actions are: (2014-01-20) tar.gz
trace-fixes-v3.13-rc8 Al Viro has concerns with the trace_pipe release method calling __free_page() instead of using the generic_pipe_buf_release() which does a page_cache_release(). Looking at the differences between __free_page() and page_cache_release() I do not think there's a real issue here. But to be on the safe side, and at least to be symmetric with generic_pipe_buf_get(), this patch is fine to add. (2014-01-17) tar.gz
trace-fixes-v3.13-rc2 This fixes a long standing bug in the ftrace profiler. The problem is that the profiler only initializes the online CPUs, and not possible CPUs. This causes issues if the user takes CPUs online or offline while the profiler is running. (2013-12-17) tar.gz
trace-fixes-3.13-rc2 A regression showed up that there's a large delay when enabling all events. This was prevalent when FTRACE_SELFTEST was enabled which enables all events several times, and caused the system bootup to pause for over a minute. (2013-12-06) tar.gz
trace-fixes-v3.13-rc1 This includes two fixes. (2013-11-26) tar.gz
trace-3.13   This batch of changes is mostly clean ups and small bug fixes. The only real feature that was added this release is from Namhyung Kim, who introduced "set_graph_notrace" filter that lets you run the function graph tracer and not trace particular functions and their call chain. (2013-11-11) tar.gz
ftrace-urgent-3.12-v2 Dave Jones's trinity program was able to enable the function tracer from a normal user account via the perf syscall "perf_event_open()". When I was able to reproduce it with trinity, I was able to track down exactly how it happened. (2013-11-06) tar.gz
ftrace-urgent-3.12 Dave Jones's trinity program was able to enable the function tracer from a normal user account via the perf syscall "perf_event_open()". When I was able to reproduce it with trinity, I was able to track down exactly how it happened. (2013-11-06) tar.gz
trace-3.12   Not much changes for the 3.12 merge window. The major tracing changes are still in flux, and will have to wait for 3.13. (2013-09-08) tar.gz
trace-fixes-3.11-rc3 Oleg Nesterov has been working hard in closing all the holes that can lead to race conditions between deleting an event and accessing an event debugfs file. This included a fix to the debugfs system (acked by Greg Kroah-Hartman). We think that all the holes have been patched and hopefully we don't find more. I haven't marked all of them for stable because I need to examine them more to figure out how far back some of the changes need to go. (2013-08-05) tar.gz
trace-fixes-3.11-rc2 Oleg is working on fixing a very tight race between opening a event file and deleting that event at the same time (both must be done as root). (2013-07-26) tar.gz
trace-3.11-rc2 This contains fixes, optimizations and some clean ups (2013-07-22) tar.gz
trace-3.11   The majority of the changes here are cleanups for the large changes that were added to 3.10, which includes several bug fixes that have been marked for stable. (2013-07-05) tar.gz
trace-fixes-v3.10-rc5 Yoshihiro Yunomae fixed a regression in the output format when using one of the counter clocks. The new multibuffer code changed the trace_clock file to update the trace instances tr->clock_id but the actual traces still used the value from the obsolete global variable trace_clock_id. (2013-06-11) tar.gz
trace-fixes-v3.10-rc3-v3 This contains 4 fixes. (2013-06-06) tar.gz
trace-fixes-v3.10-rc3-v2 I was testing a config for one bug and triggered a livelock lockup. A NMI watchdog dump showed what was happening: (2013-05-29) tar.gz
trace-fixes-v3.10-rc3 Two more fixes: (2013-05-28) tar.gz
trace-fixes-v3.10-rc2 Masami Hiramatsu fixed another bug. This time returning a proper result in event_enable_func(). After checking the return status of try_module_get(), it returned the status of try_module_get(). But try_module_get() returns 0 on failure, which is success for event_enable_func(). (2013-05-22) tar.gz
trace-fixes-v3.10-rc1 This includes a fix to a memory leak when adding filters to traces. (2013-05-15) tar.gz
trace-fixes-v3.10 The majority of these changes are from Masami Hiramatsu bringing kprobes up to par with the latest changes to ftrace (multi buffering and the new function probes). (2013-05-10) tar.gz
trace-3.10   Tracing updates for Linux 3.10 (2013-04-29) tar.gz
trace-fixes-v3.9-rc-v3 Namhyung Kim found and fixed a bug that can crash the kernel by simply doing: echo 1234 | tee -a /sys/kernel/debug/tracing/set_ftrace_pid (2013-04-12) tar.gz
trace-fixes-3.9-rc-v2 Namhyung Kim fixed a long standing bug that can cause a kernel panic. If the function profiler fails to allocate memory for everything, it will do a double free on the same pointer which can cause a panic. (2013-04-10) tar.gz
trace-fixes-3.9-rc6 This includes three fixes. Two fix features added in 3.9 and one fixes a long time minor bug. (2013-04-08) tar.gz
ftrace-fixes-3.9-rc6 This includes three fixes. Two fix features added in 3.9 and one fixes a long time minor bug. (2013-04-08) tar.gz
trace-3.8-rc4-fix Kprobes now uses the function tracer if it can. That is, if a probe is placed on a function mcount/nop location, and the arch supports it, instead of adding a breakpoint, kprobes will register a function callback as that is much more efficient. (2013-01-21) tar.gz
trace-3.8-rc3-regression-fix The clean up patch commit 0fb9656d "tracing: Make tracing_enabled be equal to tracing_on" caused two regressions. (2013-01-14) tar.gz
trace-3.8-rc2-regression-fix commit 7bcfaf54f591a0775254c4ea679faf615152ee3a "tracing: Add trace_options kernel command line parameter" (2013-01-10) tar.gz
v3.8-rc2     Linux 3.8-rc2 (2013-01-02) tar.gz
v3.8-rc1     Linux 3.8-rc1 (2012-12-21) tar.gz
v3.7         Linux 3.7 (2012-12-10) tar.gz
v3.7-rc8     Linux 3.7-rc8 (2012-12-03) tar.gz
v3.7-rc7     Linux 3.7-rc7 (2012-11-25) tar.gz
v3.7-rc6     Linux 3.7-rc6 (2012-11-16) tar.gz
v3.7-rc5     Linux 3.7-rc5 (2012-11-11) tar.gz
v3.7-rc4     Linux 3.7-rc4 (2012-11-04) tar.gz
v3.7-rc3     Linux 3.7-rc3 (2012-10-28) tar.gz
v3.7-rc2     Linux 3.7-rc2 (2012-10-20) tar.gz
v3.7-rc1     Linux 3.7-rc1 (2012-10-14) tar.gz
v3.6         Linux 3.6 (2012-09-30) tar.gz
v3.6-rc7     Linux 3.6-rc7 (2012-09-23) tar.gz
v3.6-rc6     Linux 3.6-rc6 (2012-09-16) tar.gz
v3.6-rc5     Linux 3.6-rc5 (2012-09-08) tar.gz
v3.6-rc4     Linux 3.6-rc4 (2012-09-01) tar.gz
v3.6-rc3     Linux 3.6-rc3 (2012-08-22) tar.gz
v3.6-rc2     Linux 3.6-rc2 (2012-08-16) tar.gz
v3.6-rc1     Linux 3.6-rc1 (2012-08-02) tar.gz
v3.5         Linux 3.5 (2012-07-21) tar.gz
v3.5-rc7     Linux 3.5-rc7 (2012-07-14) tar.gz
v3.5-rc6     Linux 3.5-rc6 (2012-07-07) tar.gz
v3.5-rc5     Linux 3.5-rc5 (2012-06-30) tar.gz
v3.5-rc4     Linux 3.5-rc4 (2012-06-24) tar.gz
v3.5-rc3     Linux 3.5-rc3 (2012-06-16) tar.gz
v3.5-rc2     Linux 3.5-rc2 (2012-06-08) tar.gz
v3.5-rc1     Linux 3.5-rc1 (2012-06-02) tar.gz
v3.4         Linux 3.4 (2012-05-20) tar.gz
v3.4-rc7     Linux 3.4-rc7 (2012-05-12) tar.gz
v3.4-rc6     Linux 3.4-rc6 (2012-05-06) tar.gz
v3.4-rc5     Linux 3.4-rc5 (2012-04-29) tar.gz
v3.4-rc4     Linux 3.4-rc4 (2012-04-21) tar.gz
v3.4-rc3     Linux 3.4-rc3 (2012-04-15) tar.gz
v3.4-rc2     Linux 3.4-rc2 (2012-04-07) tar.gz
v3.4-rc1     Linux 3.4-rc1 (2012-03-31) tar.gz
v3.3         Linux 3.3 (2012-03-18) tar.gz
v3.3-rc7     Linux 3.3-rc7 (2012-03-10) tar.gz
v3.3-rc6     Linux 3.3-rc6 (2012-03-03) tar.gz
v3.3-rc5     Linux 3.3-rc5 (2012-02-25) tar.gz
v3.3-rc4     Linux 3.3-rc4 (2012-02-18) tar.gz
v3.3-rc3     Linux 3.3-rc3 (2012-02-08) tar.gz
v3.3-rc2     Linux 3.3-rc2 (2012-01-31) tar.gz
v3.3-rc1     Linux 3.3-rc1 (2012-01-19) tar.gz
v3.2         Linux 3.2 (2012-01-04) tar.gz
v3.2-rc7     Linux 3.2-rc7 (2011-12-23) tar.gz
v3.2-rc6     Linux 3.2-rc6 (2011-12-16) tar.gz
v3.2-rc5     Linux 3.2-rc5 (2011-12-09) tar.gz
v3.2-rc4     Linux 3.2-rc4 (2011-12-01) tar.gz
v3.2-rc3     Linux 3.2-rc3 (2011-11-23) tar.gz
v3.2-rc2     Linux 3.2-rc2 (2011-11-15) tar.gz
v3.2-rc1     Linux 3.2-rc1 (2011-11-07) tar.gz
v3.1         Linux v3.1 (2011-10-24) tar.gz
v3.1-rc10    Linux 3.1-rc10 (2011-10-17) tar.gz
v3.1-rc9     Linux 3.1-rc9 (2011-10-04) tar.gz
v3.1-rc8     Linux 3.1-rc8 (2011-09-27) tar.gz
v3.1-rc7     Linux 3.1-rc7 (2011-09-21) tar.gz
v3.1-rc6     Linux 3.1-rc6 (2011-09-12) tar.gz
v3.1-rc5     Linux 3.1-rc5 (2011-09-04) tar.gz
v3.0.4       This is the 3.0.4 stable release (2011-08-29) tar.gz
v3.1-rc4     Linux 3.1-rc4 (2011-08-28) tar.gz
v3.1-rc3     Linux 3.1-rc3 (2011-08-22) tar.gz
v3.0.3       This is the 3.0.3 stable release (2011-08-17) tar.gz
v3.0.2       This is the 3.0.2 stable release (2011-08-15) tar.gz
v3.1-rc2     Linux 3.1-rc2 (2011-08-14) tar.gz
v3.1-rc1     Linux 3.1-rc1 (2011-08-07) tar.gz
v3.0.1       This is the 3.0.1 stable release (2011-08-04) tar.gz
v3.0         Linux 3.0 (2011-07-21) tar.gz
v3.0-rc7     Linux 3.0-rc7 (2011-07-11) tar.gz
v3.0-rc6     Linux 3.0-rc6 (2011-07-04) tar.gz
v3.0-rc5     Linux 3.0-rc5 (2011-06-27) tar.gz
v3.0-rc4     Linux 3.0-rc4 (2011-06-20) tar.gz
v3.0-rc3     Linux 3.0-rc3 (2011-06-13) tar.gz
v3.0-rc2     Linux 3.0-rc2 (2011-06-06) tar.gz
v3.0-rc1     Linux 3.0-rc1 (2011-05-29) tar.gz
v2.6.39      Linux 2.6.39 (2011-05-18) tar.gz
v2.6.39-rc7  Linux 2.6.39-rc7 (2011-05-09) tar.gz
v2.6.39-rc6  Linux 2.6.39-rc6 (2011-05-03) tar.gz
v2.6.39-rc5  Linux 2.6.39-rc5 (2011-04-26) tar.gz
v2.6.39-rc4  Linux 2.6.39-rc4 (2011-04-18) tar.gz
v2.6.39-rc3  Linux 2.6.39-rc3 (2011-04-11) tar.gz
v2.6.39-rc2  Linux 2.6.39-rc2 (2011-04-05) tar.gz
v2.6.33.9-rt31 v2.6.33.9-rt31 (2011-04-04) tar.gz
v2.6.39-rc1  Linux 2.6.39-rc1 (2011-03-29) tar.gz
v2.6.33.9    This is the stable release (2011-03-28) tar.gz
v2.6.33.8    This is the stable release (2011-03-21) tar.gz
v2.6.38      Linux 2.6.38 (2011-03-14) tar.gz
v2.6.38-rc8  Linux 2.6.38-rc8 (2011-03-07) tar.gz
v2.6.38-rc7  Linux 2.6.38-rc7 (2011-03-01) tar.gz
v2.6.38-rc6  Linux 2.6.38-rc6 (2011-02-21) tar.gz
v2.6.38-rc5  Linux 2.6.38-rc5 (2011-02-15) tar.gz
v2.6.38-rc4  Linux 2.6.38-rc4 (2011-02-07) tar.gz
v2.6.38-rc3  Linux 2.6.38-rc3 (2011-02-01) tar.gz
v2.6.38-rc2  Linux 2.6.38-rc2 (2011-01-21) tar.gz
v2.6.38-rc1  Linux 2.6.38-rc1 (2011-01-18) tar.gz
v2.6.37      Linux 2.6.37 (2011-01-04) tar.gz
v2.6.37-rc8  Linux 2.6.37-rc8 (2010-12-28) tar.gz
v2.6.37-rc7  Linux 2.6.37-rc7 (2010-12-21) tar.gz
v2. v2. (2010-12-21) tar.gz
v2.6.37-rc6  Linux 2.6.37-rc6 (2010-12-15) tar.gz
v2.6.37-rc5  Linux 2.6.37-rc5 (2010-12-06) tar.gz
v2.6.37-rc4  Linux 2.6.37-rc4 (2010-11-29) tar.gz
v2.6.37-rc3  Linux 2.6.37-rc3 (2010-11-21) tar.gz
v2.6.37-rc2  Linux 2.6.37-rc2 (2010-11-15) tar.gz
v2.6.37-rc1  Linux 2.6.37-rc1 (2010-11-01) tar.gz
v2.6.36      Linux 2.6.36 (2010-10-20) tar.gz
v2.6.36-rc8  Linux 2.6.36-rc8 (2010-10-14) tar.gz
v2.6.36-rc7  Linux 2.6.36-rc7 (2010-10-06) tar.gz
v2.6.36-rc6  Linux 2.6.36-rc6 (2010-09-28) tar.gz
v2.6.36-rc5  Linux 2.6.36-rc5 (2010-09-20) tar.gz
v2.6.36-rc4  Linux 2.6.36-rc4 (2010-09-12) tar.gz
v2.6.36-rc3  Linux 2.6.36-rc3 (2010-08-29) tar.gz
v2.6.36-rc2  Linux 2.6.36-rc2 (2010-08-22) tar.gz
v2.6.36-rc1  Linux 2.6.36-rc1 (2010-08-15) tar.gz
v2.6.33.7-rt29 v2.6.33.7-rt29 (2010-08-03) tar.gz
v2.6.33.7    This is the stable release (2010-08-02) tar.gz
v2.6.33.6-rt28 v2.6.33.6-rt28 (2010-08-02) tar.gz
v2.6.35      Linux 2.6.35 (2010-08-01) tar.gz
v2.6.33.6-rt27 v2.6.33.6-rt27 (2010-07-31) tar.gz
v2.6.35-rc6  Linux 2.6.35-rc6 (2010-07-22) tar.gz
v2.6.33.6-rt26 v2.6.33.6-rt26 (2010-07-13) tar.gz
v2.6.33.5-rt25 v2.6.33.5-rt25 (2010-07-13) tar.gz
v2.6.33.5-rt24 v2.6.33.5-rt24 (2010-07-13) tar.gz
v2.6.35-rc5  Linux 2.6.35-rc5 (2010-07-12) tar.gz
v2.6.33.6    This is the stable release (2010-07-05) tar.gz
v2.6.35-rc4  Linux 2.6.35-rc4 (2010-07-04) tar.gz
v2.6.35-rc3  Linux 2.6.35-rc3 (2010-06-11) tar.gz
v2.6.33.5-rt23 v2.6.33.5-rt23 (2010-06-09) tar.gz
v2.6.35-rc2  Linux 2.6.35-rc2 (2010-06-05) tar.gz
v2.6.33.5-rt22 v2.6.33.5-rt22 (2010-05-31) tar.gz
v2.6.33.4-rt21 v2.6.33.4-rt21 (2010-05-31) tar.gz
v2.6.35-rc1  Linux 2.6.35-rc1 (2010-05-30) tar.gz
v2.6.33.5    This is the stable release (2010-05-26) tar.gz
v2.6.33.4-rt20 v2.6.33.4-rt20 (2010-05-17) tar.gz
v2.6.34      Linux 2.6.34 (2010-05-16) tar.gz
v2.6.33.4    This is the stable release (2010-05-12) tar.gz
v2.6.34-rc7  Linux 2.6.34-rc7 (2010-05-09) tar.gz
v2.6.33.3-rt19 v2.6.33.3-rt19 (2010-05-02) tar.gz
v2.6.33.3-rt18 v2.6.33.3-rt18 (2010-05-02) tar.gz
v2.6.33.3-rt17 v2.6.33.3-rt17 (2010-04-30) tar.gz
v2.6.34-rc6  Linux 2.6.34-rc6 (2010-04-29) tar.gz
v2.6.33.3-rt16 v2.6.33.3-rt16 (2010-04-27) tar.gz
v2.6.33.3-rt15 v2.6.33.3-rt15 (2010-04-27) tar.gz
v2.6.33.3-rt14 v2.6.33.3-rt14 (2010-04-27) tar.gz
v2.6.33.3    This is the stable release (2010-04-26) tar.gz
v2.6.34-rc5  Linux 2.6.34-rc5 (2010-04-19) tar.gz
v2.6.34-rc4  Linux 2.6.34-rc4 (2010-04-12) tar.gz
v2.6.33.2-rt13 v2.6.33.2-rt13 (2010-04-07) tar.gz
v2.6.33.2-rt12 v2.6.33.2-rt12 (2010-04-02) tar.gz
v2.6.33.2    This is the stable release (2010-04-01) tar.gz
v2.6.34-rc3  Linux 2.6.34-rc3 (2010-03-30) tar.gz
v2.6.33.1-rt11 v2.6.33.1-rt11 (2010-03-21) tar.gz
v2.6.34-rc2  Linux 2.6.34-rc2 (2010-03-19) tar.gz
v2.6.33.1-rt10 v2.6.33.1-rt10 (2010-03-17) tar.gz
v2.6.33.1-rt9 v2.6.33.1-rt9 (2010-03-16) tar.gz
v2.6.33-rt8  v2.6.33-rt8 (2010-03-16) tar.gz
v2.6.33.1    This is the stable release (2010-03-15) tar.gz
v2.6.33-rt7  v2.6.33-rt7 (2010-03-12) tar.gz
v2.6.33-rt6  v2.6.33-rt6 (2010-03-12) tar.gz
v2.6.33-rt5  v2.6.33-rt5 (2010-03-12) tar.gz
v2.6.34-rc1  Linux 2.6.34-rc1 (2010-03-08) tar.gz
v2.6.33-rt4  v2.6.33-rt4 (2010-02-27) tar.gz
v2.6.33-rt3  v2.6.33-rt3 (2010-02-26) tar.gz
v2.6.33      Linux 2.6.33 (2010-02-24) tar.gz
v2.6.33-rc8-rt2 v2.6.33-rc8-rt2 (2010-02-24) tar.gz
v2.6.33-rc8-rt1 v2.6.33-rc8-rt1 (2010-02-21) tar.gz
v2.6.31-rt-head 2.6.31-rt head marker (2010-02-20) tar.gz
v2.6.31.12-rt21 v2.6.31.12-rt21 (2010-02-18) tar.gz
v2.6.33-rc8  Linux 2.6.33-rc8 (2010-02-12) tar.gz
v2.6.33-rc7  Linux 2.6.33-rc7 (2010-02-06) tar.gz
v2.6.33-rc6  Linux 2.6.33-rc6 (2010-01-29) tar.gz
v2.6.33-rc5  Linux 2.6.33-rc5 (2010-01-21) tar.gz
v2.6.31.12-rt20 v2.6.31.12-rt20 (2010-01-21) tar.gz
v2.6.31.12   This is the stable release (2010-01-18) tar.gz
v2.6.33-rc4  Linux 2.6.33-rc4 (2010-01-12) tar.gz
v2.6.31.11   This is the stable release (2010-01-07) tar.gz
v2.6.31.10   This is the stable release (2010-01-06) tar.gz
v2.6.33-rc3  Linux 2.6.33-rc3 (2010-01-05) tar.gz
v2.6.33-rc2  Linux 2.6.33-rc2 (2009-12-24) tar.gz
v2.6.31.9    This is the stable release (2009-12-18) tar.gz
v2.6.33-rc1  Linux 2.6.33-rc1 (2009-12-17) tar.gz
v2.6.31.8    This is the stable release (2009-12-14) tar.gz
v2.6.31.7    This is the stable release (2009-12-08) tar.gz
v2.6.32      Linux 2.6.32 (2009-12-02) tar.gz
v2.6.32-rc8  Linux 2.6.32-rc8 (2009-11-19) tar.gz
v2.6.32-rc7  Linux 2.6.32-rc7 (2009-11-12) tar.gz
v2.6.31.6-rt19 v2.6.31.6-rt19 (2009-11-10) tar.gz
v2.6.31.6    This is the stable release (2009-11-09) tar.gz
v2.6.31.5-rt18 v2.6.31.5-rt18 (2009-11-06) tar.gz
v2.6.31.5-rt17 v2.6.31.5-rt17 (2009-11-06) tar.gz
v2.6.32-rc6  Linux 2.6.32-rc6 (2009-11-03) tar.gz
v2.6.31.5    This is the stable release (2009-10-22) tar.gz
v2.6.31.4-rt15 v2.6.31.4-rt15 (2009-10-20) tar.gz
v2.6.32-rc5  Linux 2.6.32-rc5 (2009-10-15) tar.gz
v2.6.31.4-rt14 v2.6.31.4-rt14 (2009-10-14) tar.gz
v2.6.31.4    This is the stable release (2009-10-12) tar.gz
v2.6.32-rc4  Linux 2.6.32-rc4 (2009-10-11) tar.gz
v2.6.31.3    This is the stable release (2009-10-07) tar.gz
v2.6.31.2-rt13 v2.6.31.2-rt13 (2009-10-06) tar.gz
v2.6.31.1-rt12 v2.6.31.1-rt12 (2009-10-06) tar.gz
v2.6.31.2    This is the stable release (2009-10-05) tar.gz
v2.6.32-rc3  Linux 2.6.32-rc3 (2009-10-04) tar.gz
v2.6.32-rc1  Linux 2.6.32-rc1 (2009-09-27) tar.gz
v2.6.32-rc2  Linux 2.6.32-rc1 (2009-09-27) tar.gz
v2.6.31.1    This is the stable release (2009-09-24) tar.gz
v2.6.31-rt11 v2.6.31-rt11 (2009-09-18) tar.gz
v2.6.31-rt10 v2.6.31-rt10 (2009-09-15) tar.gz
v2.6.31      Linux 2.6.31 (2009-09-09) tar.gz
v2.6.31-rc9  Linux 2.6.31-rc9 (2009-09-05) tar.gz
v2.6.31-rc8-rt9 v2.6.31-rc8-rt9 (2009-08-28) tar.gz
v2.6.31-rc8  Linux 2.6.31-rc8 (2009-08-27) tar.gz
v2.6.31-rc7-rt8 v2.6.31-rc7-rt8 (2009-08-26) tar.gz
v2.6.31-rc7-rt7 v2.6.31-rc7-rt7 (2009-08-25) tar.gz
v2.6.31-rc7  Linux 2.6.31-rc7 (2009-08-21) tar.gz
v2.6.31-rc6-rt6 v2.6.31-rc6-rt6 (2009-08-21) tar.gz
v2.6.31-rc6-rt5 v2.6.31-rc6-rt5 (2009-08-19) tar.gz
v2.6.31-rc6-rt4 v2.6.31-rc6-rt4 (2009-08-18) tar.gz
v2.6.31-rc6-rt3 v2.6.31-rc6-rt3 (2009-08-17) tar.gz
v2.6.31-rc6-rt2 v2.6.31-rc6-rt2 (2009-08-16) tar.gz
v2.6.31-rc6  Linux 2.6.31-rc6 (2009-08-13) tar.gz
v2.6.31-rc5  Linux 2.6.31-rc5 (2009-07-31) tar.gz
v2.6.31-rc4  Linux 2.6.31-rc4 (2009-07-22) tar.gz
v2.6.31-rc3  Linux 2.6.31-rc3 (2009-07-13) tar.gz
v2.6.31-rc2  Linux 2.6.31-rc2 (2009-07-04) tar.gz
v2.6.29.6    This is the stable release (2009-07-02) tar.gz
v2.6.31-rc1  Linux 2.6.31-rc1 (2009-06-24) tar.gz
v2.6.29.5    This is the stable release (2009-06-15) tar.gz
v2.6.30      Linux 2.6.30 (2009-06-09) tar.gz
v2.6.30-rc8  Linux 2.6.30-rc8 (2009-06-02) tar.gz
v2.6.30-rc7  Linux 2.6.30-rc7 (2009-05-23) tar.gz
v2.6.29.4    This is the stable release (2009-05-18) tar.gz
v2.6.30-rc6  Linux 2.6.30-rc6 (2009-05-15) tar.gz
v2.6.30-rc5  Linux 2.6.30-rc5 (2009-05-08) tar.gz
v2.6.29.3    This is the stable release (2009-05-08) tar.gz
v2.6.30-rc4  Linux 2.6.30-rc4 (2009-04-29) tar.gz
trace-kconfig-20090430-144827 kconfig: add make localyesconfig option (2009-04-29) tar.gz
v2.6.29.2    This is the stable release (2009-04-27) tar.gz
v2.6.30-rc3  Linux 2.6.30-rc3 (2009-04-21) tar.gz
v2.6.30-rc2  Linux 2.6.30-rc2 (2009-04-14) tar.gz
v2.6.30-rc1  Linux 2.6.30-rc1 (2009-04-07) tar.gz
v2.6.29.1    This is the stable release (2009-04-02) tar.gz
trace-rfc-tip-tracing-function-profiler-20090325-210827 tracing: add average time in function to function profiler (2009-03-25) tar.gz
trace-rfc-tip-tracing-function-profiler-20090325-132759 tracing: add handler to trace_stat (2009-03-24) tar.gz
v2.6.29      Linux 2.6.29 (2009-03-23) tar.gz
v2.6.29-rc8  Linux 2.6.29-rc8 (2009-03-12) tar.gz
v2.6.29-rc7  Linux 2.6.29-rc7 (2009-03-03) tar.gz
v2.6.29-rc6  Linux 2.6.29-rc6 (2009-02-22) tar.gz
v2.6.29-rc5  Linux 2.6.29-rc5 (2009-02-13) tar.gz
v2.6.29-rc4  Linus 2.6.29-rc4 (2009-02-08) tar.gz
trace-ppc-ftrace-20090206-003823 prevent kprobes from catching spurious page faults (2009-02-05) tar.gz
v2.6.29-rc3  Linux 2.6.29-rc3 (2009-01-28) tar.gz
v2.6.29-rc2  Linux 2.6.29-rc2 (2009-01-16) tar.gz
v2.6.29-rc1  Linux 2.6.29-rc1 (2009-01-10) tar.gz
trace-ppc-ftrace-enable-20090106-234603 Merge branch 'for-linus' of git:// (2009-01-06) tar.gz
v2.6.28      Linux 2.6.28 (2008-12-24) tar.gz
trace-tip-devel-20081223-232047 Merge branch 'tracing/ring-buffer' (2008-12-23) tar.gz
trace-devel-20081223-112752 Null pointer deref with hrtimer_try_to_cancel() (2008-12-20) tar.gz
v2.6.28-rc9  Linux 2.6.28-rc9 (2008-12-18) tar.gz
v2.6.28-rc8  Linux 2.6.28-rc8 (2008-12-10) tar.gz
v2.6.28-rc7  Linux 2.6.28-rc7 (2008-12-01) tar.gz
v2.6.28-rc6  Linux 2.6.28-rc6 (2008-11-20) tar.gz
trace-ppc-ftrace-20081120-164154 powerpc/ppc32: ftrace, dynamic ftrace to handle modules (2008-11-20) tar.gz
trace-ppc-ftrace-hack-20081119-155924 Merge branch 'for-linus' of git:// (2008-11-18) tar.gz
ppc-trace-20081117-203413 ftrace,ppc64: do not use nops for modules (2008-11-17) tar.gz
ppc-trace-20081117-150845 ftrace,ppc: fix test of branch link (2008-11-17) tar.gz
v2.6.28-rc5  Linux 2.6.28-rc5 (2008-11-15) tar.gz
ppc-trace-20081116-162543 ftrace,ppc32: dynamic ftrace to handle modules (2008-11-15) tar.gz
ppc-trace-20081115-165034 ftrace: allow NULL pointers in mcount_loc (2008-11-14) tar.gz
ppc-trace-20081114-192003 Merge branch 'tracing/urgent' (2008-11-13) tar.gz
trace-20081112-234047 ftrace: do not update max buffer with no users (2008-11-12) tar.gz
trace-20081112-203303 ftrace: do not update max buffer with no users (2008-11-12) tar.gz
trace-20081111-152735 ring-buffer: buffer record on/off switch (2008-11-11) tar.gz
trace-20081112-230831 ring-buffer: buffer record on/off switch (2008-11-11) tar.gz
v2.6.28-rc4  Linux 2.6.28-rc4 (2008-11-09) tar.gz
v2.6.28-rc3  Linux 2.6.28-rc3 (2008-11-02) tar.gz
v2.6.28-rc2  Linux 2.6.28-rc2 (2008-10-26) tar.gz
v2.6.28-rc1  Linux 2.6.28-rc1 (2008-10-23) tar.gz
v2.6.27      Linux 2.6.27 (2008-10-09) tar.gz
v2.6.27-rc9  Linux 2.6.27-rc9 (2008-10-06) tar.gz
v2.6.27-rc8  Linux 2.6.27-rc8 (2008-09-29) tar.gz
v2.6.27-rc7  Linux 2.6.27-rc7 (2008-09-21) tar.gz
v2.6.27-rc6  Linux 2.6.27-rc6 (2008-09-09) tar.gz
v2.6.27-rc5  Linux 2.6.27-rc5 (2008-08-28) tar.gz
v2.6.27-rc4  Linux 2.6.27-rc4 (2008-08-20) tar.gz
v2.6.27-rc3  Linux 2.6.27-rc3 (2008-08-12) tar.gz
v2.6.27-rc2  Linux 2.6.27-rc2 (2008-08-05) tar.gz
v2.6.27-rc1  Linux 2.6.27-rc1 (2008-07-28) tar.gz
v2.6.26      Linux 2.6.26 (2008-07-13) tar.gz
v2.6.26-rc9  Linux 2.6.26-rc9 (2008-07-05) tar.gz
v2.6.26-rc8  Linux 2.6.26-rc8 (2008-06-24) tar.gz
v2.6.26-rc7  Linux 2.6.26-rc7 (2008-06-20) tar.gz
v2.6.26-rc6  Linux 2.6.26-rc6 (2008-06-12) tar.gz
v2.6.26-rc5  Linux 2.6.26-rc5 (2008-06-04) tar.gz
v2.6.26-rc4  Linux 2.6.26-rc4 (2008-05-26) tar.gz
v2.6.26-rc3  Linux 2.6.26-rc3 (2008-05-18) tar.gz
v2.6.26-rc2  Linux 2.6.26-rc2 (2008-05-11) tar.gz
v2.6.26-rc1  Linux 2.6.26-rc1 (2008-05-03) tar.gz
v2.6.25      Linux 2.6.25 (2008-04-16) tar.gz
v2.6.25-rc9  Linux 2.6.25-rc9 (2008-04-11) tar.gz
v2.6.25-rc8  Linux 2.6.25-rc8 (2008-04-01) tar.gz
v2.6.25-rc7  Linux 2.6.25-rc7 (2008-03-25) tar.gz
v2.6.25-rc6  Linux 2.6.25-rc6 (2008-03-16) tar.gz
v2.6.25-rc5  Linux 2.6.25-rc5 (2008-03-09) tar.gz
v2.6.25-rc4  Linux 2.6.25-rc4 (2008-03-04) tar.gz
v2.6.25-rc3  Linux 2.6.25-rc3 (2008-02-24) tar.gz
v2.6.25-rc2  Linux 2.6.25-rc2 (2008-02-15) tar.gz
v2.6.25-rc1  Linux 2.6.25-rc1 (2008-02-10) tar.gz
v2.6.24      Linux 2.6.24 (2008-01-24) tar.gz
v2.6.24-rc8  Linux 2.6.24-rc8 (2008-01-15) tar.gz
v2.6.24-rc7  Linux 2.6.24-rc7 (2008-01-06) tar.gz
v2.6.24-rc6  Linux 2.6.24-rc6 (2007-12-20) tar.gz
v2.6.24-rc5  Linux 2.6.24-rc5 (2007-12-10) tar.gz
v2.6.24-rc4  Linux 2.6.24-rc4 (2007-12-03) tar.gz
v2.6.24-rc3  Linux 2.6.24-rc3 (2007-11-16) tar.gz
v2.6.24-rc2  Linux 2.6.24-rc2 (2007-11-06) tar.gz
v2.6.24-rc1  Linux 2.6.24-rc1 (2007-10-23) tar.gz
v2.6.23      Linux 2.6.23 (2007-10-09) tar.gz
v2.6.23-rc9  Linux 2.6.23-rc9 (2007-10-01) tar.gz
v2.6.23-rc8  Linux 2.6.23-rc8 (2007-09-24) tar.gz
v2.6.23-rc7  Linux 2.6.23-rc7 (2007-09-19) tar.gz
v2.6.23-rc6  Linux 2.6.23-rc6 (2007-09-10) tar.gz
v2.6.23-rc5  Linux 2.6.23-rc5 (2007-08-31) tar.gz
v2.6.23-rc4  Linux 2.6.23-rc4 (2007-08-27) tar.gz
v2.6.23-rc3  Linux 2.6.23-rc3 (2007-08-12) tar.gz
v2.6.23-rc2  Linus 2.6.23-rc2 (2007-08-03) tar.gz
v2.6.23-rc1  Linux 2.6.23-rc1 (2007-07-22) tar.gz
v2.6.22      Linux 2.6.22 (2007-07-08) tar.gz
v2.6.22-rc7  Linux 2.6.22-rc7 (2007-07-01) tar.gz
v2.6.22-rc6  Linux 2.6.22-rc6 (2007-06-24) tar.gz
v2.6.22-rc5  Linux 2.6.22-rc5 (2007-06-16) tar.gz
v2.6.22-rc4  Linus 2.6.22-rc4 (2007-06-04) tar.gz
v2.6.22-rc3  Linux 2.6.22-rc3 (2007-05-25) tar.gz
v2.6.22-rc2  Linux 2.6.22-rc2 (2007-05-18) tar.gz
v2.6.22-rc1  Linus 2.6.22-rc1 (2007-05-12) tar.gz
v2.6.21      Linux 2.6.21 (2007-04-25) tar.gz
v2.6.21-rc7  Linux 2.6.21-rc7 (2007-04-15) tar.gz
v2.6.21-rc6  Linux 2.6.21-rc6 (2007-04-07) tar.gz
v2.6.21-rc5  Linux 2.6.21-rc5 (2007-03-25) tar.gz
v2.6.21-rc4  Linux 2.6.21-rc4 (2007-03-15) tar.gz
v2.6.21-rc3  Linux 2.6.21-rc3 (2007-03-06) tar.gz
v2.6.21-rc2  Linux 2.6.21-rc2 (2007-02-27) tar.gz
v2.6.21-rc1  Linux 2.6.21-rc1 (2007-02-20) tar.gz
v2.6.20      Linux 2.6.20 (2007-02-04) tar.gz
v2.6.20-rc7  Linux 2.6.20-rc7 (2007-01-30) tar.gz
v2.6.20-rc6  Linux 2.6.20-rc6 (2007-01-24) tar.gz
v2.6.20-rc5  Linux 2.6.20-rc5 (2007-01-12) tar.gz
v2.6.20-rc4  Linux 2.6.20-rc4 (2007-01-06) tar.gz
v2.6.20-rc3  Linux 2.6.20-rc3 (2006-12-31) tar.gz
v2.6.20-rc2  Linux 2.6.20-rc2 (2006-12-23) tar.gz
v2.6.20-rc1  Linux v2.6.20-rc1 (2006-12-13) tar.gz
v2.6.19      Linux 2.6.19 (2006-11-29) tar.gz
v2.6.19-rc6  Linux 2.6.19-rc6 (2006-11-15) tar.gz
v2.6.19-rc5  Linux 2.6.19-rc5 (2006-11-07) tar.gz
v2.6.19-rc4  Linux 2.6.19-rc4 (2006-10-30) tar.gz
v2.6.19-rc3  Linux 2.6.19-rc3 release (2006-10-23) tar.gz
v2.6.19-rc2  Linux 2.6.19-rc2 (2006-10-13) tar.gz
v2.6.19-rc1  Linux v2.6.19-rc1 (2006-10-04) tar.gz
v2.6.18      Raise the Jolly Roger! (2006-09-19) tar.gz
v2.6.18-rc7  Linux 2.6.18-rc7 (2006-09-12) tar.gz
v2.6.18-rc6  Linux 2.6.18-rc6 release (2006-09-03) tar.gz
v2.6.18-rc5  Linux 2.6.18-rc5 (2006-08-27) tar.gz
v2.6.18-rc4  Linux v2.6.18-rc4 (2006-08-06) tar.gz
v2.6.18-rc3  Linux v2.6.18-rc3 (2006-07-29) tar.gz
v2.6.18-rc2  Linux v2.6.18-rc2 (2006-07-15) tar.gz
v2.6.18-rc1  Linux v2.6.18-rc1 (2006-07-05) tar.gz
v2.6.17      Linux v2.6.17 (2006-06-17) tar.gz
v2.6.17-rc6  Linux v2.6.17-rc6 (2006-06-05) tar.gz
v2.6.17-rc5  Linux 2.6.17-rc5 release (2006-05-24) tar.gz
v2.6.17-rc4  Linux v2.6.17-rc4 release (2006-05-11) tar.gz
v2.6.17-rc3  Linux v2.6.17-rc3 (2006-04-26) tar.gz
v2.6.17-rc2  Linux v2.6.17-rc2 (2006-04-18) tar.gz
v2.6.17-rc1  Linux v2.6.17-rc1 (2006-04-02) tar.gz
v2.6.16      Linux v2.6.16 release (2006-03-19) tar.gz
v2.6.16-rc6  Linux v2.6.16-rc6 release (2006-03-11) tar.gz
v2.6.16-rc5  Linux v2.6.16-rc5 release (2006-02-26) tar.gz
v2.6.16-rc4  Linux v2.6.16-rc4 release (2006-02-17) tar.gz
v2.6.16-rc3  Linux v2.6.16-rc3 (2006-02-12) tar.gz
v2.6.16-rc2  Linux v2.6.16-rc2 (2006-02-02) tar.gz
v2.6.16-rc1  Linux v2.6.16-rc1 (2006-01-16) tar.gz
v2.6.15      Linux 2.6.15 release (2006-01-02) tar.gz
v2.6.15-rc7  Christmas eve is when the _real_ celebrations take place. (2005-12-24) tar.gz
v2.6.15-rc6  Linux 2.6.15-rc6 (2005-12-18) tar.gz
v2.6.15-rc5  Linux v2.6.15-rc5 release (2005-12-03) tar.gz
v2.6.15-rc4  Linux v2.6.15-rc4 (2005-11-30) tar.gz
v2.6.15-rc3  Linux v2.6.15-rc3 (2005-11-28) tar.gz
v2.6.15-rc2  Linux v2.6.15-rc2 (2005-11-19) tar.gz
v2.6.15-rc1  Linux v2.6.15-rc1 (2005-11-11) tar.gz
v2.6.14      Linux 2.6.14 release (2005-10-27) tar.gz
v2.6.14-rc5  Linux v2.6.14-rc5 release (2005-10-19) tar.gz
v2.6.14-rc4  Linux 2.6.14-rc4 release (2005-10-10) tar.gz
v2.6.14-rc3  Linux v2.6.14-rc3 release (2005-09-30) tar.gz
v2.6.14-rc2  Linux v2.6.14-rc2 release (2005-09-19) tar.gz
v2.6.14-rc1  Linux v2.6.14-rc1 (2005-09-12) tar.gz
v2.6.13      Linux 2.6.13 release (2005-08-28) tar.gz
v2.6.13-rc7  Linux v2.6.13-rc7 (2005-08-23) tar.gz
v2.6.13-rc6  Linux 2.6.13-rc6 release (2005-08-07) tar.gz
v2.6.13-rc5  Aiming for final. Sure. (2005-08-01) tar.gz
v2.6.13-rc4  Get out from LKS flood (2005-07-28) tar.gz
v2.6.11      This is the 2.6.11 tree object. () tar.gz
v2.6.11-tree This is the 2.6.11 tree object. () tar.gz
v2.6.12      This is the final 2.6.12 release () tar.gz
v2.6.12-rc2  Linux v2.6.12-rc2 release () tar.gz
v2.6.12-rc3  Linux v2.6.12-rc3 release () tar.gz
v2.6.12-rc4  Linux v2.6.12-rc4 release () tar.gz
v2.6.12-rc5  Linux-2.6.12-rc5 release () tar.gz
v2.6.12-rc6  Linux-v2.6.12-rc6 release () tar.gz
v2.6.13-rc1  Linux v2.6.13-rc1 () tar.gz
v2.6.13-rc2  Linux v2.6.13-rc2 () tar.gz
v2.6.13-rc3  Linux v2.6.13-rc3 () tar.gz

git clone