This is more of an RFC than an actual review request. Currently, the yocto CVE checker fails to report CVEs in docker, due to mismatch of the package names (eg "docker-moby" versus just "docker" in

Hello Bruce when openvswitch enable DPDK, the do_configure will trigger follow error: checking whether dpdk is enabled... yes | checking for rte_config.h... yes | checking whether

Bumping to 19.03.15 to pickup bugfixes and security changes. The following commits comprise the change: 420b1d3625 pull: Validate layer digest format 5472f39022 buildkit: Apply apparmor

From: Saul Wold <Saul.Wold@...> This updates the Ceph version to 16.2.1 which required a couple changes to base code via a rebased patch which also disabled the sanity check due to it not

Acked-by: Martin Jansa <Martin.Jansa@...> Thanks!

What's the base for this ? I've tried it with and without your previous upgrade patch, and it won't apply in either case. I just pushed a new master branch for the libseccomp fixes, it is probably

This updates the Ceph version to 16.2.1 which required a couple changes to base code via a rebased patch which also disabled the sanity check due to it not working correctly, but the actual compile

Dang, I thought I took care of that. Maybe something happened with Devtool, strange. Ok, I figured out what happened, Version 2 coming, there is some other missing change. I did not see this, I will

<Daniel.Dragomir@...> wrote: I didn't currently have a plan to do that backport, since it is a major version bump and missed when I had to branch for the release. But if someone can

Signed-off-by: Trevor Gamblin <trevor.gamblin@...> --- .../containerd/files/CVE-2021-3121.patch | 849 +++++++++--------- 1 file changed, 423 insertions(+), 426 deletions(-) diff

Hi Bruce! Do you know when this patch will be back-ported on hardknott? Currently in only on master: 9f35986 (HEAD -> master, origin/master, origin/HEAD) libvirt: uprev v6.3 -> v7.2 Thanks, Daniel

argh. My bad, that should be "master-ceph" Bruce -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II

I had to adjust the hashes to get this to download, and once I did that, I had to limit the build to avoid OOM, and then ran into this: 24 -Wpessimizing-move -Wredundant-move

Add a new xen-rpi-u-boot-scr recipe to PROVIDE u-boot-default-script instead of using a bbappend to rpi-u-boot-scr. This allows the new recipe to be selected by indicating it as PREFERRED_PROVIDER of

Improve meta-virt-xen.inc by moving all the Raspberry Pi 4 config settings to a new xen-raspberrypi4-64.inc file in the raspberrypi dynamic layer. The new .inc file is included only for the

Apply update to the device tree to allow Xen 4.14 to boot. Suggested-by: Bertrand Marquis <bertrand.marquis@...> Signed-off-by: Christopher Clark <christopher.w.clark@...> ---

fatload needs to read from mmc 1:1 to find the Xen hypervisor and Linux kernel binaries with the current Yocto Linux 5.10 kernel. Add boot messages to to the u-boot script to indicate the size of

The 5.10 version of the Linux Yocto kernel supports running Xen on the Raspberry Pi 4, so the previous preference for linux-yocto-dev can be replaced. Use the ?= operator to set the kernel preference

Added to the raspberrypi dynamic layer for use with Xen as preparation for switching to it as the default preference. Signed-off-by: Christopher Clark <christopher.w.clark@...> ---

Since upstream Xen 4.14 and 4.15 have working default configs for Xen on the Raspberry Pi 4, the defconfig and bbappend in the raspberrypi dynamic layer can now be removed. Signed-off-by: Christopher