[OE-core] Patchtest results for [PATCH] scripts/oe-setup-build: write a build environment initialization one-liner into the build directory
Thank you for your submission. Patchtest identified one or more issues with the patch. Please see the log below for more information: --- Testing patch /home/patchtest/share/mboxes/scripts-oe-setup-build-write-a-build-environment-initialization-one-liner-into-the-build-directory.patch FAIL: test shortlog length: Edit shortlog so that it is 90 characters or less (currently 99 characters) (test_mbox.TestMbox.test_shortlog_length) PASS: test Signed-off-by presence (test_mbox.TestMbox.test_signed_off_by_presence) PASS: test author valid (test_mbox.TestMbox.test_author_valid) PASS: test commit message presence (test_mbox.TestMbox.test_commit_message_presence) PASS: test max line length (test_metadata.TestMetadata.test_max_line_length) PASS: test mbox format (test_mbox.TestMbox.test_mbox_format) PASS: test non-AUH upgrade (test_mbox.TestMbox.test_non_auh_upgrade) PASS: test shortlog format (test_mbox.TestMbox.test_shortlog_format) SKIP: pretest pylint: No python related patches, skipping test (test_python_pylint.PyLint.pretest_pylint) SKIP: pretest src uri left files: No modified recipes, skipping pretest (test_metadata.TestMetadata.pretest_src_uri_left_files) SKIP: test CVE check ignore: No modified recipes or older target branch, skipping test (test_metadata.TestMetadata.test_cve_check_ignore) SKIP: test CVE tag format: No new CVE patches introduced (test_patch.TestPatch.test_cve_tag_format) SKIP: test Signed-off-by presence: No new CVE patches introduced (test_patch.TestPatch.test_signed_off_by_presence) SKIP: test Upstream-Status presence: No new CVE patches introduced (test_patch.TestPatch.test_upstream_status_presence_format) SKIP: test bugzilla entry format: No bug ID found (test_mbox.TestMbox.test_bugzilla_entry_format) SKIP: test lic files chksum modified not mentioned: No modified recipes, skipping test (test_metadata.TestMetadata.test_lic_files_chksum_modified_not_mentioned) SKIP: test lic files chksum presence: No added recipes, skipping test (test_metadata.TestMetadata.test_lic_files_chksum_presence) SKIP: test license presence: No added recipes, skipping test (test_metadata.TestMetadata.test_license_presence) SKIP: test pylint: No python related patches, skipping test (test_python_pylint.PyLint.test_pylint) SKIP: test series merge on head: Merge test is disabled for now (test_mbox.TestMbox.test_series_merge_on_head) SKIP: test src uri left files: No modified recipes, skipping pretest (test_metadata.TestMetadata.test_src_uri_left_files) SKIP: test summary presence: No added recipes, skipping test (test_metadata.TestMetadata.test_summary_presence) SKIP: test target mailing list: Series merged, no reason to check other mailing lists (test_mbox.TestMbox.test_target_mailing_list) --- Please address the issues identified and submit a new revision of the patch, or alternatively, reply to this email with an explanation of why the patch should be accepted. If you believe these results are due to an error in patchtest, please submit a bug at https://bugzilla.yoctoproject.org/ (use the 'Patchtest' category under 'Yocto Project Subprojects'). For more information on specific failures, see: https://wiki.yoctoproject.org/wiki/Patchtest. Thank you! -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#196625): https://lists.openembedded.org/g/openembedded-core/message/196625 Mute This Topic: https://lists.openembedded.org/mt/104740471/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[OE-core] Patchtest results for [PATCH] xz: correct upstream version check
Thank you for your submission. Patchtest identified one or more issues with the patch. Please see the log below for more information: --- Testing patch /home/patchtest/share/mboxes/xz-correct-upstream-version-check.patch FAIL: test commit message presence: Please include a commit message on your patch explaining the change (test_mbox.TestMbox.test_commit_message_presence) PASS: pretest src uri left files (test_metadata.TestMetadata.pretest_src_uri_left_files) PASS: test CVE check ignore (test_metadata.TestMetadata.test_cve_check_ignore) PASS: test Signed-off-by presence (test_mbox.TestMbox.test_signed_off_by_presence) PASS: test author valid (test_mbox.TestMbox.test_author_valid) PASS: test lic files chksum modified not mentioned (test_metadata.TestMetadata.test_lic_files_chksum_modified_not_mentioned) PASS: test max line length (test_metadata.TestMetadata.test_max_line_length) PASS: test mbox format (test_mbox.TestMbox.test_mbox_format) PASS: test non-AUH upgrade (test_mbox.TestMbox.test_non_auh_upgrade) PASS: test shortlog format (test_mbox.TestMbox.test_shortlog_format) PASS: test shortlog length (test_mbox.TestMbox.test_shortlog_length) PASS: test src uri left files (test_metadata.TestMetadata.test_src_uri_left_files) SKIP: pretest pylint: No python related patches, skipping test (test_python_pylint.PyLint.pretest_pylint) SKIP: test CVE tag format: No new CVE patches introduced (test_patch.TestPatch.test_cve_tag_format) SKIP: test Signed-off-by presence: No new CVE patches introduced (test_patch.TestPatch.test_signed_off_by_presence) SKIP: test Upstream-Status presence: No new CVE patches introduced (test_patch.TestPatch.test_upstream_status_presence_format) SKIP: test bugzilla entry format: No bug ID found (test_mbox.TestMbox.test_bugzilla_entry_format) SKIP: test lic files chksum presence: No added recipes, skipping test (test_metadata.TestMetadata.test_lic_files_chksum_presence) SKIP: test license presence: No added recipes, skipping test (test_metadata.TestMetadata.test_license_presence) SKIP: test pylint: No python related patches, skipping test (test_python_pylint.PyLint.test_pylint) SKIP: test series merge on head: Merge test is disabled for now (test_mbox.TestMbox.test_series_merge_on_head) SKIP: test summary presence: No added recipes, skipping test (test_metadata.TestMetadata.test_summary_presence) SKIP: test target mailing list: Series merged, no reason to check other mailing lists (test_mbox.TestMbox.test_target_mailing_list) --- Please address the issues identified and submit a new revision of the patch, or alternatively, reply to this email with an explanation of why the patch should be accepted. If you believe these results are due to an error in patchtest, please submit a bug at https://bugzilla.yoctoproject.org/ (use the 'Patchtest' category under 'Yocto Project Subprojects'). For more information on specific failures, see: https://wiki.yoctoproject.org/wiki/Patchtest. Thank you! -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#196626): https://lists.openembedded.org/g/openembedded-core/message/196626 Mute This Topic: https://lists.openembedded.org/mt/104740472/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [PATCH] xz: correct upstream version check
Signed-off-by: Alexander Kanavin
---
meta/recipes-extended/xz/xz_5.4.6.bb | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/meta/recipes-extended/xz/xz_5.4.6.bb
b/meta/recipes-extended/xz/xz_5.4.6.bb
index 6c13e7ebe59..da3b75a10b0 100644
--- a/meta/recipes-extended/xz/xz_5.4.6.bb
+++ b/meta/recipes-extended/xz/xz_5.4.6.bb
@@ -28,7 +28,8 @@ SRC_URI =
"https://github.com/tukaani-project/xz/releases/download/v${PV}/xz-${P
file://run-ptest \
"
SRC_URI[sha256sum] =
"aeba3e03bf8140ddedf62a0a367158340520f6b384f75ca6045ccc6c0d43fd5c"
-UPSTREAM_CHECK_REGEX = "xz-(?P\d+(\.\d+)+)\.tar"
+UPSTREAM_CHECK_REGEX = "releases/tag/v(?P\d+(\.\d+)+)"
+UPSTREAM_CHECK_URI = "https://github.com/tukaani-project/xz/releases/;
CACHED_CONFIGUREVARS += "gl_cv_posix_shell=/bin/sh"
--
2.39.2
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196624):
https://lists.openembedded.org/g/openembedded-core/message/196624
Mute This Topic: https://lists.openembedded.org/mt/104740371/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [PATCH] scripts/oe-setup-build: write a build environment initialization one-liner into the build directory
With this, users no longer have to know where oe-init-build-env is relative to
the
build directory; that information is contained in the one liner and then
it's possible to simply use that:
. /path/to/build/init-build-env
This will particularly help with initializing builds in unpacked
build bundles, as users won't have to know where oe-init-build-env
is in the bundle directory tree - similar to esdk initialization.
Signed-off-by: Alexander Kanavin
---
scripts/oe-setup-build | 11 ++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/scripts/oe-setup-build b/scripts/oe-setup-build
index 5364f2b4812..c0476992a2a 100755
--- a/scripts/oe-setup-build
+++ b/scripts/oe-setup-build
@@ -91,7 +91,16 @@ def setup_build_env(args):
builddir = args.b if args.b else template["buildpath"]
no_shell = args.no_shell
coredir =
os.path.abspath(os.path.join(os.path.dirname(os.path.realpath(__file__)), '..'))
-cmd = "TEMPLATECONF={} . {} {}".format(template["templatepath"],
os.path.join(coredir, 'oe-init-build-env'), builddir)
+cmd_base = ". {} {}".format(os.path.join(coredir, 'oe-init-build-env'),
os.path.abspath(builddir))
+
+initbuild = os.path.join(builddir, 'init-build-env')
+if not os.path.exists(initbuild):
+os.makedirs(builddir, exist_ok=True)
+with open(initbuild, 'w') as f:
+f.write(cmd_base)
+print("\nRun '. {}' to initialize the build in a current shell
session.\n".format(initbuild))
+
+cmd = "TEMPLATECONF={} {}".format(template["templatepath"], cmd_base)
if not no_shell:
cmd = cmd + " && {}".format(os.environ['SHELL'])
print("Running:", cmd)
--
2.39.2
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196623):
https://lists.openembedded.org/g/openembedded-core/message/196623
Mute This Topic: https://lists.openembedded.org/mt/104740367/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [PATCH v2] image-live.bbclass: Adjust the default value for INITRD_LIVE
From: Kevin Hao
The ${INITRAMFS_FSTYPES} may contains multi filesystem types,
such as "cpio.gz cpio.xz". So it can't be used directly in setting
of the default INITRD_LIVE. We choose the first filesystem type
in ${INITRAMFS_FSTYPES} for the default INITRD_LIVE.
Signed-off-by: Kevin Hao
---
v2: Drop the adding of ${IMAGE_NAME_SUFFIX}.
meta/classes-recipe/image-live.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/classes-recipe/image-live.bbclass
b/meta/classes-recipe/image-live.bbclass
index da919d52f983..d2e95ef51c3a 100644
--- a/meta/classes-recipe/image-live.bbclass
+++ b/meta/classes-recipe/image-live.bbclass
@@ -38,7 +38,7 @@ do_bootimg[depends] += "dosfstools-native:do_populate_sysroot
\
LABELS_LIVE ?= "boot install"
ROOT_LIVE ?= "root=/dev/ram0"
INITRD_IMAGE_LIVE ?= "${MLPREFIX}core-image-minimal-initramfs"
-INITRD_LIVE ?=
"${DEPLOY_DIR_IMAGE}/${INITRD_IMAGE_LIVE}${IMAGE_MACHINE_SUFFIX}.${INITRAMFS_FSTYPES}"
+INITRD_LIVE ?=
"${DEPLOY_DIR_IMAGE}/${INITRD_IMAGE_LIVE}${IMAGE_MACHINE_SUFFIX}.${@d.getVar('INITRAMFS_FSTYPES').split()[0]}"
LIVE_ROOTFS_TYPE ?= "ext4"
ROOTFS ?= "${IMGDEPLOYDIR}/${IMAGE_LINK_NAME}.${LIVE_ROOTFS_TYPE}"
--
2.43.2
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196622):
https://lists.openembedded.org/g/openembedded-core/message/196622
Mute This Topic: https://lists.openembedded.org/mt/104739998/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] [PATCH] image-live.bbclass: Adjust the default value for INITRD_LIVE
On Tue, Mar 05, 2024 at 12:11:51AM +, Richard Purdie wrote:
> On Sun, 2024-03-03 at 14:54 +0800, Kevin Hao wrote:
> > From: Kevin Hao
> >
> > - After the commit 26d97acc7137 ("image-artifact-names: include
> > ${IMAGE_NAME_SUFFIX} directly in both ${IMAGE_NAME} and
> > ${IMAGE_LINK_NAME}"), the image names have changed from
> > core-image-minimal-qemux86-64-20230307181808.rootfs.ext4
> > core-image-minimal-qemux86-64.ext4
> > to
> > core-image-minimal-qemux86-64.rootfs-20230307181456.ext4
> > core-image-minimal-qemux86-64.rootfs.ext4
> > So we also need to add ${IMAGE_NAME_SUFFIX} to the default INITRD_LIVE.
> >
> > - The ${INITRAMFS_FSTYPES} may contains multi filesystem types,
> > such as "cpio.gz cpio.xz". So it can't be used directly in setting
> > of the default INITRD_LIVE. We choose the first filesystem type
> > in ${INITRAMFS_FSTYPES} for the default INITRD_LIVE.
> >
> > Signed-off-by: Kevin Hao
> > ---
> > meta/classes-recipe/image-live.bbclass | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
>
> I think this causes:
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/58/builds/8468/steps/11/logs/stdio
>
> unfortunately.
Sorry, my default. ${IMAGE_NAME_SUFFIX} shouldn't be added to INITRD_LIVE. V2
is coming.
Thanks,
Kevin
signature.asc
Description: PGP signature
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196621):
https://lists.openembedded.org/g/openembedded-core/message/196621
Mute This Topic: https://lists.openembedded.org/mt/104699273/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] [PATCH] glibc: fix multilib headers conflict for arm
On 3/5/24 01:00, Richard Purdie wrote: On Mon, 2024-03-04 at 09:12 +0800, Kai Kang wrote: From: Kai Kang The header files conflic when multilib enabled for arm: Error: Transaction test error: file /usr/include/finclude/math-vector-fortran.h conflicts between attempted installs of lib32-libc6-dev-2.39+git0+312e159626-r0.armv7at2hf_neon and libc6-dev-2.39+git0+312e159626-r0.cortexa72 Invoke function oe_multilib_header to resolve it. Signed-off-by: Kai Kang --- meta/recipes-core/glibc/glibc-package.inc | 2 ++ 1 file changed, 2 insertions(+) It may fix conflicts but it appears to break the fortran compiler: https://autobuilder.yoctoproject.org/typhoon/#/builders/127/builds/2987/steps/14/logs/stdio I've not specifically bisected it to this but it does seem most likely. OK. I'll figure it out. Regards, kai Cheers, Richard -- Kai Kang Wind River Linux -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#196620): https://lists.openembedded.org/g/openembedded-core/message/196620 Mute This Topic: https://lists.openembedded.org/mt/104714533/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] [PATCH] image-live.bbclass: Adjust the default value for INITRD_LIVE
On Sun, 2024-03-03 at 14:54 +0800, Kevin Hao wrote:
> From: Kevin Hao
>
> - After the commit 26d97acc7137 ("image-artifact-names: include
> ${IMAGE_NAME_SUFFIX} directly in both ${IMAGE_NAME} and
> ${IMAGE_LINK_NAME}"), the image names have changed from
> core-image-minimal-qemux86-64-20230307181808.rootfs.ext4
> core-image-minimal-qemux86-64.ext4
> to
> core-image-minimal-qemux86-64.rootfs-20230307181456.ext4
> core-image-minimal-qemux86-64.rootfs.ext4
> So we also need to add ${IMAGE_NAME_SUFFIX} to the default INITRD_LIVE.
>
> - The ${INITRAMFS_FSTYPES} may contains multi filesystem types,
> such as "cpio.gz cpio.xz". So it can't be used directly in setting
> of the default INITRD_LIVE. We choose the first filesystem type
> in ${INITRAMFS_FSTYPES} for the default INITRD_LIVE.
>
> Signed-off-by: Kevin Hao
> ---
> meta/classes-recipe/image-live.bbclass | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
I think this causes:
https://autobuilder.yoctoproject.org/typhoon/#/builders/58/builds/8468/steps/11/logs/stdio
unfortunately.
Cheers,
Richard
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196619):
https://lists.openembedded.org/g/openembedded-core/message/196619
Mute This Topic: https://lists.openembedded.org/mt/104699273/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] [PATCH 1/2] kernel-module-dirs.bbclass: Add class
On Mon, 2024-03-04 at 19:10 +, Peter Kjellerstedt wrote: > > > I mean something more like meta/conf/image-uefi.conf but kernel focused. > > Hmm, the naming of that file messes with the expectations I've learnt over > the years of working with OE. I've always thought that .conf files are > used for definitions that are part of the global configuration, and .inc > files are used for more local definitions. While I of course know that > there is no technical difference between the two, that kind of semantics > is helpful when looking at an individual file to know the context in which > it is used. > > > > > We need to do better about more focused conf/inc files. > > In that regard, kernel-module-dirs.bbclass was very focused. ;) > > Do you see a difference in, e.g., kernel-module-dirs.bbclass vs. > kernel-module-dirs.inc? I.e., why is an .inc (or .conf) file more suitable > than a .bbclass file in this case? There is a big difference, please step back and try and think about the bigger picture on this and other variable definitions. > One reason I can see for why a .bbclass would be preferred, is because it > is only inherited once even if there are multiple inherits. E.g., say I > would take the proposed kernel-module-dirs.bbclass and turn it into a more > generic kernel-vars.inc file. This file would then most likely be needed > by, e.g., kernel.bbclass and module.bbclass. However, based on its current > contents, it would also be needed by kernel-module-split.bbclass that both > of them inherit. But since it is an .inc file, requiring it from both > kernel.bbclass and kernel-module-split.bbclass would result in a lot of > warnings about duplicate inclusion. On the other hand, having > kernel-module-split.bbclass rely on that whatever inherits it has already > required the kernel-vars.inc file seems wrong. What we have today with all the ever increasing maze of ever smaller bbclass files also seems very wrong. I'm trying to give some pointers about what I might find more acceptable since I very much doubt you'd accept an outright "no". Yes, what I'm proposing also isn't perfect and yes, we might need to work on actually improving some of the infrastructure if necessary but so be it, we need to try and improve this rather than making it worse. I'd also highlight that choosing to try and do this now at feature freeze is really not helpful. I do not have the time to spend on this right now. Cheers, Richard -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#196618): https://lists.openembedded.org/g/openembedded-core/message/196618 Mute This Topic: https://lists.openembedded.org/mt/104724883/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [PATCH] bmaptool: now part of Yocto Project
The bmaptool (previously: bmap-tools, bmap-tool, bmaptool) has been moved
to be under the Yocto Project umbrella and is now hosted at:
github.com/yoctoproject/bmaptool
Signed-off-by: Trevor Woerner
---
meta/classes-recipe/image_types.bbclass | 2 +-
meta/classes-recipe/image_types_wic.bbclass | 2 +-
meta/conf/distro/include/maintainers.inc | 2 +-
.../bmap-tools_git.bb => bmaptool/bmaptool_git.bb}| 8
.../files/0001-BmapCopy.py-fix-error-message.patch| 0
...0002-CLI.py-fix-block-device-udev-race-condition.patch | 0
.../0003-BmapCopy.py-tweak-suggested-udev-rule.patch | 0
7 files changed, 7 insertions(+), 7 deletions(-)
rename meta/recipes-support/{bmap-tools/bmap-tools_git.bb =>
bmaptool/bmaptool_git.bb} (78%)
rename meta/recipes-support/{bmap-tools =>
bmaptool}/files/0001-BmapCopy.py-fix-error-message.patch (100%)
rename meta/recipes-support/{bmap-tools =>
bmaptool}/files/0002-CLI.py-fix-block-device-udev-race-condition.patch (100%)
rename meta/recipes-support/{bmap-tools =>
bmaptool}/files/0003-BmapCopy.py-tweak-suggested-udev-rule.patch (100%)
diff --git a/meta/classes-recipe/image_types.bbclass
b/meta/classes-recipe/image_types.bbclass
index 3733bdfc20c6..4ad13b43677a 100644
--- a/meta/classes-recipe/image_types.bbclass
+++ b/meta/classes-recipe/image_types.bbclass
@@ -363,7 +363,7 @@ CONVERSION_DEPENDS_zip = "zip-native"
CONVERSION_DEPENDS_7zip = "p7zip-native"
CONVERSION_DEPENDS_zst = "zstd-native"
CONVERSION_DEPENDS_sum = "mtd-utils-native"
-CONVERSION_DEPENDS_bmap = "bmap-tools-native"
+CONVERSION_DEPENDS_bmap = "bmaptool-native"
CONVERSION_DEPENDS_u-boot = "u-boot-tools-native"
CONVERSION_DEPENDS_vmdk = "qemu-system-native"
CONVERSION_DEPENDS_vdi = "qemu-system-native"
diff --git a/meta/classes-recipe/image_types_wic.bbclass
b/meta/classes-recipe/image_types_wic.bbclass
index ce7125f6f18f..cf3be909b30c 100644
--- a/meta/classes-recipe/image_types_wic.bbclass
+++ b/meta/classes-recipe/image_types_wic.bbclass
@@ -106,7 +106,7 @@ do_image_wic[recrdeptask] += "do_deploy"
do_image_wic[deptask] += "do_image_complete"
WKS_FILE_DEPENDS_DEFAULT = '${@bb.utils.contains_any("BUILD_ARCH", [ 'x86_64',
'i686' ], "syslinux-native", "",d)}'
-WKS_FILE_DEPENDS_DEFAULT += "bmap-tools-native cdrtools-native
btrfs-tools-native squashfs-tools-native e2fsprogs-native erofs-utils-native"
+WKS_FILE_DEPENDS_DEFAULT += "bmaptool-native cdrtools-native
btrfs-tools-native squashfs-tools-native e2fsprogs-native erofs-utils-native"
# Unified kernel images need objcopy
WKS_FILE_DEPENDS_DEFAULT += "virtual/${TARGET_PREFIX}binutils"
WKS_FILE_DEPENDS_BOOTLOADERS = ""
diff --git a/meta/conf/distro/include/maintainers.inc
b/meta/conf/distro/include/maintainers.inc
index 7e17e9b71fa0..a3433f496cb4 100644
--- a/meta/conf/distro/include/maintainers.inc
+++ b/meta/conf/distro/include/maintainers.inc
@@ -70,7 +70,7 @@ RECIPE_MAINTAINER:pn-bison = "Chen Qi "
RECIPE_MAINTAINER:pn-blktool = "Yi Zhao "
RECIPE_MAINTAINER:pn-blktrace = "Alexander Kanavin "
RECIPE_MAINTAINER:pn-bluez5 = "Anuj Mittal "
-RECIPE_MAINTAINER:pn-bmap-tools = "Anuj Mittal "
+RECIPE_MAINTAINER:pn-bmaptool = "Trevor Woerner "
RECIPE_MAINTAINER:pn-boost = "Alexander Kanavin "
RECIPE_MAINTAINER:pn-boost-build-native = "Alexander Kanavin
"
RECIPE_MAINTAINER:pn-bootchart2 = "Alexander Kanavin "
diff --git a/meta/recipes-support/bmap-tools/bmap-tools_git.bb
b/meta/recipes-support/bmaptool/bmaptool_git.bb
similarity index 78%
rename from meta/recipes-support/bmap-tools/bmap-tools_git.bb
rename to meta/recipes-support/bmaptool/bmaptool_git.bb
index ffb6ccfe99a5..87328af8c65b 100644
--- a/meta/recipes-support/bmap-tools/bmap-tools_git.bb
+++ b/meta/recipes-support/bmaptool/bmaptool_git.bb
@@ -1,16 +1,16 @@
SUMMARY = "Tools to generate block map (AKA bmap) and flash images using bmap"
-DESCRIPTION = "Bmap-tools - tools to generate block map (AKA bmap) and flash
images using \
-bmap. Bmaptool is a generic tool for creating the block map (bmap) for a file,
\
+DESCRIPTION = "bmaptool - tools to generate block map (AKA bmap) and flash
images using \
+bmap. bmaptool is a generic tool for creating the block map (bmap) for a file,
\
and copying files using the block map. The idea is that large file containing \
unused blocks, like raw system image files, can be copied or flashed a lot \
faster with bmaptool than with traditional tools like "dd" or "cp"."
-HOMEPAGE = "https://github.com/01org/bmap-tools;
+HOMEPAGE = "https://github.com/yoctoproject/bmaptool;
SECTION = "console/utils"
LICENSE = "GPL-2.0-only"
LIC_FILES_CHKSUM = "file://LICENSE;md5=b234ee4d69f5fce4486a80fdaf4a4263"
FILESEXTRAPATHS:prepend := "${THISDIR}/files:"
-SRC_URI = "git://github.com/intel/${BPN};branch=main;protocol=https \
+SRC_URI = "git://github.com/yoctoproject/${BPN};branch=main;protocol=https \
file://0001-BmapCopy.py-fix-error-message.patch \
Re: [OE-core] [PATCH 1/2] kernel-module-dirs.bbclass: Add class
> -Original Message-
> From: Richard Purdie
> Sent: den 4 mars 2024 18:39
> To: Peter Kjellerstedt ;
> openembedded-core@lists.openembedded.org
> Subject: Re: [OE-core] [PATCH 1/2] kernel-module-dirs.bbclass: Add class
>
> On Mon, 2024-03-04 at 17:20 +, Peter Kjellerstedt wrote:
> > > -Original Message-
> > > From: Richard Purdie
> > > Sent: den 4 mars 2024 17:17
> > > To: Peter Kjellerstedt ;
> > > openembedded-core@lists.openembedded.org
> > > Subject: Re: [OE-core] [PATCH 1/2] kernel-module-dirs.bbclass: Add class
> > >
> > > On Mon, 2024-03-04 at 16:57 +0100, Peter Kjellerstedt wrote:
> > > > Split out the two variables modulesloaddir and modprobedir from
> > > > kernel-module-split.bbclass as they can be useful to other recipes than
> > > > kernel module recipes.
> > > >
> > > > Signed-off-by: Peter Kjellerstedt
> > > > ---
> > > > meta/classes-recipe/kernel-module-dirs.bbclass | 8
> > > > 1 file changed, 8 insertions(+)
> > > > create mode 100644 meta/classes-recipe/kernel-module-dirs.bbclass
> > > >
> > > > diff --git a/meta/classes-recipe/kernel-module-dirs.bbclass
> > > > b/meta/classes-recipe/kernel-module-dirs.bbclass
> > > > new file mode 100644
> > > > index 00..eecc36ab52
> > > > --- /dev/null
> > > > +++ b/meta/classes-recipe/kernel-module-dirs.bbclass
> > > > @@ -0,0 +1,8 @@
> > > > +#
> > > > +# Copyright OpenEmbedded Contributors
> > > > +#
> > > > +# SPDX-License-Identifier: MIT
> > > > +#
> > > > +
> > > > +modulesloaddir ??= "${@bb.utils.contains('DISTRO_FEATURES', 'systemd',
> > > > '${nonarch_libdir}', '${sysconfdir}', d)}/modules-load.d"
> > > > +modprobedir ??= "${@bb.utils.contains('DISTRO_FEATURES', 'systemd',
> > > > '${nonarch_base_libdir}', '${sysconfdir}', d)}/modprobe.d"
> > >
> > > Absolutely not. We are not having yet more kernel classes just for two
> > > variables.
> >
> > Ok. I considered adding them to bitbake.conf where all other similar *dir
> > variables are defined, but I opted for a bbclass since I expect it to only
> > be relatively few recipes that need either of them (we currently have ~10
> > non-module recipes that could use them).
>
> bitbake.conf is also an absolute no.
Yes, that was what I expected.
>
> > > There is probably a better way moving some definitions to a new conf
> > > file for the kernel in general.
> >
> > I am not sure what to make of this. What I wanted to achieve was to be
> > able to make the two path variables available to non-module recipes. I am
> > not sure how that matches what you meant with "a new conf file for the
> > kernel". Did you actually mean a .conf file where the variables would be
> > added to the global state, or did you mean a .bbclass/.inc file similar to
> > the one I proposed, but with a more generic name so that it can take other
> > variables than just the two path variables above?
>
> I mean something more like meta/conf/image-uefi.conf but kernel focused.
Hmm, the naming of that file messes with the expectations I've learnt over
the years of working with OE. I've always thought that .conf files are
used for definitions that are part of the global configuration, and .inc
files are used for more local definitions. While I of course know that
there is no technical difference between the two, that kind of semantics
is helpful when looking at an individual file to know the context in which
it is used.
>
> We need to do better about more focused conf/inc files.
In that regard, kernel-module-dirs.bbclass was very focused. ;)
Do you see a difference in, e.g., kernel-module-dirs.bbclass vs.
kernel-module-dirs.inc? I.e., why is an .inc (or .conf) file more suitable
than a .bbclass file in this case?
One reason I can see for why a .bbclass would be preferred, is because it
is only inherited once even if there are multiple inherits. E.g., say I
would take the proposed kernel-module-dirs.bbclass and turn it into a more
generic kernel-vars.inc file. This file would then most likely be needed
by, e.g., kernel.bbclass and module.bbclass. However, based on its current
contents, it would also be needed by kernel-module-split.bbclass that both
of them inherit. But since it is an .inc file, requiring it from both
kernel.bbclass and kernel-module-split.bbclass would result in a lot of
warnings about duplicate inclusion. On the other hand, having
kernel-module-split.bbclass rely on that whatever inherits it has already
required the kernel-vars.inc file seems wrong.
>
> Cheers,
>
> Richard
//Peter
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196616):
https://lists.openembedded.org/g/openembedded-core/message/196616
Mute This Topic: https://lists.openembedded.org/mt/104724883/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] [PATCH 1/2] kernel-module-dirs.bbclass: Add class
On Mon, 2024-03-04 at 17:20 +, Peter Kjellerstedt wrote:
> > -Original Message-
> > From: Richard Purdie
> > Sent: den 4 mars 2024 17:17
> > To: Peter Kjellerstedt ;
> > openembedded-core@lists.openembedded.org
> > Subject: Re: [OE-core] [PATCH 1/2] kernel-module-dirs.bbclass: Add class
> >
> > On Mon, 2024-03-04 at 16:57 +0100, Peter Kjellerstedt wrote:
> > > Split out the two variables modulesloaddir and modprobedir from
> > > kernel-module-split.bbclass as they can be useful to other recipes than
> > > kernel module recipes.
> > >
> > > Signed-off-by: Peter Kjellerstedt
> > > ---
> > > meta/classes-recipe/kernel-module-dirs.bbclass | 8
> > > 1 file changed, 8 insertions(+)
> > > create mode 100644 meta/classes-recipe/kernel-module-dirs.bbclass
> > >
> > > diff --git a/meta/classes-recipe/kernel-module-dirs.bbclass
> > > b/meta/classes-recipe/kernel-module-dirs.bbclass
> > > new file mode 100644
> > > index 00..eecc36ab52
> > > --- /dev/null
> > > +++ b/meta/classes-recipe/kernel-module-dirs.bbclass
> > > @@ -0,0 +1,8 @@
> > > +#
> > > +# Copyright OpenEmbedded Contributors
> > > +#
> > > +# SPDX-License-Identifier: MIT
> > > +#
> > > +
> > > +modulesloaddir ??= "${@bb.utils.contains('DISTRO_FEATURES', 'systemd',
> > > '${nonarch_libdir}', '${sysconfdir}', d)}/modules-load.d"
> > > +modprobedir ??= "${@bb.utils.contains('DISTRO_FEATURES', 'systemd',
> > > '${nonarch_base_libdir}', '${sysconfdir}', d)}/modprobe.d"
> >
> > Absolutely not. We are not having yet more kernel classes just for two
> > variables.
>
> Ok. I considered adding them to bitbake.conf where all other similar *dir
> variables are defined, but I opted for a bbclass since I expect it to only
> be relatively few recipes that need either of them (we currently have ~10
> non-module recipes that could use them).
bitbake.conf is also an absolute no.
> > There is probably a better way moving some definitions to a new conf
> > file for the kernel in general.
>
> I am not sure what to make of this. What I wanted to achieve was to be
> able to make the two path variables available to non-module recipes. I am
> not sure how that matches what you meant with "a new conf file for the
> kernel". Did you actually mean a .conf file where the variables would be
> added to the global state, or did you mean a .bbclass/.inc file similar to
> the one I proposed, but with a more generic name so that it can take other
> variables than just the two path variables above?
I mean something more like meta/conf/image-uefi.conf but kernel focused.
We need to do better about more focused conf/inc files.
Cheers,
Richard
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196615):
https://lists.openembedded.org/g/openembedded-core/message/196615
Mute This Topic: https://lists.openembedded.org/mt/104724883/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] [PATCH 1/2] kernel-module-dirs.bbclass: Add class
> -Original Message-
> From: Richard Purdie
> Sent: den 4 mars 2024 17:17
> To: Peter Kjellerstedt ;
> openembedded-core@lists.openembedded.org
> Subject: Re: [OE-core] [PATCH 1/2] kernel-module-dirs.bbclass: Add class
>
> On Mon, 2024-03-04 at 16:57 +0100, Peter Kjellerstedt wrote:
> > Split out the two variables modulesloaddir and modprobedir from
> > kernel-module-split.bbclass as they can be useful to other recipes than
> > kernel module recipes.
> >
> > Signed-off-by: Peter Kjellerstedt
> > ---
> > meta/classes-recipe/kernel-module-dirs.bbclass | 8
> > 1 file changed, 8 insertions(+)
> > create mode 100644 meta/classes-recipe/kernel-module-dirs.bbclass
> >
> > diff --git a/meta/classes-recipe/kernel-module-dirs.bbclass
> > b/meta/classes-recipe/kernel-module-dirs.bbclass
> > new file mode 100644
> > index 00..eecc36ab52
> > --- /dev/null
> > +++ b/meta/classes-recipe/kernel-module-dirs.bbclass
> > @@ -0,0 +1,8 @@
> > +#
> > +# Copyright OpenEmbedded Contributors
> > +#
> > +# SPDX-License-Identifier: MIT
> > +#
> > +
> > +modulesloaddir ??= "${@bb.utils.contains('DISTRO_FEATURES', 'systemd',
> > '${nonarch_libdir}', '${sysconfdir}', d)}/modules-load.d"
> > +modprobedir ??= "${@bb.utils.contains('DISTRO_FEATURES', 'systemd',
> > '${nonarch_base_libdir}', '${sysconfdir}', d)}/modprobe.d"
>
> Absolutely not. We are not having yet more kernel classes just for two
> variables.
Ok. I considered adding them to bitbake.conf where all other similar *dir
variables are defined, but I opted for a bbclass since I expect it to only
be relatively few recipes that need either of them (we currently have ~10
non-module recipes that could use them).
>
> There is probably a better way moving some definitions to a new conf
> file for the kernel in general.
I am not sure what to make of this. What I wanted to achieve was to be
able to make the two path variables available to non-module recipes. I am
not sure how that matches what you meant with "a new conf file for the
kernel". Did you actually mean a .conf file where the variables would be
added to the global state, or did you mean a .bbclass/.inc file similar to
the one I proposed, but with a more generic name so that it can take other
variables than just the two path variables above?
>
> Cheers,
>
> Richard
//Peter
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196614):
https://lists.openembedded.org/g/openembedded-core/message/196614
Mute This Topic: https://lists.openembedded.org/mt/104724883/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] [PATCH] glibc: fix multilib headers conflict for arm
On Mon, 2024-03-04 at 09:12 +0800, Kai Kang wrote: > From: Kai Kang > > The header files conflic when multilib enabled for arm: > > > Error: Transaction test error: > > file /usr/include/finclude/math-vector-fortran.h conflicts between > > attempted installs of > lib32-libc6-dev-2.39+git0+312e159626-r0.armv7at2hf_neon and > libc6-dev-2.39+git0+312e159626-r0.cortexa72 > > Invoke function oe_multilib_header to resolve it. > > Signed-off-by: Kai Kang > --- > meta/recipes-core/glibc/glibc-package.inc | 2 ++ > 1 file changed, 2 insertions(+) It may fix conflicts but it appears to break the fortran compiler: https://autobuilder.yoctoproject.org/typhoon/#/builders/127/builds/2987/steps/14/logs/stdio I've not specifically bisected it to this but it does seem most likely. Cheers, Richard -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#196613): https://lists.openembedded.org/g/openembedded-core/message/196613 Mute This Topic: https://lists.openembedded.org/mt/104714533/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] [PATCH 1/2] kernel-module-dirs.bbclass: Add class
On Mon, 2024-03-04 at 16:57 +0100, Peter Kjellerstedt wrote:
> Split out the two variables modulesloaddir and modprobedir from
> kernel-module-split.bbclass as they can be useful to other recipes than
> kernel module recipes.
>
> Signed-off-by: Peter Kjellerstedt
> ---
> meta/classes-recipe/kernel-module-dirs.bbclass | 8
> 1 file changed, 8 insertions(+)
> create mode 100644 meta/classes-recipe/kernel-module-dirs.bbclass
>
> diff --git a/meta/classes-recipe/kernel-module-dirs.bbclass
> b/meta/classes-recipe/kernel-module-dirs.bbclass
> new file mode 100644
> index 00..eecc36ab52
> --- /dev/null
> +++ b/meta/classes-recipe/kernel-module-dirs.bbclass
> @@ -0,0 +1,8 @@
> +#
> +# Copyright OpenEmbedded Contributors
> +#
> +# SPDX-License-Identifier: MIT
> +#
> +
> +modulesloaddir ??= "${@bb.utils.contains('DISTRO_FEATURES', 'systemd',
> '${nonarch_libdir}', '${sysconfdir}', d)}/modules-load.d"
> +modprobedir ??= "${@bb.utils.contains('DISTRO_FEATURES', 'systemd',
> '${nonarch_base_libdir}', '${sysconfdir}', d)}/modprobe.d"
Absolutely not. We are not having yet more kernel classes just for two
variables.
There is probably a better way moving some definitions to a new conf
file for the kernel in general.
Cheers,
Richard
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196612):
https://lists.openembedded.org/g/openembedded-core/message/196612
Mute This Topic: https://lists.openembedded.org/mt/104724883/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [PATCH 2/2] kernel-module-split.bbclass: Inherit kernel-module-dirs
The two variables modulesloaddir and modprobedir have been moved to
their own bbclass, kernel-module-dirs.
Signed-off-by: Peter Kjellerstedt
---
meta/classes-recipe/kernel-module-split.bbclass | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/meta/classes-recipe/kernel-module-split.bbclass
b/meta/classes-recipe/kernel-module-split.bbclass
index c1208d55e0..ce8e5e1c09 100644
--- a/meta/classes-recipe/kernel-module-split.bbclass
+++ b/meta/classes-recipe/kernel-module-split.bbclass
@@ -4,6 +4,8 @@
# SPDX-License-Identifier: MIT
#
+inherit kernel-module-dirs
+
pkg_postinst:modules () {
if [ -z "$D" ]; then
depmod -a ${KERNEL_VERSION}
@@ -30,9 +32,6 @@ fi
PACKAGE_WRITE_DEPS += "kmod-native depmodwrapper-cross"
-modulesloaddir ??= "${@bb.utils.contains('DISTRO_FEATURES', 'systemd',
'${nonarch_libdir}', '${sysconfdir}', d)}/modules-load.d"
-modprobedir ??= "${@bb.utils.contains('DISTRO_FEATURES', 'systemd',
'${nonarch_base_libdir}', '${sysconfdir}', d)}/modprobe.d"
-
KERNEL_SPLIT_MODULES ?= "1"
PACKAGESPLITFUNCS =+ "split_kernel_module_packages"
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196610):
https://lists.openembedded.org/g/openembedded-core/message/196610
Mute This Topic: https://lists.openembedded.org/mt/104724882/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [PATCH 1/2] kernel-module-dirs.bbclass: Add class
Split out the two variables modulesloaddir and modprobedir from
kernel-module-split.bbclass as they can be useful to other recipes than
kernel module recipes.
Signed-off-by: Peter Kjellerstedt
---
meta/classes-recipe/kernel-module-dirs.bbclass | 8
1 file changed, 8 insertions(+)
create mode 100644 meta/classes-recipe/kernel-module-dirs.bbclass
diff --git a/meta/classes-recipe/kernel-module-dirs.bbclass
b/meta/classes-recipe/kernel-module-dirs.bbclass
new file mode 100644
index 00..eecc36ab52
--- /dev/null
+++ b/meta/classes-recipe/kernel-module-dirs.bbclass
@@ -0,0 +1,8 @@
+#
+# Copyright OpenEmbedded Contributors
+#
+# SPDX-License-Identifier: MIT
+#
+
+modulesloaddir ??= "${@bb.utils.contains('DISTRO_FEATURES', 'systemd',
'${nonarch_libdir}', '${sysconfdir}', d)}/modules-load.d"
+modprobedir ??= "${@bb.utils.contains('DISTRO_FEATURES', 'systemd',
'${nonarch_base_libdir}', '${sysconfdir}', d)}/modprobe.d"
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196611):
https://lists.openembedded.org/g/openembedded-core/message/196611
Mute This Topic: https://lists.openembedded.org/mt/104724883/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core][kirkstone 10/11] tzdata : Upgrade to 2024a
From: Priyal Doshi
Signed-off-by: Priyal Doshi
Signed-off-by: Alexandre Belloni
(cherry picked from commit 5abbd0abf992ce8d11f3ae31fb1d83d97f5319fa)
Signed-off-by: Shubham Kulkarni
Signed-off-by: Steve Sakoman
---
meta/recipes-extended/timezone/timezone.inc | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/meta/recipes-extended/timezone/timezone.inc
b/meta/recipes-extended/timezone/timezone.inc
index 2774e5e730..4734adcc08 100644
--- a/meta/recipes-extended/timezone/timezone.inc
+++ b/meta/recipes-extended/timezone/timezone.inc
@@ -6,7 +6,7 @@ SECTION = "base"
LICENSE = "PD & BSD-3-Clause"
LIC_FILES_CHKSUM = "file://LICENSE;md5=c679c9d6b02bc2757b3eaf8f53c43fba"
-PV = "2023d"
+PV = "2024a"
SRC_URI ="
http://www.iana.org/time-zones/repository/releases/tzcode${PV}.tar.gz;name=tzcode;subdir=tz
\
http://www.iana.org/time-zones/repository/releases/tzdata${PV}.tar.gz;name=tzdata;subdir=tz
\
@@ -16,5 +16,5 @@ S = "${WORKDIR}/tz"
UPSTREAM_CHECK_URI = "http://www.iana.org/time-zones;
-SRC_URI[tzcode.sha256sum] =
"e9a5f9e118886d2de92b62bb05510a28cc6c058d791c93bd6b84d3292c3c161e"
-SRC_URI[tzdata.sha256sum] =
"dbca21970b0a8b8c0ceceec1d7b91fa903be0f6eca5ae732b5329672232a08f3"
+SRC_URI[tzcode.sha256sum] =
"80072894adff5a458f1d143e16e4ca1d8b2a122c9c5399da482cb68cba6a1ff8"
+SRC_URI[tzdata.sha256sum] =
"0d0434459acbd2059a7a8da1f3304a84a86591f6ed69c6248fffa502b6edffe3"
--
2.34.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196608):
https://lists.openembedded.org/g/openembedded-core/message/196608
Mute This Topic: https://lists.openembedded.org/mt/104724086/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core][kirkstone 09/11] linux-firmware: upgrade 20231030 -> 20231211
From: Alexander Sverdlin
Signed-off-by: Alexander Sverdlin
Signed-off-by: Alexandre Belloni
Signed-off-by: Richard Purdie
(cherry picked from commit 0caafdbbf4e7dc84b919afe14f7cb8c46a9e4ac2)
Signed-off-by: Steve Sakoman
---
...nux-firmware_20231030.bb => linux-firmware_20231211.bb} | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
rename meta/recipes-kernel/linux-firmware/{linux-firmware_20231030.bb =>
linux-firmware_20231211.bb} (99%)
diff --git a/meta/recipes-kernel/linux-firmware/linux-firmware_20231030.bb
b/meta/recipes-kernel/linux-firmware/linux-firmware_20231211.bb
similarity index 99%
rename from meta/recipes-kernel/linux-firmware/linux-firmware_20231030.bb
rename to meta/recipes-kernel/linux-firmware/linux-firmware_20231211.bb
index a42e5ed825..48e83cb34b 100644
--- a/meta/recipes-kernel/linux-firmware/linux-firmware_20231030.bb
+++ b/meta/recipes-kernel/linux-firmware/linux-firmware_20231211.bb
@@ -147,7 +147,7 @@ LIC_FILES_CHKSUM =
"file://LICENCE.Abilis;md5=b5ee3f410780e56711ad48eadc22b8bc \
"
# WHENCE checksum is defined separately to ease overriding it if
# class-devupstream is selected.
-WHENCE_CHKSUM = "ceb5248746d24d165b603e71b288cf75"
+WHENCE_CHKSUM = "3113c4ea08e5171555f3bf49eceb5b07"
# These are not common licenses, set NO_GENERIC_LICENSE for them
# so that the license files will be copied from fetched source
@@ -231,7 +231,7 @@ SRC_URI:class-devupstream =
"git://git.kernel.org/pub/scm/linux/kernel/git/firmw
# Pin this to the 20220509 release, override this in local.conf
SRCREV:class-devupstream ?= "b19cbdca78ab2adfd210c91be15a22568e8b8cae"
-SRC_URI[sha256sum] =
"c98d200fc4a3120de1a594713ce34e135819dff23e883a4ed387863ba25679c7"
+SRC_URI[sha256sum] =
"96af7e4b5eabd37869cdb3dcbb7ab36911106d39b76e799fa1caab16a9dbe8bb"
inherit allarch
@@ -242,7 +242,8 @@ do_compile() {
}
do_install() {
-oe_runmake 'DESTDIR=${D}'
'FIRMWAREDIR=${nonarch_base_libdir}/firmware' install
+# install-nodedup avoids rdfind dependency
+oe_runmake 'DESTDIR=${D}'
'FIRMWAREDIR=${nonarch_base_libdir}/firmware' install-nodedup
cp GPL-2 LICEN[CS]E.* WHENCE ${D}${nonarch_base_libdir}/firmware/
}
--
2.34.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196607):
https://lists.openembedded.org/g/openembedded-core/message/196607
Mute This Topic: https://lists.openembedded.org/mt/104724083/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core][kirkstone 08/11] bind: Upgrade 9.18.19 -> 9.18.24
From: Soumya Sambu
Includes security fixes for - CVE-2023-4408, CVE-2023-5517,
CVE-2023-5679, CVE-2023-50868 and CVE-2023-50387
Changelog:
=
https://gitlab.isc.org/isc-projects/bind9/-/blob/v9.18.24/CHANGES
Signed-off-by: Soumya Sambu
Signed-off-by: Steve Sakoman
---
.../bind/{bind_9.18.19.bb => bind_9.18.24.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-connectivity/bind/{bind_9.18.19.bb => bind_9.18.24.bb}
(97%)
diff --git a/meta/recipes-connectivity/bind/bind_9.18.19.bb
b/meta/recipes-connectivity/bind/bind_9.18.24.bb
similarity index 97%
rename from meta/recipes-connectivity/bind/bind_9.18.19.bb
rename to meta/recipes-connectivity/bind/bind_9.18.24.bb
index a829cc566d..fbbebe89ad 100644
--- a/meta/recipes-connectivity/bind/bind_9.18.19.bb
+++ b/meta/recipes-connectivity/bind/bind_9.18.24.bb
@@ -20,7 +20,7 @@ SRC_URI =
"https://ftp.isc.org/isc/bind9/${PV}/${BPN}-${PV}.tar.xz \
file://0001-avoid-start-failure-with-bind-user.patch \
"
-SRC_URI[sha256sum] =
"115e09c05439bebade1d272eda08fa88eb3b60129edef690588c87a4d27612cc"
+SRC_URI[sha256sum] =
"709d73023c9115ddad3bab65b6c8c79a590196d0d114f5d0ca2533dbd52ddf66"
UPSTREAM_CHECK_URI = "https://ftp.isc.org/isc/bind9/;
# follow the ESV versions divisible by 2
--
2.34.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196606):
https://lists.openembedded.org/g/openembedded-core/message/196606
Mute This Topic: https://lists.openembedded.org/mt/104724082/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core][kirkstone 11/11] kernel.bbclass: Set pkg-config variables for building modules
From: Munehisa Kamata
[Backport cd2072e5d953 from the master without HOSTPKG_CONFIG setting]
The pkg-config workaround has been applied for kernel image building, but
not for module building. So pkg-config variables are different between
do_compile and do_compile_kernelmodules tasks. It may unnecessary trigger
rebuilding of a few host tools at the later task.
Especially when CONFIG_DEBUG_INFO_BTF is enabled in the kernel, it may even
trigger rebuilding vmlinux at do_compile_kernelmodules due to the rebuilt
host tools such as certs/extract-cert or objtool (on x86). This eventually
creates an inconsistent set of kernel binaries.
Here is the repro steps:
- Check out nanbield on x86
- The unexpected rebuild happens on kirkstone or possibly earlier
- Ensure that pahole is available (e.g. via meta-oe)
- Set KERNEL_DEBUG to "True" to properly set up PAHOLE
e.g.
$ export KERNEL_DEBUG="True"
$ export BB_ENV_PASSTHROUGH_ADDITIONS="${BB_ENV_PASSTHROUGH_ADDITIONS}
KERNEL_DEBUG"
- Enable CONFIG_DEBUG_INFO_BTF=y
e.g.
$ bitbake -c menuconfig virtual/kernel
-> Kernel hacking
-> Compile-time checks and compiler options
-> Generate BTF typeinfo
- Build the kernel
e.g.
$ bitbake virtual/kernel
The BTF information in the resulting bzImage and kernel modules are
inconsistent, because the module's BTF information is generated using the
"second" vmlinux that doesn't have the identical BTF to the "first" vmlinux.
These modules can't be loaded at runtime due to the BTF mismatch.
This also leads to a build-id mismatch between the installed bzImage and
vmlinux since the bzImage is created from the first vmlinux, but the
installed vmlinux is the second one.
$ eu-readelf -n
tmp/work/qemux86_64-poky-linux/linux-yocto/6.5.13+git/image/boot/{bzImage*,vmlinux*}
| grep "Build ID"
Build ID: 4a0d62ee7fef0244950f0f604253729875bea493
Build ID: fb99b3d91399dbe42bf67ddee59e0f5a0c7f74d9
To avoid the unexpected rebuilding that results in such inconsistency, set
the same pkg-config variables when building kernel and modules. For kernel
5.19 and above, simply set the HOSTPKG_CONFIG in the make command line.
Signed-off-by: Munehisa Kamata
Signed-off-by: Richard Purdie
Signed-off-by: Steve Sakoman
---
meta/classes/kernel.bbclass | 7 +++
1 file changed, 7 insertions(+)
diff --git a/meta/classes/kernel.bbclass b/meta/classes/kernel.bbclass
index 96e41b5192..dbd89057f3 100644
--- a/meta/classes/kernel.bbclass
+++ b/meta/classes/kernel.bbclass
@@ -396,6 +396,13 @@ addtask transform_kernel after do_compile before do_install
do_compile_kernelmodules() {
unset CFLAGS CPPFLAGS CXXFLAGS LDFLAGS MACHINE
+
+ # setup native pkg-config variables (kconfig scripts call pkg-config
directly, cannot generically be overriden to pkg-config-native)
+ export PKG_CONFIG_DIR="${STAGING_DIR_NATIVE}${libdir_native}/pkgconfig"
+ export
PKG_CONFIG_PATH="$PKG_CONFIG_DIR:${STAGING_DATADIR_NATIVE}/pkgconfig"
+ export PKG_CONFIG_LIBDIR="$PKG_CONFIG_DIR"
+ export PKG_CONFIG_SYSROOT_DIR=""
+
if [ "${KERNEL_DEBUG_TIMESTAMPS}" != "1" ]; then
# kernel sources do not use do_unpack, so SOURCE_DATE_EPOCH may
not
# be set
--
2.34.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196609):
https://lists.openembedded.org/g/openembedded-core/message/196609
Mute This Topic: https://lists.openembedded.org/mt/104724088/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core][kirkstone 07/11] cve_check: cleanup logging
From: Ross Burton
Primarily list the number of patches found, useful when debugging.
Also clean up some bad escaping that caused warnings and use
re.IGNORECASE instead of manually doing case-insenstive rang matches.
Signed-off-by: Ross Burton
Signed-off-by: Richard Purdie
(cherry picked from commit 10acc75b7f3387b968bacd51aade6a8dc11a463f)
Signed-off-by: Steve Sakoman
---
meta/lib/oe/cve_check.py | 13 ++---
1 file changed, 6 insertions(+), 7 deletions(-)
diff --git a/meta/lib/oe/cve_check.py b/meta/lib/oe/cve_check.py
index 65b1358ffc..ca2b393116 100644
--- a/meta/lib/oe/cve_check.py
+++ b/meta/lib/oe/cve_check.py
@@ -73,20 +73,19 @@ def get_patched_cves(d):
import re
import oe.patch
-pn = d.getVar("PN")
-cve_match = re.compile("CVE:( CVE\-\d{4}\-\d+)+")
+cve_match = re.compile(r"CVE:( CVE-\d{4}-\d+)+")
# Matches the last "CVE--ID" in the file name, also if written
# in lowercase. Possible to have multiple CVE IDs in a single
# file name, but only the last one will be detected from the file name.
# However, patch files contents addressing multiple CVE IDs are supported
# (cve_match regular expression)
-
-cve_file_name_match = re.compile(".*([Cc][Vv][Ee]\-\d{4}\-\d+)")
+cve_file_name_match = re.compile(r".*(CVE-\d{4}-\d+)", re.IGNORECASE)
patched_cves = set()
-bb.debug(2, "Looking for patches that solves CVEs for %s" % pn)
-for url in oe.patch.src_patches(d):
+patches = oe.patch.src_patches(d)
+bb.debug(2, "Scanning %d patches for CVEs" % len(patches))
+for url in patches:
patch_file = bb.fetch.decodeurl(url)[2]
# Check patch file name for CVE ID
@@ -94,7 +93,7 @@ def get_patched_cves(d):
if fname_match:
cve = fname_match.group(1).upper()
patched_cves.add(cve)
-bb.debug(2, "Found CVE %s from patch file name %s" % (cve,
patch_file))
+bb.debug(2, "Found %s from patch file name %s" % (cve, patch_file))
# Remote patches won't be present and compressed patches won't be
# unpacked, so say we're not scanning them
--
2.34.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196605):
https://lists.openembedded.org/g/openembedded-core/message/196605
Mute This Topic: https://lists.openembedded.org/mt/104724078/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core][kirkstone 06/11] dbus: Add missing CVE_PRODUCT
From: Dhairya Nagodra
- The current recipe only contains one (out of three) valid product
names for dbus package in NVD.
- This could result in reporting of lesser number CVEs than actual.
- Added missing names to get a proper list.
Signed-off-by: Dhairya Nagodra
Signed-off-by: Steve Sakoman
---
meta/recipes-core/dbus/dbus_1.14.8.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-core/dbus/dbus_1.14.8.bb
b/meta/recipes-core/dbus/dbus_1.14.8.bb
index 4da307ecb3..f03e5c2d2e 100644
--- a/meta/recipes-core/dbus/dbus_1.14.8.bb
+++ b/meta/recipes-core/dbus/dbus_1.14.8.bb
@@ -184,4 +184,4 @@ do_install:class-nativesdk() {
}
BBCLASSEXTEND = "native nativesdk"
-CVE_PRODUCT += "d-bus_project:d-bus"
+CVE_PRODUCT += "d-bus_project:d-bus freedesktop:dbus freedesktop:libdbus"
--
2.34.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196604):
https://lists.openembedded.org/g/openembedded-core/message/196604
Mute This Topic: https://lists.openembedded.org/mt/104724076/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core][kirkstone 05/11] qemu: Fix CVE-2023-42467
From: Poonam Jadhav
1. scsi-disk: allow MODE SELECT block descriptor to set the block size
Link:
https://github.com/qemu/qemu/commit/356c4c441ec01910314c5867c680bef80d1dd373
The MODE SELECT command can contain an optional block descriptor that can be
used
to set the device block size. If the block descriptor is present then update the
block size on the SCSI device accordingly.
This allows CDROMs to be used with A/UX which requires a CDROM drive which is
capable of switching from a 2048 byte sector size to a 512 byte sector size.
2. scsi-disk: ensure block size is non-zero and changes limited to bits 8-15
Link:
https://github.com/qemu/qemu/commit/55794c904df723109b228da28b5db778e0df3110
The existing code assumes that the block size can be generated from p[1] << 8
in multiple places which ignores the top and bottom 8 bits. If the block size
is allowed to be set to an arbitrary value then this causes a mismatch
between the value written by the guest in the block descriptor and the value
subsequently read back using READ CAPACITY causing the guest to generate
requests that can crash QEMU.
For now restrict block size changes to bits 8-15 and also ignore requests to
set the block size to 0 which causes the SCSI emulation to crash in at least
one place with a divide by zero error.
3. Disallow block sizes smaller than 512 [CVE-2023-42467]
Link:
https://gitlab.com/qemu-project/qemu/-/commit/7cfcc79b0ab800959716738aff9419f53fc68c9c
We are doing things like
nb_sectors /= (s->qdev.blocksize / BDRV_SECTOR_SIZE);
in the code here (e.g. in scsi_disk_emulate_mode_sense()), so if
the blocksize is smaller than BDRV_SECTOR_SIZE (=512), this crashes
with a division by 0 exception. Thus disallow block sizes of 256
bytes to avoid this situation.
Signed-off-by: Poonam Jadhav
Signed-off-by: Steve Sakoman
---
meta/recipes-devtools/qemu/qemu.inc | 3 +
.../qemu/qemu/CVE-2023-42467.patch| 46 +
...lock-desriptor-to-set-the-block-size.patch | 54 +++
...ero-and-changes-limited-to-bits-8-15.patch | 67 +++
4 files changed, 170 insertions(+)
create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2023-42467.patch
create mode 100644
meta/recipes-devtools/qemu/qemu/scsi-disk-allow-MODE-SELECT-block-desriptor-to-set-the-block-size.patch
create mode 100644
meta/recipes-devtools/qemu/qemu/scsi-disk-ensure-block-size-is-non-zero-and-changes-limited-to-bits-8-15.patch
diff --git a/meta/recipes-devtools/qemu/qemu.inc
b/meta/recipes-devtools/qemu/qemu.inc
index d3e6ced988..ad6b310137 100644
--- a/meta/recipes-devtools/qemu/qemu.inc
+++ b/meta/recipes-devtools/qemu/qemu.inc
@@ -105,6 +105,9 @@ SRC_URI = "https://download.qemu.org/${BPN}-${PV}.tar.xz \
file://CVE-2023-5088.patch \
file://CVE-2024-24474.patch \
file://CVE-2023-6693.patch \
+
file://scsi-disk-allow-MODE-SELECT-block-desriptor-to-set-the-block-size.patch \
+
file://scsi-disk-ensure-block-size-is-non-zero-and-changes-limited-to-bits-8-15.patch
\
+ file://CVE-2023-42467.patch \
"
UPSTREAM_CHECK_REGEX = "qemu-(?P\d+(\.\d+)+)\.tar"
diff --git a/meta/recipes-devtools/qemu/qemu/CVE-2023-42467.patch
b/meta/recipes-devtools/qemu/qemu/CVE-2023-42467.patch
new file mode 100644
index 00..d53683faa7
--- /dev/null
+++ b/meta/recipes-devtools/qemu/qemu/CVE-2023-42467.patch
@@ -0,0 +1,46 @@
+From 7cfcc79b0ab800959716738aff9419f53fc68c9c Mon Sep 17 00:00:00 2001
+From: Thomas Huth
+Date: Mon, 25 Sep 2023 11:18:54 +0200
+Subject: [PATCH] hw/scsi/scsi-disk: Disallow block sizes smaller than 512
+ [CVE-2023-42467]
+
+We are doing things like
+
+nb_sectors /= (s->qdev.blocksize / BDRV_SECTOR_SIZE);
+
+in the code here (e.g. in scsi_disk_emulate_mode_sense()), so if
+the blocksize is smaller than BDRV_SECTOR_SIZE (=512), this crashes
+with a division by 0 exception. Thus disallow block sizes of 256
+bytes to avoid this situation.
+
+Resolves: https://gitlab.com/qemu-project/qemu/-/issues/1813
+CVE: 2023-42467
+Signed-off-by: Thomas Huth
+Message-ID: <20230925091854.49198-1-th...@redhat.com>
+Signed-off-by: Paolo Bonzini
+
+CVE: CVE-2023-42467
+Upstream-Status: Backport
[https://gitlab.com/qemu-project/qemu/-/commit/7cfcc79b0ab800959716738aff9419f53fc68c9c]
+Signed-off-by: Poonam Jadhav
+---
+ hw/scsi/scsi-disk.c | 5 +++--
+ 1 file changed, 3 insertions(+), 2 deletions(-)
+
+diff --git a/hw/scsi/scsi-disk.c b/hw/scsi/scsi-disk.c
+index e0d79c7966c..477ee2bcd47 100644
+--- a/hw/scsi/scsi-disk.c
b/hw/scsi/scsi-disk.c
+@@ -1628,9 +1628,10 @@ static void scsi_disk_emulate_mode_select(SCSIDiskReq
*r, uint8_t *inbuf)
+ * Since the existing code only checks/updates bits 8-15 of the block
+ * size, restrict ourselves to the same requirement for now to ensure
+ * that a block size set by a block descriptor and then read back by
+- * a subsequent SCSI command will be the same
++
[OE-core][kirkstone 04/11] qemu: Backport fix CVE-2023-6693
From: Vivek Kumbhar
Upstream-Status: Backport
[https://gitlab.com/qemu-project/qemu/-/commit/2220e8189fb94068dbad333228659fbac819abb0]
Signed-off-by: Vivek Kumbhar
Signed-off-by: Steve Sakoman
---
meta/recipes-devtools/qemu/qemu.inc | 1 +
.../qemu/qemu/CVE-2023-6693.patch | 74 +++
2 files changed, 75 insertions(+)
create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2023-6693.patch
diff --git a/meta/recipes-devtools/qemu/qemu.inc
b/meta/recipes-devtools/qemu/qemu.inc
index 18752af274..d3e6ced988 100644
--- a/meta/recipes-devtools/qemu/qemu.inc
+++ b/meta/recipes-devtools/qemu/qemu.inc
@@ -104,6 +104,7 @@ SRC_URI = "https://download.qemu.org/${BPN}-${PV}.tar.xz \
file://CVE-2023-1544.patch \
file://CVE-2023-5088.patch \
file://CVE-2024-24474.patch \
+ file://CVE-2023-6693.patch \
"
UPSTREAM_CHECK_REGEX = "qemu-(?P\d+(\.\d+)+)\.tar"
diff --git a/meta/recipes-devtools/qemu/qemu/CVE-2023-6693.patch
b/meta/recipes-devtools/qemu/qemu/CVE-2023-6693.patch
new file mode 100644
index 00..b91f2e6902
--- /dev/null
+++ b/meta/recipes-devtools/qemu/qemu/CVE-2023-6693.patch
@@ -0,0 +1,74 @@
+From 2220e8189fb94068dbad333228659fbac819abb0 Mon Sep 17 00:00:00 2001
+From: Jason Wang
+Date: Tue, 2 Jan 2024 11:29:01 +0800
+Subject: [PATCH] virtio-net: correctly copy vnet header when flushing TX
+
+When HASH_REPORT is negotiated, the guest_hdr_len might be larger than
+the size of the mergeable rx buffer header. Using
+virtio_net_hdr_mrg_rxbuf during the header swap might lead a stack
+overflow in this case. Fixing this by using virtio_net_hdr_v1_hash
+instead.
+
+Reported-by: Xiao Lei
+Cc: Yuri Benditovich
+Cc: qemu-sta...@nongnu.org
+Cc: Mauro Matteo Cascella
+Fixes: CVE-2023-6693
+Fixes: e22f0603fb2f ("virtio-net: reference implementation of hash report")
+Reviewed-by: Michael Tokarev
+Signed-off-by: Jason Wang
+
+Upstream-Status: Backport
[https://gitlab.com/qemu-project/qemu/-/commit/2220e8189fb94068dbad333228659fbac819abb0]
+CVE: CVE-2023-6693
+Signed-off-by: Vivek Kumbhar
+---
+ hw/net/virtio-net.c | 13 +
+ 1 file changed, 9 insertions(+), 4 deletions(-)
+
+diff --git a/hw/net/virtio-net.c b/hw/net/virtio-net.c
+index e1f474883..42e66697f 100644
+--- a/hw/net/virtio-net.c
b/hw/net/virtio-net.c
+@@ -600,6 +600,11 @@ static void virtio_net_set_mrg_rx_bufs(VirtIONet *n, int
mergeable_rx_bufs,
+
+ n->mergeable_rx_bufs = mergeable_rx_bufs;
+
++/*
++ * Note: when extending the vnet header, please make sure to
++ * change the vnet header copying logic in virtio_net_flush_tx()
++ * as well.
++ */
+ if (version_1) {
+ n->guest_hdr_len = hash_report ?
+ sizeof(struct virtio_net_hdr_v1_hash) :
+@@ -2520,7 +2525,7 @@ static int32_t virtio_net_flush_tx(VirtIONetQueue *q)
+ ssize_t ret;
+ unsigned int out_num;
+ struct iovec sg[VIRTQUEUE_MAX_SIZE], sg2[VIRTQUEUE_MAX_SIZE + 1],
*out_sg;
+-struct virtio_net_hdr_mrg_rxbuf mhdr;
++struct virtio_net_hdr_v1_hash vhdr;
+
+ elem = virtqueue_pop(q->tx_vq, sizeof(VirtQueueElement));
+ if (!elem) {
+@@ -2537,7 +2542,7 @@ static int32_t virtio_net_flush_tx(VirtIONetQueue *q)
+ }
+
+ if (n->has_vnet_hdr) {
+-if (iov_to_buf(out_sg, out_num, 0, , n->guest_hdr_len) <
++if (iov_to_buf(out_sg, out_num, 0, , n->guest_hdr_len) <
+ n->guest_hdr_len) {
+ virtio_error(vdev, "virtio-net header incorrect");
+ virtqueue_detach_element(q->tx_vq, elem, 0);
+@@ -2545,8 +2550,8 @@ static int32_t virtio_net_flush_tx(VirtIONetQueue *q)
+ return -EINVAL;
+ }
+ if (n->needs_vnet_hdr_swap) {
+-virtio_net_hdr_swap(vdev, (void *) );
+-sg2[0].iov_base =
++virtio_net_hdr_swap(vdev, (void *) );
++sg2[0].iov_base =
+ sg2[0].iov_len = n->guest_hdr_len;
+ out_num = iov_copy([1], ARRAY_SIZE(sg2) - 1,
+out_sg, out_num,
+--
+2.34.1
--
2.34.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196602):
https://lists.openembedded.org/g/openembedded-core/message/196602
Mute This Topic: https://lists.openembedded.org/mt/104724071/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core][kirkstone 02/11] glibc: ignore CVE-2023-0687
From: Peter Marko This CVE was backported to glibc 2.35 branch 9 months ago. NVD recently updated CPE and it appeared in kirkstone cve reports. https://sourceware.org/git/?p=glibc.git;a=log;h=refs/heads/release/2.35/master gmon: Fix allocated buffer overflow (bug 29444) https://sourceware.org/git/?p=glibc.git;a=commit;h=f2820e478c68a73a38f81512cc38b220212a Signed-off-by: Peter Marko Signed-off-by: Steve Sakoman --- meta/recipes-core/glibc/glibc_2.35.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/recipes-core/glibc/glibc_2.35.bb b/meta/recipes-core/glibc/glibc_2.35.bb index 21cd99dfdd..3ec6610d01 100644 --- a/meta/recipes-core/glibc/glibc_2.35.bb +++ b/meta/recipes-core/glibc/glibc_2.35.bb @@ -24,7 +24,7 @@ CVE_CHECK_IGNORE += "CVE-2019-1010025" CVE_CHECK_IGNORE += "CVE-2023-4527" # To avoid these in cve-check reports since the recipe version did not change -CVE_CHECK_IGNORE += "CVE-2023-4813 CVE-2023-4806 CVE-2023-4911 CVE-2023-5156" +CVE_CHECK_IGNORE += "CVE-2023-0687 CVE-2023-4813 CVE-2023-4806 CVE-2023-4911 CVE-2023-5156" DEPENDS += "gperf-native bison-native" -- 2.34.1 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#196600): https://lists.openembedded.org/g/openembedded-core/message/196600 Mute This Topic: https://lists.openembedded.org/mt/104724069/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[OE-core][kirkstone 03/11] qemu: Fix for CVE-2024-24474
From: Vijay Anusuri
Upstream-Status: Backport
[https://github.com/qemu/qemu/commit/77668e4b9bca03a856c27ba899a2513ddf52bb52]
Signed-off-by: Vijay Anusuri
Signed-off-by: Steve Sakoman
---
meta/recipes-devtools/qemu/qemu.inc | 1 +
.../qemu/qemu/CVE-2024-24474.patch| 44 +++
2 files changed, 45 insertions(+)
create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2024-24474.patch
diff --git a/meta/recipes-devtools/qemu/qemu.inc
b/meta/recipes-devtools/qemu/qemu.inc
index c5fb9b1eab..18752af274 100644
--- a/meta/recipes-devtools/qemu/qemu.inc
+++ b/meta/recipes-devtools/qemu/qemu.inc
@@ -103,6 +103,7 @@ SRC_URI = "https://download.qemu.org/${BPN}-${PV}.tar.xz \
file://CVE-2021-3638.patch \
file://CVE-2023-1544.patch \
file://CVE-2023-5088.patch \
+ file://CVE-2024-24474.patch \
"
UPSTREAM_CHECK_REGEX = "qemu-(?P\d+(\.\d+)+)\.tar"
diff --git a/meta/recipes-devtools/qemu/qemu/CVE-2024-24474.patch
b/meta/recipes-devtools/qemu/qemu/CVE-2024-24474.patch
new file mode 100644
index 00..e890fe56cf
--- /dev/null
+++ b/meta/recipes-devtools/qemu/qemu/CVE-2024-24474.patch
@@ -0,0 +1,44 @@
+From 77668e4b9bca03a856c27ba899a2513ddf52bb52 Mon Sep 17 00:00:00 2001
+From: Mark Cave-Ayland
+Date: Wed, 13 Sep 2023 21:44:09 +0100
+Subject: [PATCH] esp: restrict non-DMA transfer length to that of available
+ data
+
+In the case where a SCSI layer transfer is incorrectly terminated, it is
+possible for a TI command to cause a SCSI buffer overflow due to the
+expected transfer data length being less than the available data in the
+FIFO. When this occurs the unsigned async_len variable underflows and
+becomes a large offset which writes past the end of the allocated SCSI
+buffer.
+
+Restrict the non-DMA transfer length to be the smallest of the expected
+transfer length and the available FIFO data to ensure that it is no longer
+possible for the SCSI buffer overflow to occur.
+
+Signed-off-by: Mark Cave-Ayland
+Resolves: https://gitlab.com/qemu-project/qemu/-/issues/1810
+Reviewed-by: Thomas Huth
+Message-ID: <20230913204410.65650-3-mark.cave-ayl...@ilande.co.uk>
+Signed-off-by: Paolo Bonzini
+
+Upstream-Status: Backport
[https://github.com/qemu/qemu/commit/77668e4b9bca03a856c27ba899a2513ddf52bb52]
+CVE: CVE-2024-24474
+Signed-off-by: Vijay Anusuri
+---
+ hw/scsi/esp.c | 3 ++-
+ 1 file changed, 2 insertions(+), 1 deletion(-)
+
+diff --git a/hw/scsi/esp.c b/hw/scsi/esp.c
+index 4218a6a96054..9b11d8c5738a 100644
+--- a/hw/scsi/esp.c
b/hw/scsi/esp.c
+@@ -759,7 +759,8 @@ static void esp_do_nodma(ESPState *s)
+ }
+
+ if (to_device) {
+-len = MIN(fifo8_num_used(>fifo), ESP_FIFO_SZ);
++len = MIN(s->async_len, ESP_FIFO_SZ);
++len = MIN(len, fifo8_num_used(>fifo));
+ esp_fifo_pop_buf(>fifo, s->async_buf, len);
+ s->async_buf += len;
+ s->async_len -= len;
--
2.34.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196601):
https://lists.openembedded.org/g/openembedded-core/message/196601
Mute This Topic: https://lists.openembedded.org/mt/104724070/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core][kirkstone 01/11] less: Fix for CVE-2022-48624
From: Vijay Anusuri
Upstream-Status: Backport
[https://github.com/gwsw/less/commit/c6ac6de49698be84d264a0c4c0c40bb870b10144]
Signed-off-by: Vijay Anusuri
Signed-off-by: Steve Sakoman
---
.../less/less/CVE-2022-48624.patch| 41 +++
meta/recipes-extended/less/less_600.bb| 1 +
2 files changed, 42 insertions(+)
create mode 100644 meta/recipes-extended/less/less/CVE-2022-48624.patch
diff --git a/meta/recipes-extended/less/less/CVE-2022-48624.patch
b/meta/recipes-extended/less/less/CVE-2022-48624.patch
new file mode 100644
index 00..409730bd4f
--- /dev/null
+++ b/meta/recipes-extended/less/less/CVE-2022-48624.patch
@@ -0,0 +1,41 @@
+From c6ac6de49698be84d264a0c4c0c40bb870b10144 Mon Sep 17 00:00:00 2001
+From: Mark Nudelman
+Date: Sat, 25 Jun 2022 11:54:43 -0700
+Subject: [PATCH] Shell-quote filenames when invoking LESSCLOSE.
+
+Upstream-Status: Backport
[https://github.com/gwsw/less/commit/c6ac6de49698be84d264a0c4c0c40bb870b10144]
+CVE: CVE-2022-48624
+Signed-off-by: Vijay Anusuri
+---
+ filename.c | 10 --
+ 1 file changed, 8 insertions(+), 2 deletions(-)
+
+diff --git a/filename.c b/filename.c
+index 5824e385..dff20c08 100644
+--- a/filename.c
b/filename.c
+@@ -972,6 +972,8 @@ close_altfile(altfilename, filename)
+ {
+ #if HAVE_POPEN
+ char *lessclose;
++ char *qfilename;
++ char *qaltfilename;
+ FILE *fd;
+ char *cmd;
+ int len;
+@@ -986,9 +988,13 @@ close_altfile(altfilename, filename)
+ error("LESSCLOSE ignored; must contain no more than 2 %%s",
NULL_PARG);
+ return;
+ }
+- len = (int) (strlen(lessclose) + strlen(filename) + strlen(altfilename)
+ 2);
++ qfilename = shell_quote(filename);
++ qaltfilename = shell_quote(altfilename);
++ len = (int) (strlen(lessclose) + strlen(qfilename) +
strlen(qaltfilename) + 2);
+ cmd = (char *) ecalloc(len, sizeof(char));
+- SNPRINTF2(cmd, len, lessclose, filename, altfilename);
++ SNPRINTF2(cmd, len, lessclose, qfilename, qaltfilename);
++ free(qaltfilename);
++ free(qfilename);
+ fd = shellcmd(cmd);
+ free(cmd);
+ if (fd != NULL)
diff --git a/meta/recipes-extended/less/less_600.bb
b/meta/recipes-extended/less/less_600.bb
index f68281ac93..f88127a9e3 100644
--- a/meta/recipes-extended/less/less_600.bb
+++ b/meta/recipes-extended/less/less_600.bb
@@ -27,6 +27,7 @@ DEPENDS = "ncurses"
SRC_URI = "http://www.greenwoodsoftware.com/${BPN}/${BPN}-${PV}.tar.gz \
file://CVE-2022-46663.patch \
+ file://CVE-2022-48624.patch \
"
SRC_URI[sha256sum] =
"6633d6aa2b3cc717afb2c205778c7c42c4620f63b1d682f3d12c98af0be74d20"
--
2.34.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196599):
https://lists.openembedded.org/g/openembedded-core/message/196599
Mute This Topic: https://lists.openembedded.org/mt/104724067/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core][kirkstone 00/11] Patch review
Please review this set of changes for kirkstone and have comments back by
end of day Wednesday, March 6
Passed a-full on autobuilder:
https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/6640
The following changes since commit cca0971a7d92d823cc0c2b16cf14a7b2ed8ecb61:
kernel: make LOCALVERSION consistent between recipes (2024-02-27 03:51:58
-1000)
are available in the Git repository at:
https://git.openembedded.org/openembedded-core-contrib stable/kirkstone-nut
https://git.openembedded.org/openembedded-core-contrib/log/?h=stable/kirkstone-nut
Alexander Sverdlin (1):
linux-firmware: upgrade 20231030 -> 20231211
Dhairya Nagodra (1):
dbus: Add missing CVE_PRODUCT
Munehisa Kamata (1):
kernel.bbclass: Set pkg-config variables for building modules
Peter Marko (1):
glibc: ignore CVE-2023-0687
Poonam Jadhav (1):
qemu: Fix CVE-2023-42467
Priyal Doshi (1):
tzdata : Upgrade to 2024a
Ross Burton (1):
cve_check: cleanup logging
Soumya Sambu (1):
bind: Upgrade 9.18.19 -> 9.18.24
Vijay Anusuri (2):
less: Fix for CVE-2022-48624
qemu: Fix for CVE-2024-24474
Vivek Kumbhar (1):
qemu: Backport fix CVE-2023-6693
meta/classes/kernel.bbclass | 7 ++
meta/lib/oe/cve_check.py | 13 ++--
.../bind/{bind_9.18.19.bb => bind_9.18.24.bb} | 2 +-
meta/recipes-core/dbus/dbus_1.14.8.bb | 2 +-
meta/recipes-core/glibc/glibc_2.35.bb | 2 +-
meta/recipes-devtools/qemu/qemu.inc | 5 ++
.../qemu/qemu/CVE-2023-42467.patch| 46
.../qemu/qemu/CVE-2023-6693.patch | 74 +++
.../qemu/qemu/CVE-2024-24474.patch| 44 +++
...lock-desriptor-to-set-the-block-size.patch | 54 ++
...ero-and-changes-limited-to-bits-8-15.patch | 67 +
.../less/less/CVE-2022-48624.patch| 41 ++
meta/recipes-extended/less/less_600.bb| 1 +
meta/recipes-extended/timezone/timezone.inc | 6 +-
...20231030.bb => linux-firmware_20231211.bb} | 7 +-
15 files changed, 355 insertions(+), 16 deletions(-)
rename meta/recipes-connectivity/bind/{bind_9.18.19.bb => bind_9.18.24.bb}
(97%)
create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2023-42467.patch
create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2023-6693.patch
create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2024-24474.patch
create mode 100644
meta/recipes-devtools/qemu/qemu/scsi-disk-allow-MODE-SELECT-block-desriptor-to-set-the-block-size.patch
create mode 100644
meta/recipes-devtools/qemu/qemu/scsi-disk-ensure-block-size-is-non-zero-and-changes-limited-to-bits-8-15.patch
create mode 100644 meta/recipes-extended/less/less/CVE-2022-48624.patch
rename meta/recipes-kernel/linux-firmware/{linux-firmware_20231030.bb =>
linux-firmware_20231211.bb} (99%)
--
2.34.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196598):
https://lists.openembedded.org/g/openembedded-core/message/196598
Mute This Topic: https://lists.openembedded.org/mt/104724066/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] [yocto-security] OE-core CVE metrics for master on Sun 03 Mar 2024 01:00:01 AM HST
On 3 Mar 2024, at 13:18, Peter Marko via lists.yoctoproject.org wrote: > > I already mentioned this last week. > https://lists.openembedded.org/g/openembedded-core/message/196199 > > I think that partial NVD DB update is not working properly as things which > were corrected by NVD are still showing up in patchmetrics but not in email > reports. I need to file a bug for this issue. If CPEs are updated then they only reach an existing database if the CVE itself is updated, as a CPE change alone isn’t enough to appear in the query we use. I’ve a branch that adds this second query to the fetcher but it is incredibly slow (and you thought the current fetcher was slow?) and still isn’t 100% accurate. NIST are aware of “limitations” with the new API… For accurate runs I do sadly recommend forcing a full fetch of the CVE data. Ross -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#196597): https://lists.openembedded.org/g/openembedded-core/message/196597 Mute This Topic: https://lists.openembedded.org/mt/104701002/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core][kirkstone][PATCH] libseccomp: Add back in PTESTS_SLOW list
This needs to be tested on master, and submitted for master first. Alex On Mon, 4 Mar 2024 at 13:03, Sourav Kumar Pramanik wrote: > > Enable libseccomp-ptest in PTESTS_SLOW as > all tests are passing now. > > Signed-off-by: Sourav Pramanik > --- > meta/conf/distro/include/ptest-packagelists.inc | 3 +-- > 1 file changed, 1 insertion(+), 2 deletions(-) > > diff --git a/meta/conf/distro/include/ptest-packagelists.inc > b/meta/conf/distro/include/ptest-packagelists.inc > index 5c6a30635f..f39b048b21 100644 > --- a/meta/conf/distro/include/ptest-packagelists.inc > +++ b/meta/conf/distro/include/ptest-packagelists.inc > @@ -88,6 +88,7 @@ PTESTS_SLOW = "\ > glib-2.0-ptest \ > gstreamer1.0-ptest \ > libevent-ptest \ > +libseccomp-ptest \ > lttng-tools-ptest \ > openssh-ptest \ > openssl-ptest \ > @@ -112,7 +113,6 @@ PTESTS_PROBLEMS:append:riscv64 = " valgrind-ptest" > #libinput-ptest \ # Tests need an unloaded system to be reliable > #libpam-ptest \ # Needs pam DISTRO_FEATURE > #numactl-ptest \ # qemu not (yet) configured for numa; all tests are > skipped > -#libseccomp-ptest \ # tests failed: 38; add to slow tests once addressed > #python3-numpy-ptest \ # requires even more RAM and (possibly) disk > space; multiple failures > > PTESTS_PROBLEMS = "\ > @@ -124,7 +124,6 @@ PTESTS_PROBLEMS = "\ > mdadm-ptest \ > libinput-ptest \ > libpam-ptest \ > -libseccomp-ptest \ > numactl-ptest \ > python3-numpy-ptest \ > " > -- > 2.25.1 > > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#196596): https://lists.openembedded.org/g/openembedded-core/message/196596 Mute This Topic: https://lists.openembedded.org/mt/104720371/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[OE-core][kirkstone][PATCH] libseccomp: Add back in PTESTS_SLOW list
Enable libseccomp-ptest in PTESTS_SLOW as all tests are passing now. Signed-off-by: Sourav Pramanik --- meta/conf/distro/include/ptest-packagelists.inc | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/meta/conf/distro/include/ptest-packagelists.inc b/meta/conf/distro/include/ptest-packagelists.inc index 5c6a30635f..f39b048b21 100644 --- a/meta/conf/distro/include/ptest-packagelists.inc +++ b/meta/conf/distro/include/ptest-packagelists.inc @@ -88,6 +88,7 @@ PTESTS_SLOW = "\ glib-2.0-ptest \ gstreamer1.0-ptest \ libevent-ptest \ +libseccomp-ptest \ lttng-tools-ptest \ openssh-ptest \ openssl-ptest \ @@ -112,7 +113,6 @@ PTESTS_PROBLEMS:append:riscv64 = " valgrind-ptest" #libinput-ptest \ # Tests need an unloaded system to be reliable #libpam-ptest \ # Needs pam DISTRO_FEATURE #numactl-ptest \ # qemu not (yet) configured for numa; all tests are skipped -#libseccomp-ptest \ # tests failed: 38; add to slow tests once addressed #python3-numpy-ptest \ # requires even more RAM and (possibly) disk space; multiple failures PTESTS_PROBLEMS = "\ @@ -124,7 +124,6 @@ PTESTS_PROBLEMS = "\ mdadm-ptest \ libinput-ptest \ libpam-ptest \ -libseccomp-ptest \ numactl-ptest \ python3-numpy-ptest \ " -- 2.25.1 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#196595): https://lists.openembedded.org/g/openembedded-core/message/196595 Mute This Topic: https://lists.openembedded.org/mt/104720371/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [PATCH] python3-cryptography_42.0.5.bb: delete redundant ptest packaging
Since FILES:${PN}-ptest is already defined to include the contents of
${PTEST_PATH}, adding such an entry to the package is superfluous.
Signed-off-by: Robert P. J. Day
---
diff --git a/meta/recipes-devtools/python/python3-cryptography_42.0.5.bb
b/meta/recipes-devtools/python/python3-cryptography_42.0.5.bb
index 2bcb5717e4..732f925d92 100644
--- a/meta/recipes-devtools/python/python3-cryptography_42.0.5.bb
+++ b/meta/recipes-devtools/python/python3-cryptography_42.0.5.bb
@@ -60,9 +60,6 @@ do_install_ptest() {
cp -r ${S}/pyproject.toml ${D}${PTEST_PATH}/
}
-FILES:${PN}-ptest += " \
-${PTEST_PATH}/check-memfree.py \
-"
FILES:${PN}-dbg += " \
${PYTHON_SITEPACKAGES_DIR}/${SRCNAME}/hazmat/bindings/.debug \
"
--
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196594):
https://lists.openembedded.org/g/openembedded-core/message/196594
Mute This Topic: https://lists.openembedded.org/mt/104719742/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] [PATCH v4 0/3] pkg-database and systemd-sysext image
Hoi Alex, thanks for the heads up - i'll patiently wait then :-) gruß Johannes From: Alexander Kanavin Sent: Monday, March 4, 2024 10:25 To: SCHNEIDER Johannes Cc: openembedded-core@lists.openembedded.org; richard.pur...@linuxfoundation.org Subject: Re: [OE-core] [PATCH v4 0/3] pkg-database and systemd-sysext image [You don't often get email from alex.kana...@gmail.com. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ] This email is not from Hexagon’s Office 365 instance. Please be careful while clicking links, opening attachments, or replying to this email. There is a feature freeze now, so this might have to wait for after that. Alex On Mon, 4 Mar 2024 at 07:16, Johannes Schneider via lists.openembedded.org wrote: > > systemd-sysext allows to overlay another image (or multiple) ontop of > a "base-image" = the current rootfs, via the use of overlayfs; to add > tools and features meant for development purposes. > > To quote the documentation on systemd-sysext: > " ...addition in order to make debugging/development easier). System > extension images should not be misunderstood as a generic software > packaging framework, ..." > > To build a lean image, that only holds packages that are not already > part of the base-image, a snapshot of the package-database is taken > after the installation of the base-rootfs is done, and picked up again > when collecting the rootfs of such a extension image. > > with all this in place an example usage could look like this: > some-core-image.bb > inherit core-image > IMAGE_GEN_PKGDBFS = "1" > > extending-image.bb > inherit image-sysext > IMAGE_FSTYPES = "squashfs" > IMAGE_BASE_PKGDB = "some-core-image" > # the above pointing at a package-db similar to: > # > build/deploy/images/$MACHINE/some-core-image-$MACHINE-20240210172305-pkgdb.rootfs.tar.gz > > then on the device, running some-core-image, with the extension image placed > at FN: > $> ln -s "$FN" /run/extensions/$(basename $FN).raw > $> systemd-sysext list > $> SYSTEMD_LOG_LEVEL=debug systemd-sysext merge > > As long as the VERSION_ID of the extension image matches the os-release > in the base image, the above commands return sucessfully; > for details on the compativility check see the docs for systemd-sysext. > > = > > changes with v2: > rebase from 'kirkstone' onto 'master' > > changes with v3; > incorporate review suggestions for simplification > add task dependency handling > add oe-selftest for the pkgdb handling > add variable documentation and > some more comments, and examples in the commit-msg > > changes with v4; > rebase onto 'master' => no functional changes > fixed patchtest findings > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#196593): https://lists.openembedded.org/g/openembedded-core/message/196593 Mute This Topic: https://lists.openembedded.org/mt/104717642/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] [PATCH v4 0/3] pkg-database and systemd-sysext image
There is a feature freeze now, so this might have to wait for after that. Alex On Mon, 4 Mar 2024 at 07:16, Johannes Schneider via lists.openembedded.org wrote: > > systemd-sysext allows to overlay another image (or multiple) ontop of > a "base-image" = the current rootfs, via the use of overlayfs; to add > tools and features meant for development purposes. > > To quote the documentation on systemd-sysext: > " ...addition in order to make debugging/development easier). System > extension images should not be misunderstood as a generic software > packaging framework, ..." > > To build a lean image, that only holds packages that are not already > part of the base-image, a snapshot of the package-database is taken > after the installation of the base-rootfs is done, and picked up again > when collecting the rootfs of such a extension image. > > with all this in place an example usage could look like this: > some-core-image.bb > inherit core-image > IMAGE_GEN_PKGDBFS = "1" > > extending-image.bb > inherit image-sysext > IMAGE_FSTYPES = "squashfs" > IMAGE_BASE_PKGDB = "some-core-image" > # the above pointing at a package-db similar to: > # > build/deploy/images/$MACHINE/some-core-image-$MACHINE-20240210172305-pkgdb.rootfs.tar.gz > > then on the device, running some-core-image, with the extension image placed > at FN: > $> ln -s "$FN" /run/extensions/$(basename $FN).raw > $> systemd-sysext list > $> SYSTEMD_LOG_LEVEL=debug systemd-sysext merge > > As long as the VERSION_ID of the extension image matches the os-release > in the base image, the above commands return sucessfully; > for details on the compativility check see the docs for systemd-sysext. > > = > > changes with v2: > rebase from 'kirkstone' onto 'master' > > changes with v3; > incorporate review suggestions for simplification > add task dependency handling > add oe-selftest for the pkgdb handling > add variable documentation and > some more comments, and examples in the commit-msg > > changes with v4; > rebase onto 'master' => no functional changes > fixed patchtest findings > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#196592): https://lists.openembedded.org/g/openembedded-core/message/196592 Mute This Topic: https://lists.openembedded.org/mt/104717642/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
