dtrace: update NEWS and spec file for 0.6.0-2

Included information about new bugfixes and features in te 0.6.0-2
release.

Signed-off-by: Kris Van Hees <kris.van.hees@oracle.com>

diff --git a/dtrace/NEWS b/dtrace/NEWS
index b5e9fbd6d3d6a107bd8d89c4609af2e8ed819548..60452bba193211036193a1b56611e7f20c757c63 100644 (file)
--- a/dtrace/NEWS
+++ b/dtrace/NEWS
@@ -1,9 +1,9 @@
 DTrace Kernel Modules News
 ==========================
 
-Release 0.6.0 (Dec 19th, 2016)
+Release 0.6.0 (Mar  3rd, 2017)
 ------------------------------
-Kernel release: 4.1.12-81
+Kernel release: 4.1.12-92.el6uek
 
 New features:
 
@@ -32,9 +32,20 @@ New features:
    Per-provider wrappers for DTRACE_PROBE_ENABLED() can be used, as with
    DTRACE_PROBE() itself.
 
- - Function boundary tracing (FBT) is supported in a limited fashion.  For
-   now, it is limited to the entry point functions for system calls.  This
-   limitation will be lifted as soon as possible.
+ - Function boundary tracing (FBT) is supported for entry probes to most
+   functions in the core kernel.  The current implementation does not support
+   retrieval of function arguments or return probes (except for some limited
+   support on x86_64).  These features are currently under development.
+
+Changes:
+
+ - The implementation of the D 'ustack' action has been moved into the kernel
+   proper.  This change was motivated by the need to access page table
+   structures directly using a lock-free mechanism.
+
+ - Probe processing will be bypassed when the system is entering panic mode,
+   This ensures that DTrace will not cause panic related output to be
+   disrupted.
 
 Bugfixes:
 
@@ -42,6 +53,22 @@ Bugfixes:
    being executed under the assumption that preemption was disabled when in
    fact it was not.
 
+ - Probe processing (probe context) is not re-entrant, yet probes firing as a
+   result of processing another probe would cause re-entry into the processing
+   core, with often horrible effects.  The processing core has been modified to
+   block any re-entry attempt except for ERROR probe processing.  That is a
+   deliberate (and acceptable) exception in the DTrace design.
+
+ - The fast path implementation for obtaining the value of the D 'caller'
+   variable for sparc64 has been corrected.
+
+ - The implemenation of the D 'stack' action has been made more robust, making
+   sure that memory access faults are not fatal.
+
+ - The implementation of the D 'ustack' action has been reworked completely to
+   improve stability and accuracy.
+
+
 Release 0.5.3 (May 25th, 2016)
 ------------------------------
 Kernel release: 4.1.12-43.el6uek
@@ -62,6 +89,7 @@ Bugfixes:
    the sdt DTrace multi-provider module due to the handling of memory that is
    set aside for SDT probe trampolines.  This bug has been fixed.
 
+
 Release 0.5.2 (Feb 3rd, 2016)
 -----------------------------
 Kernel release: 4.1.12-33.el6uek

diff --git a/dtrace/dtrace-module.spec b/dtrace/dtrace-module.spec
index 1889764a0cbfe01de4c6a8207c355e432758c2e1..fd74dd7d1cb1a87ccafc2d6ec85919209e3118d5 100644 (file)
--- a/dtrace/dtrace-module.spec
+++ b/dtrace/dtrace-module.spec
@@ -20,7 +20,7 @@
 Name: dtrace-modules-%{kver}
 Summary: dtrace module
 Version: 0.6.0
-Release: 1%{dist}
+Release: 2%{dist}
 Provides: dtrace-modules
 Requires: at
 License: CDDL
@@ -127,6 +127,11 @@ rm -rf %{buildroot}
 /usr/include/linux/dtrace/types.h
 
 %changelog
+* Fri Mar  3 2017 - <kris.van.hees@oracle.com> - 0.6.0-2
+- Further implementation of FBT with fixes to ustack
+  [Orabug: 21220305]
+- Handle modular IPv6 and introduce typedef in6_addr_t
+  (Nick Alcock) [Orabug: 25557554]
 * Mon Dec 19 2016 - <nick.alcock@oracle.com> - 0.6.0-1
 - USDT for SPARC. [Orabug: 24455245]
 - Is-enabled probes for SDT [Orabug: 25143173]