[Kernel-packages] [Bug 2017006] Proposed package removed from archive

2024-01-05 Thread Steve Langasek
The version of lttng-modules in the proposed pocket of Lunar that was
purported to fix this bug report has been removed because one or more
bugs that were to be fixed by the upload have failed verification and
been in this state for more than 10 days.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2017006

Title:
  fix build issue for v5.19 kernels (jammy-hwe, kinetic, lunar-riscv)

Status in linux package in Ubuntu:
  Invalid
Status in lttng-modules package in Ubuntu:
  Won't Fix
Status in linux source package in Focal:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in lttng-modules source package in Jammy:
  Won't Fix
Status in linux source package in Kinetic:
  Invalid
Status in lttng-modules source package in Kinetic:
  Won't Fix
Status in linux source package in Lunar:
  Invalid
Status in lttng-modules source package in Lunar:
  Won't Fix
Status in linux source package in Mantic:
  Invalid

Bug description:
  SRU Justification

  [ Impact ]

  Upstream stable added a change in the format of jbd2 in 5.15.87 that
  was cherry-picked to kinetic:linux.

  This is incompatible with the current changes in the lttng-module
  kinetic.

  We previously encountered this issue for focal 
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2004644
  and we proactively released a new version for kinetic.
  The problem is the fix does not really work as expected.

  As shown in the logs below,
  The build error is triggered because some function declaration does not match 
the kernel's.
  In `include/instrumentation/events/jbd2.h` in lttng-modules, there is a 
conditional declaration based on the kernel version. 5.19 is missing there, 
therefore kinetic will fall back to the old declaration. The reason 5.19 is not 
there is probably because this version has reached end of life last year.

  Build logs:
  35:35 DEBUG| [stdout] In file included from 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/define_trace.h:87,
    860 02:35:35 DEBUG| [stdout]  from 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:293,
    861 02:35:35 DEBUG| [stdout]  from 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:29:
    862 02:35:35 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:133:6:
 error: conflicting types for ‘trace_jbd2_run_stats’; have ‘void(dev_t,  long 
unsigned int,  struct transaction_run_stats_s *)’ {aka ‘void(unsigned int,  
long unsigned int,  struct transaction_run_stats_s *)’}
    863 02:35:35 DEBUG| [stdout]   133 | void 
trace_##_name(_proto);
    864 02:35:35 DEBUG| [stdout]   |  ^~
    865 02:35:35 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:45:9:
 note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP’
    866 02:35:35 DEBUG| [stdout]45 | 
LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP(map, name, map, PARAMS(proto), PARAMS(args))
    867 02:35:35 DEBUG| [stdout]   | 
^~~
    868 02:35:35 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:87:9:
 note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_MAP’
    869 02:35:35 DEBUG| [stdout]87 | 
LTTNG_TRACEPOINT_EVENT_MAP(name, name,  \
    870 02:35:35 DEBUG| [stdout]   | 
^~
    871 02:35:35 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:180:1:
 note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT’
    872 02:35:35 DEBUG| [stdout]   180 | 
LTTNG_TRACEPOINT_EVENT(jbd2_run_stats,
    873 02:35:35 DEBUG| [stdout]   | ^~
    874 02:35:35 DEBUG| [stdout] In file included from 
./include/trace/events/jbd2.h:9,
    875 02:35:35 DEBUG| [stdout]  from 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:18:
    876 02:35:35 DEBUG| [stdout] 
./include/linux/tracepoint.h:245:28: note: previous definition of 
‘trace_jbd2_run_stats’ with type ‘void(dev_t,  tid_t,  struct 
transaction_run_stats_s *)’ {aka ‘void(unsigned int,  unsigned int,  struct 
transaction_run_stats_s *)’}
    877 02:35:35 DEBUG| [stdout]   245 | static inline 
void trace_##name(proto)  \
    878 02:35:35 DEBUG| [stdout]   |
^~
    879 

[Kernel-packages] [Bug 2017006] Proposed package removed from archive

2024-01-05 Thread Steve Langasek
The version of lttng-modules in the proposed pocket of Lunar that was
purported to fix this bug report has been removed because one or more
bugs that were to be fixed by the upload have failed verification and
been in this state for more than 10 days.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2017006

Title:
  fix build issue for v5.19 kernels (jammy-hwe, kinetic, lunar-riscv)

Status in linux package in Ubuntu:
  Invalid
Status in lttng-modules package in Ubuntu:
  Won't Fix
Status in linux source package in Focal:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in lttng-modules source package in Jammy:
  Won't Fix
Status in linux source package in Kinetic:
  Invalid
Status in lttng-modules source package in Kinetic:
  Won't Fix
Status in linux source package in Lunar:
  Invalid
Status in lttng-modules source package in Lunar:
  Won't Fix
Status in linux source package in Mantic:
  Invalid

Bug description:
  SRU Justification

  [ Impact ]

  Upstream stable added a change in the format of jbd2 in 5.15.87 that
  was cherry-picked to kinetic:linux.

  This is incompatible with the current changes in the lttng-module
  kinetic.

  We previously encountered this issue for focal 
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2004644
  and we proactively released a new version for kinetic.
  The problem is the fix does not really work as expected.

  As shown in the logs below,
  The build error is triggered because some function declaration does not match 
the kernel's.
  In `include/instrumentation/events/jbd2.h` in lttng-modules, there is a 
conditional declaration based on the kernel version. 5.19 is missing there, 
therefore kinetic will fall back to the old declaration. The reason 5.19 is not 
there is probably because this version has reached end of life last year.

  Build logs:
  35:35 DEBUG| [stdout] In file included from 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/define_trace.h:87,
    860 02:35:35 DEBUG| [stdout]  from 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:293,
    861 02:35:35 DEBUG| [stdout]  from 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:29:
    862 02:35:35 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:133:6:
 error: conflicting types for ‘trace_jbd2_run_stats’; have ‘void(dev_t,  long 
unsigned int,  struct transaction_run_stats_s *)’ {aka ‘void(unsigned int,  
long unsigned int,  struct transaction_run_stats_s *)’}
    863 02:35:35 DEBUG| [stdout]   133 | void 
trace_##_name(_proto);
    864 02:35:35 DEBUG| [stdout]   |  ^~
    865 02:35:35 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:45:9:
 note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP’
    866 02:35:35 DEBUG| [stdout]45 | 
LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP(map, name, map, PARAMS(proto), PARAMS(args))
    867 02:35:35 DEBUG| [stdout]   | 
^~~
    868 02:35:35 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:87:9:
 note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_MAP’
    869 02:35:35 DEBUG| [stdout]87 | 
LTTNG_TRACEPOINT_EVENT_MAP(name, name,  \
    870 02:35:35 DEBUG| [stdout]   | 
^~
    871 02:35:35 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:180:1:
 note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT’
    872 02:35:35 DEBUG| [stdout]   180 | 
LTTNG_TRACEPOINT_EVENT(jbd2_run_stats,
    873 02:35:35 DEBUG| [stdout]   | ^~
    874 02:35:35 DEBUG| [stdout] In file included from 
./include/trace/events/jbd2.h:9,
    875 02:35:35 DEBUG| [stdout]  from 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:18:
    876 02:35:35 DEBUG| [stdout] 
./include/linux/tracepoint.h:245:28: note: previous definition of 
‘trace_jbd2_run_stats’ with type ‘void(dev_t,  tid_t,  struct 
transaction_run_stats_s *)’ {aka ‘void(unsigned int,  unsigned int,  struct 
transaction_run_stats_s *)’}
    877 02:35:35 DEBUG| [stdout]   245 | static inline 
void trace_##name(proto)  \
    878 02:35:35 DEBUG| [stdout]   |
^~
    879 

[Kernel-packages] [Bug 2017006] Proposed package removed from archive

2024-01-05 Thread Steve Langasek
The version of lttng-modules in the proposed pocket of Lunar that was
purported to fix this bug report has been removed because one or more
bugs that were to be fixed by the upload have failed verification and
been in this state for more than 10 days.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2017006

Title:
  fix build issue for v5.19 kernels (jammy-hwe, kinetic, lunar-riscv)

Status in linux package in Ubuntu:
  Invalid
Status in lttng-modules package in Ubuntu:
  Won't Fix
Status in linux source package in Focal:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in lttng-modules source package in Jammy:
  Won't Fix
Status in linux source package in Kinetic:
  Invalid
Status in lttng-modules source package in Kinetic:
  Won't Fix
Status in linux source package in Lunar:
  Invalid
Status in lttng-modules source package in Lunar:
  Won't Fix
Status in linux source package in Mantic:
  Invalid

Bug description:
  SRU Justification

  [ Impact ]

  Upstream stable added a change in the format of jbd2 in 5.15.87 that
  was cherry-picked to kinetic:linux.

  This is incompatible with the current changes in the lttng-module
  kinetic.

  We previously encountered this issue for focal 
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2004644
  and we proactively released a new version for kinetic.
  The problem is the fix does not really work as expected.

  As shown in the logs below,
  The build error is triggered because some function declaration does not match 
the kernel's.
  In `include/instrumentation/events/jbd2.h` in lttng-modules, there is a 
conditional declaration based on the kernel version. 5.19 is missing there, 
therefore kinetic will fall back to the old declaration. The reason 5.19 is not 
there is probably because this version has reached end of life last year.

  Build logs:
  35:35 DEBUG| [stdout] In file included from 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/define_trace.h:87,
    860 02:35:35 DEBUG| [stdout]  from 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:293,
    861 02:35:35 DEBUG| [stdout]  from 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:29:
    862 02:35:35 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:133:6:
 error: conflicting types for ‘trace_jbd2_run_stats’; have ‘void(dev_t,  long 
unsigned int,  struct transaction_run_stats_s *)’ {aka ‘void(unsigned int,  
long unsigned int,  struct transaction_run_stats_s *)’}
    863 02:35:35 DEBUG| [stdout]   133 | void 
trace_##_name(_proto);
    864 02:35:35 DEBUG| [stdout]   |  ^~
    865 02:35:35 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:45:9:
 note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP’
    866 02:35:35 DEBUG| [stdout]45 | 
LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP(map, name, map, PARAMS(proto), PARAMS(args))
    867 02:35:35 DEBUG| [stdout]   | 
^~~
    868 02:35:35 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:87:9:
 note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_MAP’
    869 02:35:35 DEBUG| [stdout]87 | 
LTTNG_TRACEPOINT_EVENT_MAP(name, name,  \
    870 02:35:35 DEBUG| [stdout]   | 
^~
    871 02:35:35 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:180:1:
 note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT’
    872 02:35:35 DEBUG| [stdout]   180 | 
LTTNG_TRACEPOINT_EVENT(jbd2_run_stats,
    873 02:35:35 DEBUG| [stdout]   | ^~
    874 02:35:35 DEBUG| [stdout] In file included from 
./include/trace/events/jbd2.h:9,
    875 02:35:35 DEBUG| [stdout]  from 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:18:
    876 02:35:35 DEBUG| [stdout] 
./include/linux/tracepoint.h:245:28: note: previous definition of 
‘trace_jbd2_run_stats’ with type ‘void(dev_t,  tid_t,  struct 
transaction_run_stats_s *)’ {aka ‘void(unsigned int,  unsigned int,  struct 
transaction_run_stats_s *)’}
    877 02:35:35 DEBUG| [stdout]   245 | static inline 
void trace_##name(proto)  \
    878 02:35:35 DEBUG| [stdout]   |
^~
    879 

[Kernel-packages] [Bug 2017006] Proposed package removed from archive

2024-01-05 Thread Steve Langasek
The version of lttng-modules in the proposed pocket of Lunar that was
purported to fix this bug report has been removed because one or more
bugs that were to be fixed by the upload have failed verification and
been in this state for more than 10 days.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2017006

Title:
  fix build issue for v5.19 kernels (jammy-hwe, kinetic, lunar-riscv)

Status in linux package in Ubuntu:
  Invalid
Status in lttng-modules package in Ubuntu:
  Won't Fix
Status in linux source package in Focal:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in lttng-modules source package in Jammy:
  Won't Fix
Status in linux source package in Kinetic:
  Invalid
Status in lttng-modules source package in Kinetic:
  Won't Fix
Status in linux source package in Lunar:
  Invalid
Status in lttng-modules source package in Lunar:
  Won't Fix
Status in linux source package in Mantic:
  Invalid

Bug description:
  SRU Justification

  [ Impact ]

  Upstream stable added a change in the format of jbd2 in 5.15.87 that
  was cherry-picked to kinetic:linux.

  This is incompatible with the current changes in the lttng-module
  kinetic.

  We previously encountered this issue for focal 
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2004644
  and we proactively released a new version for kinetic.
  The problem is the fix does not really work as expected.

  As shown in the logs below,
  The build error is triggered because some function declaration does not match 
the kernel's.
  In `include/instrumentation/events/jbd2.h` in lttng-modules, there is a 
conditional declaration based on the kernel version. 5.19 is missing there, 
therefore kinetic will fall back to the old declaration. The reason 5.19 is not 
there is probably because this version has reached end of life last year.

  Build logs:
  35:35 DEBUG| [stdout] In file included from 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/define_trace.h:87,
    860 02:35:35 DEBUG| [stdout]  from 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:293,
    861 02:35:35 DEBUG| [stdout]  from 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:29:
    862 02:35:35 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:133:6:
 error: conflicting types for ‘trace_jbd2_run_stats’; have ‘void(dev_t,  long 
unsigned int,  struct transaction_run_stats_s *)’ {aka ‘void(unsigned int,  
long unsigned int,  struct transaction_run_stats_s *)’}
    863 02:35:35 DEBUG| [stdout]   133 | void 
trace_##_name(_proto);
    864 02:35:35 DEBUG| [stdout]   |  ^~
    865 02:35:35 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:45:9:
 note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP’
    866 02:35:35 DEBUG| [stdout]45 | 
LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP(map, name, map, PARAMS(proto), PARAMS(args))
    867 02:35:35 DEBUG| [stdout]   | 
^~~
    868 02:35:35 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:87:9:
 note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_MAP’
    869 02:35:35 DEBUG| [stdout]87 | 
LTTNG_TRACEPOINT_EVENT_MAP(name, name,  \
    870 02:35:35 DEBUG| [stdout]   | 
^~
    871 02:35:35 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:180:1:
 note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT’
    872 02:35:35 DEBUG| [stdout]   180 | 
LTTNG_TRACEPOINT_EVENT(jbd2_run_stats,
    873 02:35:35 DEBUG| [stdout]   | ^~
    874 02:35:35 DEBUG| [stdout] In file included from 
./include/trace/events/jbd2.h:9,
    875 02:35:35 DEBUG| [stdout]  from 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:18:
    876 02:35:35 DEBUG| [stdout] 
./include/linux/tracepoint.h:245:28: note: previous definition of 
‘trace_jbd2_run_stats’ with type ‘void(dev_t,  tid_t,  struct 
transaction_run_stats_s *)’ {aka ‘void(unsigned int,  unsigned int,  struct 
transaction_run_stats_s *)’}
    877 02:35:35 DEBUG| [stdout]   245 | static inline 
void trace_##name(proto)  \
    878 02:35:35 DEBUG| [stdout]   |
^~
    879 

[Kernel-packages] [Bug 2017006] Proposed package removed from archive

2024-01-05 Thread Steve Langasek
The version of lttng-modules in the proposed pocket of Jammy that was
purported to fix this bug report has been removed because one or more
bugs that were to be fixed by the upload have failed verification and
been in this state for more than 10 days.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2017006

Title:
  fix build issue for v5.19 kernels (jammy-hwe, kinetic, lunar-riscv)

Status in linux package in Ubuntu:
  Invalid
Status in lttng-modules package in Ubuntu:
  Won't Fix
Status in linux source package in Focal:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in lttng-modules source package in Jammy:
  Won't Fix
Status in linux source package in Kinetic:
  Invalid
Status in lttng-modules source package in Kinetic:
  Won't Fix
Status in linux source package in Lunar:
  Invalid
Status in lttng-modules source package in Lunar:
  Won't Fix
Status in linux source package in Mantic:
  Invalid

Bug description:
  SRU Justification

  [ Impact ]

  Upstream stable added a change in the format of jbd2 in 5.15.87 that
  was cherry-picked to kinetic:linux.

  This is incompatible with the current changes in the lttng-module
  kinetic.

  We previously encountered this issue for focal 
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2004644
  and we proactively released a new version for kinetic.
  The problem is the fix does not really work as expected.

  As shown in the logs below,
  The build error is triggered because some function declaration does not match 
the kernel's.
  In `include/instrumentation/events/jbd2.h` in lttng-modules, there is a 
conditional declaration based on the kernel version. 5.19 is missing there, 
therefore kinetic will fall back to the old declaration. The reason 5.19 is not 
there is probably because this version has reached end of life last year.

  Build logs:
  35:35 DEBUG| [stdout] In file included from 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/define_trace.h:87,
    860 02:35:35 DEBUG| [stdout]  from 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:293,
    861 02:35:35 DEBUG| [stdout]  from 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:29:
    862 02:35:35 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:133:6:
 error: conflicting types for ‘trace_jbd2_run_stats’; have ‘void(dev_t,  long 
unsigned int,  struct transaction_run_stats_s *)’ {aka ‘void(unsigned int,  
long unsigned int,  struct transaction_run_stats_s *)’}
    863 02:35:35 DEBUG| [stdout]   133 | void 
trace_##_name(_proto);
    864 02:35:35 DEBUG| [stdout]   |  ^~
    865 02:35:35 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:45:9:
 note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP’
    866 02:35:35 DEBUG| [stdout]45 | 
LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP(map, name, map, PARAMS(proto), PARAMS(args))
    867 02:35:35 DEBUG| [stdout]   | 
^~~
    868 02:35:35 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:87:9:
 note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_MAP’
    869 02:35:35 DEBUG| [stdout]87 | 
LTTNG_TRACEPOINT_EVENT_MAP(name, name,  \
    870 02:35:35 DEBUG| [stdout]   | 
^~
    871 02:35:35 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:180:1:
 note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT’
    872 02:35:35 DEBUG| [stdout]   180 | 
LTTNG_TRACEPOINT_EVENT(jbd2_run_stats,
    873 02:35:35 DEBUG| [stdout]   | ^~
    874 02:35:35 DEBUG| [stdout] In file included from 
./include/trace/events/jbd2.h:9,
    875 02:35:35 DEBUG| [stdout]  from 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:18:
    876 02:35:35 DEBUG| [stdout] 
./include/linux/tracepoint.h:245:28: note: previous definition of 
‘trace_jbd2_run_stats’ with type ‘void(dev_t,  tid_t,  struct 
transaction_run_stats_s *)’ {aka ‘void(unsigned int,  unsigned int,  struct 
transaction_run_stats_s *)’}
    877 02:35:35 DEBUG| [stdout]   245 | static inline 
void trace_##name(proto)  \
    878 02:35:35 DEBUG| [stdout]   |
^~
    879 

[Kernel-packages] [Bug 2017006] Proposed package removed from archive

2024-01-05 Thread Steve Langasek
The version of lttng-modules in the proposed pocket of Jammy that was
purported to fix this bug report has been removed because one or more
bugs that were to be fixed by the upload have failed verification and
been in this state for more than 10 days.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2017006

Title:
  fix build issue for v5.19 kernels (jammy-hwe, kinetic, lunar-riscv)

Status in linux package in Ubuntu:
  Invalid
Status in lttng-modules package in Ubuntu:
  Won't Fix
Status in linux source package in Focal:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in lttng-modules source package in Jammy:
  Won't Fix
Status in linux source package in Kinetic:
  Invalid
Status in lttng-modules source package in Kinetic:
  Won't Fix
Status in linux source package in Lunar:
  Invalid
Status in lttng-modules source package in Lunar:
  Won't Fix
Status in linux source package in Mantic:
  Invalid

Bug description:
  SRU Justification

  [ Impact ]

  Upstream stable added a change in the format of jbd2 in 5.15.87 that
  was cherry-picked to kinetic:linux.

  This is incompatible with the current changes in the lttng-module
  kinetic.

  We previously encountered this issue for focal 
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2004644
  and we proactively released a new version for kinetic.
  The problem is the fix does not really work as expected.

  As shown in the logs below,
  The build error is triggered because some function declaration does not match 
the kernel's.
  In `include/instrumentation/events/jbd2.h` in lttng-modules, there is a 
conditional declaration based on the kernel version. 5.19 is missing there, 
therefore kinetic will fall back to the old declaration. The reason 5.19 is not 
there is probably because this version has reached end of life last year.

  Build logs:
  35:35 DEBUG| [stdout] In file included from 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/define_trace.h:87,
    860 02:35:35 DEBUG| [stdout]  from 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:293,
    861 02:35:35 DEBUG| [stdout]  from 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:29:
    862 02:35:35 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:133:6:
 error: conflicting types for ‘trace_jbd2_run_stats’; have ‘void(dev_t,  long 
unsigned int,  struct transaction_run_stats_s *)’ {aka ‘void(unsigned int,  
long unsigned int,  struct transaction_run_stats_s *)’}
    863 02:35:35 DEBUG| [stdout]   133 | void 
trace_##_name(_proto);
    864 02:35:35 DEBUG| [stdout]   |  ^~
    865 02:35:35 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:45:9:
 note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP’
    866 02:35:35 DEBUG| [stdout]45 | 
LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP(map, name, map, PARAMS(proto), PARAMS(args))
    867 02:35:35 DEBUG| [stdout]   | 
^~~
    868 02:35:35 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:87:9:
 note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_MAP’
    869 02:35:35 DEBUG| [stdout]87 | 
LTTNG_TRACEPOINT_EVENT_MAP(name, name,  \
    870 02:35:35 DEBUG| [stdout]   | 
^~
    871 02:35:35 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:180:1:
 note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT’
    872 02:35:35 DEBUG| [stdout]   180 | 
LTTNG_TRACEPOINT_EVENT(jbd2_run_stats,
    873 02:35:35 DEBUG| [stdout]   | ^~
    874 02:35:35 DEBUG| [stdout] In file included from 
./include/trace/events/jbd2.h:9,
    875 02:35:35 DEBUG| [stdout]  from 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:18:
    876 02:35:35 DEBUG| [stdout] 
./include/linux/tracepoint.h:245:28: note: previous definition of 
‘trace_jbd2_run_stats’ with type ‘void(dev_t,  tid_t,  struct 
transaction_run_stats_s *)’ {aka ‘void(unsigned int,  unsigned int,  struct 
transaction_run_stats_s *)’}
    877 02:35:35 DEBUG| [stdout]   245 | static inline 
void trace_##name(proto)  \
    878 02:35:35 DEBUG| [stdout]   |
^~
    879 

[Kernel-packages] [Bug 2017006] Proposed package removed from archive

2024-01-05 Thread Steve Langasek
The version of lttng-modules in the proposed pocket of Jammy that was
purported to fix this bug report has been removed because one or more
bugs that were to be fixed by the upload have failed verification and
been in this state for more than 10 days.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2017006

Title:
  fix build issue for v5.19 kernels (jammy-hwe, kinetic, lunar-riscv)

Status in linux package in Ubuntu:
  Invalid
Status in lttng-modules package in Ubuntu:
  Won't Fix
Status in linux source package in Focal:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in lttng-modules source package in Jammy:
  Won't Fix
Status in linux source package in Kinetic:
  Invalid
Status in lttng-modules source package in Kinetic:
  Won't Fix
Status in linux source package in Lunar:
  Invalid
Status in lttng-modules source package in Lunar:
  Won't Fix
Status in linux source package in Mantic:
  Invalid

Bug description:
  SRU Justification

  [ Impact ]

  Upstream stable added a change in the format of jbd2 in 5.15.87 that
  was cherry-picked to kinetic:linux.

  This is incompatible with the current changes in the lttng-module
  kinetic.

  We previously encountered this issue for focal 
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2004644
  and we proactively released a new version for kinetic.
  The problem is the fix does not really work as expected.

  As shown in the logs below,
  The build error is triggered because some function declaration does not match 
the kernel's.
  In `include/instrumentation/events/jbd2.h` in lttng-modules, there is a 
conditional declaration based on the kernel version. 5.19 is missing there, 
therefore kinetic will fall back to the old declaration. The reason 5.19 is not 
there is probably because this version has reached end of life last year.

  Build logs:
  35:35 DEBUG| [stdout] In file included from 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/define_trace.h:87,
    860 02:35:35 DEBUG| [stdout]  from 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:293,
    861 02:35:35 DEBUG| [stdout]  from 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:29:
    862 02:35:35 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:133:6:
 error: conflicting types for ‘trace_jbd2_run_stats’; have ‘void(dev_t,  long 
unsigned int,  struct transaction_run_stats_s *)’ {aka ‘void(unsigned int,  
long unsigned int,  struct transaction_run_stats_s *)’}
    863 02:35:35 DEBUG| [stdout]   133 | void 
trace_##_name(_proto);
    864 02:35:35 DEBUG| [stdout]   |  ^~
    865 02:35:35 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:45:9:
 note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP’
    866 02:35:35 DEBUG| [stdout]45 | 
LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP(map, name, map, PARAMS(proto), PARAMS(args))
    867 02:35:35 DEBUG| [stdout]   | 
^~~
    868 02:35:35 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:87:9:
 note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_MAP’
    869 02:35:35 DEBUG| [stdout]87 | 
LTTNG_TRACEPOINT_EVENT_MAP(name, name,  \
    870 02:35:35 DEBUG| [stdout]   | 
^~
    871 02:35:35 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:180:1:
 note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT’
    872 02:35:35 DEBUG| [stdout]   180 | 
LTTNG_TRACEPOINT_EVENT(jbd2_run_stats,
    873 02:35:35 DEBUG| [stdout]   | ^~
    874 02:35:35 DEBUG| [stdout] In file included from 
./include/trace/events/jbd2.h:9,
    875 02:35:35 DEBUG| [stdout]  from 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:18:
    876 02:35:35 DEBUG| [stdout] 
./include/linux/tracepoint.h:245:28: note: previous definition of 
‘trace_jbd2_run_stats’ with type ‘void(dev_t,  tid_t,  struct 
transaction_run_stats_s *)’ {aka ‘void(unsigned int,  unsigned int,  struct 
transaction_run_stats_s *)’}
    877 02:35:35 DEBUG| [stdout]   245 | static inline 
void trace_##name(proto)  \
    878 02:35:35 DEBUG| [stdout]   |
^~
    879 

[Kernel-packages] [Bug 2017006] Proposed package removed from archive

2024-01-05 Thread Steve Langasek
The version of lttng-modules in the proposed pocket of Jammy that was
purported to fix this bug report has been removed because one or more
bugs that were to be fixed by the upload have failed verification and
been in this state for more than 10 days.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2017006

Title:
  fix build issue for v5.19 kernels (jammy-hwe, kinetic, lunar-riscv)

Status in linux package in Ubuntu:
  Invalid
Status in lttng-modules package in Ubuntu:
  Won't Fix
Status in linux source package in Focal:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in lttng-modules source package in Jammy:
  Won't Fix
Status in linux source package in Kinetic:
  Invalid
Status in lttng-modules source package in Kinetic:
  Won't Fix
Status in linux source package in Lunar:
  Invalid
Status in lttng-modules source package in Lunar:
  Won't Fix
Status in linux source package in Mantic:
  Invalid

Bug description:
  SRU Justification

  [ Impact ]

  Upstream stable added a change in the format of jbd2 in 5.15.87 that
  was cherry-picked to kinetic:linux.

  This is incompatible with the current changes in the lttng-module
  kinetic.

  We previously encountered this issue for focal 
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2004644
  and we proactively released a new version for kinetic.
  The problem is the fix does not really work as expected.

  As shown in the logs below,
  The build error is triggered because some function declaration does not match 
the kernel's.
  In `include/instrumentation/events/jbd2.h` in lttng-modules, there is a 
conditional declaration based on the kernel version. 5.19 is missing there, 
therefore kinetic will fall back to the old declaration. The reason 5.19 is not 
there is probably because this version has reached end of life last year.

  Build logs:
  35:35 DEBUG| [stdout] In file included from 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/define_trace.h:87,
    860 02:35:35 DEBUG| [stdout]  from 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:293,
    861 02:35:35 DEBUG| [stdout]  from 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:29:
    862 02:35:35 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:133:6:
 error: conflicting types for ‘trace_jbd2_run_stats’; have ‘void(dev_t,  long 
unsigned int,  struct transaction_run_stats_s *)’ {aka ‘void(unsigned int,  
long unsigned int,  struct transaction_run_stats_s *)’}
    863 02:35:35 DEBUG| [stdout]   133 | void 
trace_##_name(_proto);
    864 02:35:35 DEBUG| [stdout]   |  ^~
    865 02:35:35 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:45:9:
 note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP’
    866 02:35:35 DEBUG| [stdout]45 | 
LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP(map, name, map, PARAMS(proto), PARAMS(args))
    867 02:35:35 DEBUG| [stdout]   | 
^~~
    868 02:35:35 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:87:9:
 note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_MAP’
    869 02:35:35 DEBUG| [stdout]87 | 
LTTNG_TRACEPOINT_EVENT_MAP(name, name,  \
    870 02:35:35 DEBUG| [stdout]   | 
^~
    871 02:35:35 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:180:1:
 note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT’
    872 02:35:35 DEBUG| [stdout]   180 | 
LTTNG_TRACEPOINT_EVENT(jbd2_run_stats,
    873 02:35:35 DEBUG| [stdout]   | ^~
    874 02:35:35 DEBUG| [stdout] In file included from 
./include/trace/events/jbd2.h:9,
    875 02:35:35 DEBUG| [stdout]  from 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:18:
    876 02:35:35 DEBUG| [stdout] 
./include/linux/tracepoint.h:245:28: note: previous definition of 
‘trace_jbd2_run_stats’ with type ‘void(dev_t,  tid_t,  struct 
transaction_run_stats_s *)’ {aka ‘void(unsigned int,  unsigned int,  struct 
transaction_run_stats_s *)’}
    877 02:35:35 DEBUG| [stdout]   245 | static inline 
void trace_##name(proto)  \
    878 02:35:35 DEBUG| [stdout]   |
^~
    879 

[Kernel-packages] [Bug 2017006] Proposed package removed from archive

2023-07-21 Thread Łukasz Zemczak
The version of lttng-modules in the proposed pocket of Kinetic that was
purported to fix this bug report has been removed because one or more
bugs that were to be fixed by the upload have failed verification and
been in this state for more than 10 days.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2017006

Title:
  fix build issue for v5.19 kernels (jammy-hwe, kinetic, lunar-riscv)

Status in linux package in Ubuntu:
  In Progress
Status in lttng-modules package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  In Progress
Status in linux source package in Jammy:
  In Progress
Status in lttng-modules source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  In Progress
Status in lttng-modules source package in Kinetic:
  Confirmed
Status in linux source package in Lunar:
  In Progress
Status in lttng-modules source package in Lunar:
  Fix Committed
Status in linux source package in Mantic:
  In Progress

Bug description:
  SRU Justification

  [ Impact ]

  Upstream stable added a change in the format of jbd2 in 5.15.87 that
  was cherry-picked to kinetic:linux.

  This is incompatible with the current changes in the lttng-module
  kinetic.

  We previously encountered this issue for focal 
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2004644
  and we proactively released a new version for kinetic.
  The problem is the fix does not really work as expected.

  As shown in the logs below,
  The build error is triggered because some function declaration does not match 
the kernel's.
  In `include/instrumentation/events/jbd2.h` in lttng-modules, there is a 
conditional declaration based on the kernel version. 5.19 is missing there, 
therefore kinetic will fall back to the old declaration. The reason 5.19 is not 
there is probably because this version has reached end of life last year.

  Build logs:
  35:35 DEBUG| [stdout] In file included from 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/define_trace.h:87,
    860 02:35:35 DEBUG| [stdout]  from 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:293,
    861 02:35:35 DEBUG| [stdout]  from 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:29:
    862 02:35:35 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:133:6:
 error: conflicting types for ‘trace_jbd2_run_stats’; have ‘void(dev_t,  long 
unsigned int,  struct transaction_run_stats_s *)’ {aka ‘void(unsigned int,  
long unsigned int,  struct transaction_run_stats_s *)’}
    863 02:35:35 DEBUG| [stdout]   133 | void 
trace_##_name(_proto);
    864 02:35:35 DEBUG| [stdout]   |  ^~
    865 02:35:35 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:45:9:
 note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP’
    866 02:35:35 DEBUG| [stdout]45 | 
LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP(map, name, map, PARAMS(proto), PARAMS(args))
    867 02:35:35 DEBUG| [stdout]   | 
^~~
    868 02:35:35 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:87:9:
 note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_MAP’
    869 02:35:35 DEBUG| [stdout]87 | 
LTTNG_TRACEPOINT_EVENT_MAP(name, name,  \
    870 02:35:35 DEBUG| [stdout]   | 
^~
    871 02:35:35 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:180:1:
 note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT’
    872 02:35:35 DEBUG| [stdout]   180 | 
LTTNG_TRACEPOINT_EVENT(jbd2_run_stats,
    873 02:35:35 DEBUG| [stdout]   | ^~
    874 02:35:35 DEBUG| [stdout] In file included from 
./include/trace/events/jbd2.h:9,
    875 02:35:35 DEBUG| [stdout]  from 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:18:
    876 02:35:35 DEBUG| [stdout] 
./include/linux/tracepoint.h:245:28: note: previous definition of 
‘trace_jbd2_run_stats’ with type ‘void(dev_t,  tid_t,  struct 
transaction_run_stats_s *)’ {aka ‘void(unsigned int,  unsigned int,  struct 
transaction_run_stats_s *)’}
    877 02:35:35 DEBUG| [stdout]   245 | static inline 
void trace_##name(proto)  \
    878 02:35:35 DEBUG| [stdout]   |

[Kernel-packages] [Bug 2017006] Proposed package removed from archive

2023-07-21 Thread Łukasz Zemczak
The version of lttng-modules in the proposed pocket of Kinetic that was
purported to fix this bug report has been removed because one or more
bugs that were to be fixed by the upload have failed verification and
been in this state for more than 10 days.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2017006

Title:
  fix build issue for v5.19 kernels (jammy-hwe, kinetic, lunar-riscv)

Status in linux package in Ubuntu:
  In Progress
Status in lttng-modules package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  In Progress
Status in linux source package in Jammy:
  In Progress
Status in lttng-modules source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  In Progress
Status in lttng-modules source package in Kinetic:
  Confirmed
Status in linux source package in Lunar:
  In Progress
Status in lttng-modules source package in Lunar:
  Fix Committed
Status in linux source package in Mantic:
  In Progress

Bug description:
  SRU Justification

  [ Impact ]

  Upstream stable added a change in the format of jbd2 in 5.15.87 that
  was cherry-picked to kinetic:linux.

  This is incompatible with the current changes in the lttng-module
  kinetic.

  We previously encountered this issue for focal 
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2004644
  and we proactively released a new version for kinetic.
  The problem is the fix does not really work as expected.

  As shown in the logs below,
  The build error is triggered because some function declaration does not match 
the kernel's.
  In `include/instrumentation/events/jbd2.h` in lttng-modules, there is a 
conditional declaration based on the kernel version. 5.19 is missing there, 
therefore kinetic will fall back to the old declaration. The reason 5.19 is not 
there is probably because this version has reached end of life last year.

  Build logs:
  35:35 DEBUG| [stdout] In file included from 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/define_trace.h:87,
    860 02:35:35 DEBUG| [stdout]  from 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:293,
    861 02:35:35 DEBUG| [stdout]  from 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:29:
    862 02:35:35 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:133:6:
 error: conflicting types for ‘trace_jbd2_run_stats’; have ‘void(dev_t,  long 
unsigned int,  struct transaction_run_stats_s *)’ {aka ‘void(unsigned int,  
long unsigned int,  struct transaction_run_stats_s *)’}
    863 02:35:35 DEBUG| [stdout]   133 | void 
trace_##_name(_proto);
    864 02:35:35 DEBUG| [stdout]   |  ^~
    865 02:35:35 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:45:9:
 note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP’
    866 02:35:35 DEBUG| [stdout]45 | 
LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP(map, name, map, PARAMS(proto), PARAMS(args))
    867 02:35:35 DEBUG| [stdout]   | 
^~~
    868 02:35:35 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:87:9:
 note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_MAP’
    869 02:35:35 DEBUG| [stdout]87 | 
LTTNG_TRACEPOINT_EVENT_MAP(name, name,  \
    870 02:35:35 DEBUG| [stdout]   | 
^~
    871 02:35:35 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:180:1:
 note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT’
    872 02:35:35 DEBUG| [stdout]   180 | 
LTTNG_TRACEPOINT_EVENT(jbd2_run_stats,
    873 02:35:35 DEBUG| [stdout]   | ^~
    874 02:35:35 DEBUG| [stdout] In file included from 
./include/trace/events/jbd2.h:9,
    875 02:35:35 DEBUG| [stdout]  from 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:18:
    876 02:35:35 DEBUG| [stdout] 
./include/linux/tracepoint.h:245:28: note: previous definition of 
‘trace_jbd2_run_stats’ with type ‘void(dev_t,  tid_t,  struct 
transaction_run_stats_s *)’ {aka ‘void(unsigned int,  unsigned int,  struct 
transaction_run_stats_s *)’}
    877 02:35:35 DEBUG| [stdout]   245 | static inline 
void trace_##name(proto)  \
    878 02:35:35 DEBUG| [stdout]   |

[Kernel-packages] [Bug 2017006] Proposed package removed from archive

2023-07-21 Thread Łukasz Zemczak
The version of lttng-modules in the proposed pocket of Kinetic that was
purported to fix this bug report has been removed because one or more
bugs that were to be fixed by the upload have failed verification and
been in this state for more than 10 days.

** Changed in: lttng-modules (Ubuntu Kinetic)
   Status: Fix Committed => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2017006

Title:
  fix build issue for v5.19 kernels (jammy-hwe, kinetic, lunar-riscv)

Status in linux package in Ubuntu:
  In Progress
Status in lttng-modules package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  In Progress
Status in linux source package in Jammy:
  In Progress
Status in lttng-modules source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  In Progress
Status in lttng-modules source package in Kinetic:
  Confirmed
Status in linux source package in Lunar:
  In Progress
Status in lttng-modules source package in Lunar:
  Fix Committed
Status in linux source package in Mantic:
  In Progress

Bug description:
  SRU Justification

  [ Impact ]

  Upstream stable added a change in the format of jbd2 in 5.15.87 that
  was cherry-picked to kinetic:linux.

  This is incompatible with the current changes in the lttng-module
  kinetic.

  We previously encountered this issue for focal 
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2004644
  and we proactively released a new version for kinetic.
  The problem is the fix does not really work as expected.

  As shown in the logs below,
  The build error is triggered because some function declaration does not match 
the kernel's.
  In `include/instrumentation/events/jbd2.h` in lttng-modules, there is a 
conditional declaration based on the kernel version. 5.19 is missing there, 
therefore kinetic will fall back to the old declaration. The reason 5.19 is not 
there is probably because this version has reached end of life last year.

  Build logs:
  35:35 DEBUG| [stdout] In file included from 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/define_trace.h:87,
    860 02:35:35 DEBUG| [stdout]  from 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:293,
    861 02:35:35 DEBUG| [stdout]  from 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:29:
    862 02:35:35 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:133:6:
 error: conflicting types for ‘trace_jbd2_run_stats’; have ‘void(dev_t,  long 
unsigned int,  struct transaction_run_stats_s *)’ {aka ‘void(unsigned int,  
long unsigned int,  struct transaction_run_stats_s *)’}
    863 02:35:35 DEBUG| [stdout]   133 | void 
trace_##_name(_proto);
    864 02:35:35 DEBUG| [stdout]   |  ^~
    865 02:35:35 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:45:9:
 note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP’
    866 02:35:35 DEBUG| [stdout]45 | 
LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP(map, name, map, PARAMS(proto), PARAMS(args))
    867 02:35:35 DEBUG| [stdout]   | 
^~~
    868 02:35:35 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:87:9:
 note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_MAP’
    869 02:35:35 DEBUG| [stdout]87 | 
LTTNG_TRACEPOINT_EVENT_MAP(name, name,  \
    870 02:35:35 DEBUG| [stdout]   | 
^~
    871 02:35:35 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:180:1:
 note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT’
    872 02:35:35 DEBUG| [stdout]   180 | 
LTTNG_TRACEPOINT_EVENT(jbd2_run_stats,
    873 02:35:35 DEBUG| [stdout]   | ^~
    874 02:35:35 DEBUG| [stdout] In file included from 
./include/trace/events/jbd2.h:9,
    875 02:35:35 DEBUG| [stdout]  from 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:18:
    876 02:35:35 DEBUG| [stdout] 
./include/linux/tracepoint.h:245:28: note: previous definition of 
‘trace_jbd2_run_stats’ with type ‘void(dev_t,  tid_t,  struct 
transaction_run_stats_s *)’ {aka ‘void(unsigned int,  unsigned int,  struct 
transaction_run_stats_s *)’}
    877 02:35:35 DEBUG| [stdout]   245 | static inline 
void trace_##name(proto)   

[Kernel-packages] [Bug 2017006] Proposed package removed from archive

2023-07-21 Thread Łukasz Zemczak
The version of lttng-modules in the proposed pocket of Kinetic that was
purported to fix this bug report has been removed because one or more
bugs that were to be fixed by the upload have failed verification and
been in this state for more than 10 days.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2017006

Title:
  fix build issue for v5.19 kernels (jammy-hwe, kinetic, lunar-riscv)

Status in linux package in Ubuntu:
  In Progress
Status in lttng-modules package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  In Progress
Status in linux source package in Jammy:
  In Progress
Status in lttng-modules source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  In Progress
Status in lttng-modules source package in Kinetic:
  Confirmed
Status in linux source package in Lunar:
  In Progress
Status in lttng-modules source package in Lunar:
  Fix Committed
Status in linux source package in Mantic:
  In Progress

Bug description:
  SRU Justification

  [ Impact ]

  Upstream stable added a change in the format of jbd2 in 5.15.87 that
  was cherry-picked to kinetic:linux.

  This is incompatible with the current changes in the lttng-module
  kinetic.

  We previously encountered this issue for focal 
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2004644
  and we proactively released a new version for kinetic.
  The problem is the fix does not really work as expected.

  As shown in the logs below,
  The build error is triggered because some function declaration does not match 
the kernel's.
  In `include/instrumentation/events/jbd2.h` in lttng-modules, there is a 
conditional declaration based on the kernel version. 5.19 is missing there, 
therefore kinetic will fall back to the old declaration. The reason 5.19 is not 
there is probably because this version has reached end of life last year.

  Build logs:
  35:35 DEBUG| [stdout] In file included from 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/define_trace.h:87,
    860 02:35:35 DEBUG| [stdout]  from 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:293,
    861 02:35:35 DEBUG| [stdout]  from 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:29:
    862 02:35:35 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:133:6:
 error: conflicting types for ‘trace_jbd2_run_stats’; have ‘void(dev_t,  long 
unsigned int,  struct transaction_run_stats_s *)’ {aka ‘void(unsigned int,  
long unsigned int,  struct transaction_run_stats_s *)’}
    863 02:35:35 DEBUG| [stdout]   133 | void 
trace_##_name(_proto);
    864 02:35:35 DEBUG| [stdout]   |  ^~
    865 02:35:35 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:45:9:
 note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP’
    866 02:35:35 DEBUG| [stdout]45 | 
LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP(map, name, map, PARAMS(proto), PARAMS(args))
    867 02:35:35 DEBUG| [stdout]   | 
^~~
    868 02:35:35 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:87:9:
 note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_MAP’
    869 02:35:35 DEBUG| [stdout]87 | 
LTTNG_TRACEPOINT_EVENT_MAP(name, name,  \
    870 02:35:35 DEBUG| [stdout]   | 
^~
    871 02:35:35 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:180:1:
 note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT’
    872 02:35:35 DEBUG| [stdout]   180 | 
LTTNG_TRACEPOINT_EVENT(jbd2_run_stats,
    873 02:35:35 DEBUG| [stdout]   | ^~
    874 02:35:35 DEBUG| [stdout] In file included from 
./include/trace/events/jbd2.h:9,
    875 02:35:35 DEBUG| [stdout]  from 
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:18:
    876 02:35:35 DEBUG| [stdout] 
./include/linux/tracepoint.h:245:28: note: previous definition of 
‘trace_jbd2_run_stats’ with type ‘void(dev_t,  tid_t,  struct 
transaction_run_stats_s *)’ {aka ‘void(unsigned int,  unsigned int,  struct 
transaction_run_stats_s *)’}
    877 02:35:35 DEBUG| [stdout]   245 | static inline 
void trace_##name(proto)  \
    878 02:35:35 DEBUG| [stdout]   |