Tested on 4.4, 4.8 and 4.13 HWE kernels on Xenial. Passes regression
tests. Should work fine now on all kernels from 4.4..4.13
** Description changed:
+ [SRU sysdig XENIAL for 4.11 and 4.13 kernel support]
+
+ sysdig DKMS fails to build because of API changes in 4.11, 4.13
+
+ [FIX]
+
+ Apply the following upstream sysdig commits for various kernel compat
+ fixes:
+
+ - [5fef96] Fix for kernel < 3.9 with CPU_ACCOUNTING_NATIVE disabled.
+ - [29c40f] Fix cputime for kernel 3.8 and 2.6.18
+ - [4596f0] Make sure to unlock mutex during error paths
+ - [460f6e] Update probe module for kernel 4.11 (#829)
+
+ [TEST]
+ from kernel team autotests:
+
+ sudo autotest/client/autotest-local
+ autotest/client/tests/ubuntu_sysdig_smoke_test/control
+
+ Without the fixes, these will fail. With the fixes, the regression tests
+ pass. Run this 4.4, 4.8, 4.11 azure and 4.13-hwe kernels, must pass on
+ all three kernel versions.
+
+ [REGRESSION POTENTIAL]
+ This affects just the sysdig driver. Could break on pre-4.13 older kernels,
so needs regression checking on supported kernel versions.
+
+ -------------------------------------
+
azure : 4.11.0-1014.14
- == sysdig smoke test to trace dd, cat, read and writes ==
- Limiting raw capture file to 16384 blocks
- Try 1 of 10
- Could not find start of capture message, maybe sysdig didn't start?
- Raw capture file is 0 Mbytes
- Converted events file is 0 Mbytes
- Try 2 of 10
- Could not find start of capture message, maybe sysdig didn't start?
- Raw capture file is 0 Mbytes
- Converted events file is 0 Mbytes
- Try 3 of 10
- Could not find start of capture message, maybe sysdig didn't start?
- Raw capture file is 0 Mbytes
- Converted events file is 0 Mbytes
- Try 4 of 10
- Could not find start of capture message, maybe sysdig didn't start?
- Raw capture file is 0 Mbytes
- Converted events file is 0 Mbytes
- Try 5 of 10
- Could not find start of capture message, maybe sysdig didn't start?
- Raw capture file is 0 Mbytes
- Converted events file is 0 Mbytes
- Try 6 of 10
- Could not find start of capture message, maybe sysdig didn't start?
- Raw capture file is 0 Mbytes
- Converted events file is 0 Mbytes
- Try 7 of 10
- Could not find start of capture message, maybe sysdig didn't start?
- Raw capture file is 0 Mbytes
- Converted events file is 0 Mbytes
- Try 8 of 10
- Could not find start of capture message, maybe sysdig didn't start?
- Raw capture file is 0 Mbytes
- Converted events file is 0 Mbytes
- Try 9 of 10
- Could not find start of capture message, maybe sysdig didn't start?
- Raw capture file is 0 Mbytes
- Converted events file is 0 Mbytes
- Try 10 of 10
- Could not find start of capture message, maybe sysdig didn't start?
- Raw capture file is 0 Mbytes
- Converted events file is 0 Mbytes
- Found:
- 0 sysdig events
- 0 context switches
- 0 reads from /dev/zero by dd
- 0 writes to /dev/null by dd
- FAILED (trace at least 25 context switches)
- FAILED (trace at least 25 reads of /dev/zero by dd)
- FAILED (trace at least 25 writes to /dev/null by dd)
-
+ == sysdig smoke test to trace dd, cat, read and writes ==
+ Limiting raw capture file to 16384 blocks
+ Try 1 of 10
+ Could not find start of capture message, maybe sysdig didn't start?
+ Raw capture file is 0 Mbytes
+ Converted events file is 0 Mbytes
+ Try 2 of 10
+ Could not find start of capture message, maybe sysdig didn't start?
+ Raw capture file is 0 Mbytes
+ Converted events file is 0 Mbytes
+ Try 3 of 10
+ Could not find start of capture message, maybe sysdig didn't start?
+ Raw capture file is 0 Mbytes
+ Converted events file is 0 Mbytes
+ Try 4 of 10
+ Could not find start of capture message, maybe sysdig didn't start?
+ Raw capture file is 0 Mbytes
+ Converted events file is 0 Mbytes
+ Try 5 of 10
+ Could not find start of capture message, maybe sysdig didn't start?
+ Raw capture file is 0 Mbytes
+ Converted events file is 0 Mbytes
+ Try 6 of 10
+ Could not find start of capture message, maybe sysdig didn't start?
+ Raw capture file is 0 Mbytes
+ Converted events file is 0 Mbytes
+ Try 7 of 10
+ Could not find start of capture message, maybe sysdig didn't start?
+ Raw capture file is 0 Mbytes
+ Converted events file is 0 Mbytes
+ Try 8 of 10
+ Could not find start of capture message, maybe sysdig didn't start?
+ Raw capture file is 0 Mbytes
+ Converted events file is 0 Mbytes
+ Try 9 of 10
+ Could not find start of capture message, maybe sysdig didn't start?
+ Raw capture file is 0 Mbytes
+ Converted events file is 0 Mbytes
+ Try 10 of 10
+ Could not find start of capture message, maybe sysdig didn't start?
+ Raw capture file is 0 Mbytes
+ Converted events file is 0 Mbytes
+ Found:
+ 0 sysdig events
+ 0 context switches
+ 0 reads from /dev/zero by dd
+ 0 writes to /dev/null by dd
+ FAILED (trace at least 25 context switches)
+ FAILED (trace at least 25 reads of /dev/zero by dd)
+ FAILED (trace at least 25 writes to /dev/null by dd)
+
Summary: 0 passed, 3 failed
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727275
Title:
ubuntu_sysdig_smoke_test failed on azure 4.11 kernel
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727275/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
