On Fri Oct 23, 2026 at 9:10 PM CEST, Sai Sireesha via lists.openembedded.org T 
wrote:
> Upgrade the systemd recipes to the 262.1 stable release.
>
> Update the source revisions and refresh the existing patches
> to apply against the updated upstream sources.
>
> Notable fixes in v262.1:
>   - logind: fix one-byte buffer overflow
>   - ndisc: fix an off by 2 write in ndisc_option_build_encrypted_dns()
>   - sd-bus: avoid overflow in sd_bus_message_append_{array,string}_memfd()
>   - firstboot: fix use-after-free/double-free in process_hostname()
>   - sd-event: fix hang after ratelimit expiry
>   - journal-file: refuse hash chains and field lists that loop back
>   - seccomp: mask socket() and setns() arguments to 32 bits
>   - kernel-image: handle errors when reading .osrel section
>   - udev-node: chase devlink on remove event
>
> Refresh the patch context for the updated upstream sources.
>
> Testing:
> - bitbake systemd
> - bitbake core-image-minimal
> - Booted core-image-minimal on qemux86-64
> - Verified systemd 262.1 as PID 1
> - Verified zero failed system units
> - Verified clean shutdown
>
> Signed-off-by: Sai Sireesha T <[email protected]>
> ---

Hi,

Thanks for the upgrade.

It looks like we have some warning during the do_rootfs, but without
much detail:

WARNING: core-image-full-cmdline-1.0-r0 do_rootfs: [log_check] 
core-image-full-cmdline: found 1 warning message in the logfile:
[log_check] warn.

https://autobuilder.yoctoproject.org/valkyrie/#/builders/20/builds/4830

This is only seen on qemux86 with altcfg distro. Can you have a look at
the issue?

Thanks,
Mathieu

-- 
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#248611): 
https://lists.openembedded.org/g/openembedded-core/message/248611
Mute This Topic: https://lists.openembedded.org/mt/121906069/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to