ubuntu_sysdig_smoke_test failed on azure 4.11 kernel

[Po-Hsu Lin]

[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)

Summary: 0 passed, 3 failed

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1727275

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Colin Ian King (colin-king)]

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

[Colin Ian King (colin-king)]

Debdiff

[Colin Ian King (colin-king)]

Package built OK: https://launchpad.net/~colin-king/+archive/ubuntu/amber/+packages

[Colin Ian King (colin-king)]

Sam, so you mind testing my fix using the PPA below:

sudo add-apt-repository ppa:colin-king/amber
sudo apt-get update
sudo apt-get install sysdig-dkms

[Po-Hsu Lin (cypressyew)]

Verified with Colin's ppa, the test has passed with the dkms.

08:08:39 INFO | == sysdig smoke test to trace dd, cat, read and writes ==
08:08:39 INFO | Limiting raw capture file to 16384 blocks
08:08:39 INFO | Try 1 of 10
08:08:39 INFO | Sysdig capture started after 1 seconds wait
08:08:39 INFO | Raw capture file is 0 Mbytes
08:08:39 INFO | Converted events file is 0 Mbytes
08:08:39 INFO | Try 2 of 10
08:08:39 INFO | Sysdig capture started after 1 seconds wait
08:08:39 INFO | Raw capture file is 16 Mbytes
08:08:39 INFO | Converted events file is 19 Mbytes
08:08:39 INFO | Found:
08:08:39 INFO | 187531 sysdig events
08:08:39 INFO | 14705 context switches
08:08:39 INFO | 18759 reads from /dev/zero by dd
08:08:39 INFO | 18747 writes to /dev/null by dd
08:08:39 INFO | PASSED (trace at least 25 context switches)
08:08:39 INFO | PASSED (trace at least 25 reads of /dev/zero by dd)
08:08:39 INFO | PASSED (trace at least 25 writes to /dev/null by dd)
08:08:39 INFO |
08:08:39 INFO | Summary: 3 passed, 0 failed

[Łukasz Zemczak (sil2100)]

Hello Po-Hsu, or anyone else affected,

Accepted sysdig into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/sysdig/0.8.0-1ubuntu3 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

[Po-Hsu Lin (cypressyew)]

Verified with sysdig 0.8.0-1ubuntu3 on azure kernel, it works as expected.
Thanks

[Łukasz Zemczak (sil2100)]

@Po-Hsu Lin: did you do regression checking on supported kernel versions as per what was written in the [Regression Potential] field?

[Po-Hsu Lin (cypressyew)]

Hi Łukasz,

I have tested with 3.13, 4.4, 4.10 kernel, also on 4.11 azure.
Thanks

[Launchpad Janitor (janitor)]

This bug was fixed in the package sysdig - 0.8.0-1ubuntu3

---------------
sysdig (0.8.0-1ubuntu3) xenial; urgency=medium

  * Fix build issues with 4.11 kernel headers (LP: #1727275)
    backports from upstream sysdig to support 4.11 and HWE 4.13
    kernels using the following commits:
    - [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)

 -- Colin Ian King <email address hidden> Fri, 27 Oct 2017 15:13:11 +0100

[Brian Murray (brian-murray)]

The verification of the Stable Release Update for sysdig has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.