From: Daniel Turull <[email protected]> The LTTng project documents its stable-branch policy in README.md, "Supported versions" at L171: fixes are backported to the last stable version unless they would break the ABI or API, and security fixes to the last two. So upgrades within a major.minor are stable point upgrades per the OE-Core stable release policy (ref-manual, "Stable Point Release Upgrades").
https://docs.yoctoproject.org/dev/ref-manual/release-process.html#stable-point-release-upgrades https://github.com/lttng/lttng-modules/blob/v2.15.2/README.md#supported-versions https://github.com/lttng/lttng-modules/tree/stable-2.15 This recipe's policy differs from the rest of the project in one respect worth stating. Where lttng-ust and lttng-tools do not backport new features at all, L185 says kernel-version enablement is backported to the last stable version. That is the only non-fix content a point release carries, and for a kernel tracer it keeps existing probes working against newer kernels rather than adding anything a user can call: no new options, no new API, no changed defaults. Upstream labels these entries "fix:" alongside the rest. Six branches are maintained in parallel, stable-2.11 through stable-2.16, and released from together: 2.14.6 and 2.15.2 the same day in June 2026, 2.14.5 and 2.15.1 in April, seven such days in the last two years. The ChangeLog entries for the current series are fixes throughout. 2.15.2 (Jun 19 2026) is 13 entries: a leaked file and fd on channel create error, plus twelve probe adjustments tracking kernel changes to ext4, btrfs, vfs, vmscan and hrtimer tracepoints. 2.15.1 (Apr 24 2026) is three, covering kallsyms on powerpc64 with ABI V1, a snd_soc_dapm_context move and a btrfs probe range. This recipe must share its minor version with lttng-ust and lttng-tools: lttng-tools README.adoc L123 states it supports the kernel and user space tracers "sharing the same _minor_ version", and that cross-version combinations are untested. Pinning the regex to the minor is what keeps that guarantee, permitting 2.15.x -> 2.15.y and excluding the 2.15 -> 2.16 bump that would need the three coordinated. Within a series they have never moved together on any branch: taking modules, tools and ust in turn, kirkstone ships 2.13.14, 2.13.9 and 2.13.6; scarthgap 2.13.12, 2.13.13 and 2.13.10; wrynose 2.14.4, 2.14.1 and 2.14.0. The minor agrees in every row and the patch in none, and scarthgap has lttng-tools ahead of this recipe rather than behind. There is no build dependency between them either. Already tracked this way on the OE stable branches, and more thoroughly than most: counting only bumps since each branch forked, kirkstone took 2.13.4 -> 2.13.5 -> 2.13.7 -> 2.13.8 -> 2.13.9 -> 2.13.14, scarthgap 2.13.9 -> 2.13.10 -> 2.13.11 -> 2.13.12, and wrynose 2.14.0 through 2.14.4. Each also carries local "fix build for kernel N" patches between those bumps, which is the burden that staying current within a series reduces. AI-Generated: Kiro with Claude Opus 5 Signed-off-by: Daniel Turull <[email protected]> --- meta/recipes-kernel/lttng/lttng-modules_2.15.2.bb | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/meta/recipes-kernel/lttng/lttng-modules_2.15.2.bb b/meta/recipes-kernel/lttng/lttng-modules_2.15.2.bb index 49f2bc8eb2..bfa1fc619a 100644 --- a/meta/recipes-kernel/lttng/lttng-modules_2.15.2.bb +++ b/meta/recipes-kernel/lttng/lttng-modules_2.15.2.bb @@ -7,6 +7,12 @@ LIC_FILES_CHKSUM = "file://LICENSE;md5=018e002dbdda3306682e394ddd65fa32" inherit module +# lttng-modules publishes bugfix/security-only releases on its per-minor +# stable-X.Y branches. Point releases also carry kernel-version enablement, +# which keeps existing probes working against newer kernels rather than adding +# user-visible functionality. +inherit upstream-stable-release-point + include lttng-platforms.inc SRC_URI = "https://lttng.org/files/${BPN}/${BPN}-${PV}.tar.bz2 \
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#243193): https://lists.openembedded.org/g/openembedded-core/message/243193 Mute This Topic: https://lists.openembedded.org/mt/120699776/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
