The package in -proposed builds a loads correctly on: - 5.15.0-130-generic - 5.15.0-132-generic - 6.8.0-51-generic - 6.8.0-53-generic
as shown by: $ dkms status lttng-modules/2.13.11, 5.15.0-130-generic, x86_64: installed lttng-modules/2.13.11, 5.15.0-132-generic, x86_64: installed lttng-modules/2.13.11, 6.8.0-51-generic, x86_64: installed lttng-modules/2.13.11, 6.8.0-53-generic, x86_64: installed $ sudo modprobe lttng_test $ lsmod | grep lttng_test lttng_test 28672 0 lttng_tracer 3043328 38 ... ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Canonical Platform QA Team, which is subscribed to ubuntu-kernel-tests. https://bugs.launchpad.net/bugs/2096645 Title: lttng DKMS failed to build on Jammy in sru-20250113 (error: conflicting types for 'trace_mm_page_alloc_zone_locked') Status in ubuntu-kernel-tests: New Status in lttng-modules package in Ubuntu: Invalid Status in lttng-modules source package in Jammy: Fix Committed Bug description: Issue found with Jammy 5.15.0-132.143 in sru-20250113 [Impact] lttng-modules-dkms does not compile from source in Jammy: CC [M] /var/lib/dkms/lttng-modules/2.13.8/build/src/lib/ringbuffer/ring_buffer_iterator.o CC [M] /var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-kmem.o In file included from /var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/define_trace.h:87, from /var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/kmem.h:570, from /var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-kmem.c:35: /var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:133:6: error: conflicting types for 'trace_mm_page_alloc_zone_locked'; have 'void(struct page *, unsigned int, int)' 133 | void trace_##_name(_proto); | ^~~~~~ /var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/kmem.h:438:1: note: in expansion of macro 'LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP' 438 | LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP(kmem_mm_page, mm_page_alloc_zone_locked, | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ In file included from ./include/trace/events/kmem.h:9, from /var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-kmem.c:24: ./include/linux/tracepoint.h:244:28: note: previous definition of 'trace_mm_page_alloc_zone_locked' with type 'void(struct page *, unsigned int, int, int)' 244 | static inline void trace_##name(proto) \ | ^~~~~~ ./include/linux/tracepoint.h:416:9: note: in expansion of macro '__DECLARE_TRACE' 416 | __DECLARE_TRACE(name, PARAMS(proto), PARAMS(args), \ | ^~~~~~~~~~~~~~~ ./include/linux/tracepoint.h:539:9: note: in expansion of macro 'DECLARE_TRACE' 539 | DECLARE_TRACE(name, PARAMS(proto), PARAMS(args)) | ^~~~~~~~~~~~~ ./include/trace/events/kmem.h:259:1: note: in expansion of macro 'DEFINE_EVENT' 259 | DEFINE_EVENT(mm_page, mm_page_alloc_zone_locked, | ^~~~~~~~~~~~ make[3]: *** [scripts/Makefile.build:297: /var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-kmem.o] Error 1 [ Test case ] Install lttng-modules-dkms: $ sudo apt install lttng-modules-dkms Load the module: $ sudo modprobe lttng-test The same procedure should be repeated on linux-5.15, the GA kernel, to test for possible regressions. [ Fix ] Patch the code to properly support 6.8 and 5.15 ABI. [ Regression potential ] We may experience regressions in systems that are using the lttng debugging tool. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2096645/+subscriptions -- Mailing list: https://launchpad.net/~canonical-ubuntu-qa Post to : canonical-ubuntu-qa@lists.launchpad.net Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa More help : https://help.launchpad.net/ListHelp
