linux/poky.git/meta/recipes-kernel/lttng, branch 4.1_M2

lttng-modules: fix 5.19+ build

2022-07-04T21:51:49+00:00

We need to backport three patches from the lttng upstream tree to fix the build against 5.19+. Obviously we'll drop these once the next lttng-modules release is available. (From OE-Core rev: dce3c772efab4e51a82fb9c8fb74bc614ee3a82e) Signed-off-by: Bruce Ashfield Signed-off-by: Richard Purdie

lttng-modules: update 2.13.3 -> 2.13.4

2022-06-22T21:40:28+00:00

Drop backports; one of them (0009) is present only on the master branch and not on 2.13 branch, and so stays in the recipe. (From OE-Core rev: 1002941b76e0a0351e85a20e3e8d0a6a2254449c) Signed-off-by: Alexander Kanavin Signed-off-by: Luca Ceresoli Signed-off-by: Richard Purdie

lttng-modules: fix shell syntax

2022-06-08T20:52:12+00:00

* add missing space to fix: /bin/sh: 1: [: Illegal number: 119) shown in the log.do_compile (isn't fatal for the build) (From OE-Core rev: 8f785f35c8a9cdc0107fbaa76b20df5199159ee0) Signed-off-by: Martin Jansa Signed-off-by: Richard Purdie

lttng-ust: upgrade 2.13.2 -> 2.13.3

2022-06-07T20:21:55+00:00

Changelog: ========== * Document ust lock async-signal-safety * Fix: don't use strerror() from ust lock nocheck * Fix: remove non-async-signal-safe fflush from ERR() * Fix: Pointers are rejected by integer element compile time assertion for array and sequence * Fix: statedump: invalid read during iter_end * Fix: bytecode interpreter context_get_index() leaves byte order uninitialized (From OE-Core rev: d9d7b5d9fd8366bc4d2720e3396ab10f8b1ab6a0) Signed-off-by: Wang Mingyu Signed-off-by: Luca Ceresoli Signed-off-by: Richard Purdie

lttng-modules: Fix build failure for 5.10.119+ and 5.15.44+ kernel

2022-06-04T10:28:23+00:00

The following kernel commit has been back ported to v5.10.119 and v5.15.44. commit 14c174633f349cb41ea90c2c0aaddac157012f74 Author: Jason A. Donenfeld Date: Thu Feb 10 16:40:44 2022 +0100 random: remove unused tracepoints These explicit tracepoints aren't really used and show sign of aging. It's work to keep these up to date, and before I attempted to keep them up to date, they weren't up to date, which indicates that they're not really used. These days there are better ways of introspecting anyway. Which causes the following build failure lttng-modules-2.13.3/src/probes/lttng-probe-random.c:18:10: fatal error: trace/events/random.h: No such file or directory | 18 | #include | | ^~~~~~~~~~~~~~~~~~~~~~~ | compilation terminated. (From OE-Core rev: c8effd12cae7c7024f8e6c8f6ef70ed602d380ed) Signed-off-by: He Zhe Signed-off-by: Richard Purdie

lttng-modules: fix build against 5.18-rc7+

2022-05-21T07:34:16+00:00

lttng-modules fails to build against 5.18-rc7, the details of the fix are as follows: The commit [fix: sched/tracing: Don't re-read p->state when emitting sched_switch event (v5.18)] was correct, but the kernel changed their mind with the following commit: commit 9c2136be0878c88c53dea26943ce40bb03ad8d8d Author: Delyan Kratunov Date: Wed May 11 18:28:36 2022 +0000 sched/tracing: Append prev_state to tp args instead Commit fa2c3254d7cf (sched/tracing: Don't re-read p->state when emitting sched_switch event, 2022-01-20) added a new prev_state argument to the sched_switch tracepoint, before the prev task_struct pointer. This reordering of arguments broke BPF programs that use the raw tracepoint (e.g. tp_btf programs). The type of the second argument has changed and existing programs that assume a task_struct* argument (e.g. for bpf_task_storage access) will now fail to verify. If we instead append the new argument to the end, all existing programs would continue to work and can conditionally extract the prev_state argument on supported kernel versions. Fixes: fa2c3254d7cf (sched/tracing: Don't re-read p->state when emitting sched_switch event, 2022-01-20) Signed-off-by: Delyan Kratunov Signed-off-by: Peter Zijlstra (Intel) Acked-by: Steven Rostedt (Google) Link: https://lkml.kernel.org/r/c8a6930dfdd58a4a5755fc01732675472979732b.camel@fb.com By reordering the parameters (again) we can get back up and building. Upstream-Status: Backport (From OE-Core rev: fb69e5cfb043a15354beb2d613772aa0233d12ae) Signed-off-by: Bruce Ashfield Signed-off-by: Richard Purdie

lttng-tools: upgrade 2.13.4 -> 2.13.7

2022-05-05T20:17:37+00:00

(From OE-Core rev: c7e2901eacf3dcbd0c5bb91d2cc1d467b4a9aaf7) Signed-off-by: Alexander Kanavin Signed-off-by: Luca Ceresoli Signed-off-by: Richard Purdie

babeltrace: Disable warnings as errors

2022-04-19T13:14:11+00:00

These settings are good for developers/maintainers but for distributions generally disabling them turns out to be better especially when there is a knob to do so. This fixes build with gcc-12 which find additional warnings inlined from 'bt_ctf_object_set_parent' at ../../../git/src/ctf-writer/object.h:120:6, inlined from 'bt_ctf_trace_common_add_stream_class' at ../../../git/src/ctf-writer/trace.c:1243:3: ../../../git/src/ctf-writer/object.h:141:26: error: null pointer dereference [-Werror=null-dereference] 141 | if (child->parent) { | ~~~~~^~~~~~~~ ../../../git/src/ctf-writer/object.h:141:26: error: null pointer dereference [-Werror=null-dereference] cc1: all warnings being treated as errors (From OE-Core rev: 1898d10dd4d4372823e6c8b8c4ed28604e692365) Signed-off-by: Khem Raj Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie

lttng-modules: support kernel 5.18+

2022-04-14T15:46:35+00:00

Backporting changes from lttng master to support building against the 5.18+ kernel. No changes required to the patches. Once a new -stable 2.13.x is released, we can drop these patches. To enable newer kernel development against the LTS, it is worth pulling these in while we wait for an upstream release. (From OE-Core rev: 8a7237a47488442513741930ea55d69dd6bd7be4) Signed-off-by: Bruce Ashfield Signed-off-by: Richard Purdie

lttng-ust: upgrade 2.13.1 -> 2.13.2

2022-03-29T14:59:29+00:00

(From OE-Core rev: bdde01d83f52103c9a93a90f481bcf8f2e7b301f) Signed-off-by: Wang Mingyu Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie