[Bug 2114822] Re: sysdig-dkms FTBFS in Jammy on arm64

[Massimiliano Pellizzer]

> why is it marked as "Invalid" for the current Ubuntu serie. The SRU
guideline require to resolve the issue in the newer series first. What's
the status also of Noble?

Hello Sebastien,
>From Noble onward the part of sysdig that interfaces with the kernel has been moved to falcosecurity.
As a matter of fact you can see that the folder "driver" has been completely removed from the upstream project: https://github.com/draios/sysdig

> isn't really specific / helping to know what to try. What is "sysdig"
doing? Could you come with an user visible issue that could be observed
if that package isn't working as expected?

I will be more specific, thanks for the advice

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2114822

Title:
  sysdig-dkms FTBFS in Jammy on arm64

Status in sysdig package in Ubuntu:
  Invalid
Status in sysdig source package in Jammy:
  In Progress

Bug description:
  [ Impact ]

  sysdig-dkms FTBFS in Jammy on arm64 as follows:

  make: Entering directory '/usr/src/linux-headers-5.15.0-141-generic'
    4   CC [M]  /var/lib/dkms/sysdig/0.27.1/build/main.o
    5   CC [M]  /var/lib/dkms/sysdig/0.27.1/build/dynamic_params_table.o
    6   CC [M]  /var/lib/dkms/sysdig/0.27.1/build/fillers_table.o
    7   CC [M]  /var/lib/dkms/sysdig/0.27.1/build/flags_table.o
    8   CC [M]  /var/lib/dkms/sysdig/0.27.1/build/ppm_events.o
    9 /var/lib/dkms/sysdig/0.27.1/build/main.c: In function ‘drop_event’:
   10 /var/lib/dkms/sysdig/0.27.1/build/main.c:1535:17: warning: ISO C90 forbids mixed declarations and code [-Wdeclaration-after-statement]
   11  1535 |                 nanoseconds rem;
   12       |                 ^~~~~~~~~~~
   13 /var/lib/dkms/sysdig/0.27.1/build/main.c: In function ‘syscall_enter_probe’:
   14 /var/lib/dkms/sysdig/0.27.1/build/main.c:1946:28: error: ‘SYSCALL_TABLE_ID0’ undeclared (first use in this function); did you mean ‘SYSCALL_TABLE_SIZE’?
   15  1946 |         table_index = id - SYSCALL_TABLE_ID0;
   16       |                            ^~~~~~~~~~~~~~~~~
   17       |                            SYSCALL_TABLE_SIZE
   18 /var/lib/dkms/sysdig/0.27.1/build/main.c:1946:28: note: each undeclared identifier is reported only once for each function it appears in
   19 /var/lib/dkms/sysdig/0.27.1/build/main.c: In function ‘syscall_exit_probe’:
   20 /var/lib/dkms/sysdig/0.27.1/build/main.c:2023:28: error: ‘SYSCALL_TABLE_ID0’ undeclared (first use in this function); did you mean ‘SYSCALL_TABLE_SIZE’?
   21  2023 |         table_index = id - SYSCALL_TABLE_ID0;
   22       |                            ^~~~~~~~~~~~~~~~~
   23       |                            SYSCALL_TABLE_SIZE
   24 make[1]: *** [scripts/Makefile.build:297: /var/lib/dkms/sysdig/0.27.1/build/main.o] Error 1
   25 make[1]: *** Waiting for unfinished jobs....
   26 make: *** [Makefile:1915: /var/lib/dkms/sysdig/0.27.1/build] Error 2

  [ Fix ]

  Enable arm64 backporting the following patch from upstream:
  - https://github.com/falcosecurity/libs/commit/c4f096099bf81966803d26c40c6c2cb2b8d08033

  [ Test Plan ]

  Install and load sysdig driver on both Jammy generic and Jammy hwe on
  arm64:

  $ sudo apt install sysdig-dkms
  $ dkms status
  $ sudo modprobe sysdig-probe
  $ lsmod | grep sysdig

  [ Regression potential ]

  We may experience regressions in systems that are using sysdig in Jammy.
  In particular the sysdig kernel module may fail to load, or eBPF may not be able to hook functions in kernel space to trace them properly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysdig/+bug/2114822/+subscriptions