diff mbox series

[1/7] util-linux: inherit upstream-stable-release-point

Message ID 20260731122522.1647968-2-daniel.turull@ericsson.com
State Under Review
Headers show
Series Mark recipes whose point releases are fixes-only (1/3) | expand

Commit Message

Daniel Turull July 31, 2026, 12:25 p.m. UTC 
From: Daniel Turull <daniel.turull@ericsson.com>

util-linux's README ("Stable Branches") documents stable/v<major>.<minor>
branches whose maintenance releases are bug fixes only, 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/util-linux/util-linux/blob/v2.42.2/README#L95

Checked the last point release for feature creep:

  2.42.2 (Jun 16 2026), against 2.42.1 (May 18 2026): 32 commits, all
  fixes or hardening -- memory safety (a libblkid use-after-free, two
  buffer overflows, a libfdisk GPT fix), privilege tightening
  (X-mount.subdir restricted for non-root), diagnostics (fanotify queue
  overflow detection) and documentation. No new options or behaviour.

These releases are not picked up on the OE stable branches: util-linux has
had zero point-release bumps on kirkstone, scarthgap or wrynose since each
branch forked from master, leaving them at 2.37.4, 2.39.3 and 2.41.3
respectively. This addresses that gap going forward.

This addresses the general case on master, where PV is 2.42.x. Since the
regex is derived from PV, an older branch scopes it to that branch's series,
and the 2.39 series scarthgap ships does not qualify. 2.39 adopted the new
kernel mount API, so 2.39.1 introduced
LIBMOUNT_FORCE_MOUNT2={always,never,auto} as, in its own words, "a stable
workaround for use cases where new kernel API is not ready to use"; the
series also took new CPU model support and libblkid bcachefs sub-device
label probing. That is a property of the 2.39 series rather than of the
project -- 2.42.2 is 32 commits of pure fixes -- but it means this must not
be backported unchanged, and each branch's series needs checking on its own.
For the avoidance of doubt it is not a development-series effect either:
util-linux has no development/stable version split, and pre-release work
goes to -rc tags.

AI-Generated: Kiro with Claude Opus 5
Signed-off-by: Daniel Turull <daniel.turull@ericsson.com>
---
 meta/recipes-core/util-linux/util-linux.inc | 4 ++++
 1 file changed, 4 insertions(+)
diff mbox series

Patch

diff --git a/meta/recipes-core/util-linux/util-linux.inc b/meta/recipes-core/util-linux/util-linux.inc
index 460b996403..c22b599f1a 100644
--- a/meta/recipes-core/util-linux/util-linux.inc
+++ b/meta/recipes-core/util-linux/util-linux.inc
@@ -22,3 +22,7 @@  SRC_URI = "${KERNELORG_MIRROR}/linux/utils/util-linux/v${MAJOR_VERSION}/util-lin
 SRC_URI[sha256sum] = "03a05d3adf9602ef128f2da05b84b3205ce60c351e5737c0370f74000679ce8a"
 
 CVE_PRODUCT = "util-linux"
+
+# util-linux publishes bugfix/security-only point releases on its
+# stable/v<major.minor> branches.
+inherit upstream-stable-release-point