Skip to content

Release: merge master-next to master (2026-05-05)#15629

Merged
rpcme merged 31 commits into
masterfrom
master-next
May 5, 2026
Merged

Release: merge master-next to master (2026-05-05)#15629
rpcme merged 31 commits into
masterfrom
master-next

Conversation

@rpcme

@rpcme rpcme commented May 5, 2026

Copy link
Copy Markdown
Member

Weekly Release: master-next → master

Key Changes

CVE Status

  • Upstream CVE detected (not blocking — not a direct CVE in modified recipes)

meta-aws-maintainer and others added 30 commits April 28, 2026 02:50
Add XXH_NO_INLINE_HINTS=1 when DEBUG_BUILD is enabled to prevent
xxhash inline optimization issues during debug builds.

Co-authored-by: BinCaoWR <BinCaoWR@users.noreply.github.com>
Rebased from #15583
…lti-lib crashes

Remove 001-shared-static-crt-libs.patch which forces BUILD_SHARED_LIBS=OFF
for aws-crt-cpp and aws-c-iot, statically embedding them into each IoT
service .so. Combined with -Wl,-Bsymbolic, this isolates CRT globals per
.so, causing NULL allocator crashes when applications link against 2+ IoT
service libraries (e.g., IotSecureTunneling + IotJobs).

Root cause: file-static variables like s_aws_json_module_allocator in json.c
are only initialized by ApiHandle in the main binary. With -Bsymbolic and
static CRT, each .so copy stays NULL.

Restore FILES:${PN}-dev for CRT shared libs and RCONFLICTS:${PN} for
aws-c-iot (as the recipe had before commit 210a44d). The CRT now builds
as shared libraries with a single process-wide copy, which is how the
upstream SDK is designed to work.

Fixes: #15582
Reverts: 210a44d ("aws-iot-device-sdk-cpp-v2: disable sanitizer checks")
This patch forced BUILD_SHARED_LIBS=OFF for aws-crt-cpp and aws-c-iot,
causing runtime crashes when multiple IoT service .so files are linked.
Removed as part of the revert of commit 210a44d.

Fixes: #15582
@rpcme rpcme requested a review from a team as a code owner May 5, 2026 18:29
@rpcme rpcme merged commit 03d3ec1 into master May 5, 2026
8 of 12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants