we now have more rust/cargo recipes and tests that cover various use cases
so this is no longer needed.
(From OE-Core rev: 8baaf94d200f5355791ecd980727698b1ab0e539)
Signed-off-by: Frederic Martinsons <frederic.martinsons@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This provides pylibfdt, which is a runtime dependency for the dtschema
module that we already carry in oe-core.
(From OE-Core rev: 123077ecd9f3c1839da0d7b1474d689e5c6a689c)
Signed-off-by: Trevor Gamblin <tgamblin@baylibre.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
- Replace CVE_CHECK_IGNORE with CVE_STATUS to be more flexible.
The CVE_STATUS should contain an information about status wich
is decoded in 3 items:
- generic status: "Ignored", "Patched" or "Unpatched"
- more detailed status enum
- description: free text describing reason for status
Examples of usage:
CVE_STATUS[CVE-1234-0001] = "not-applicable-platform: Issue only applies on Windows"
CVE_STATUS[CVE-1234-0002] = "fixed-version: Fixed externally"
CVE_CHECK_STATUSMAP[not-applicable-platform] = "Ignored"
CVE_CHECK_STATUSMAP[fixed-version] = "Patched"
(From OE-Core rev: 34f682a24b7075b12ec308154b937ad118d69fe5)
Signed-off-by: Andrej Valek <andrej.valek@siemens.com>
Signed-off-by: Peter Marko <peter.marko@siemens.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Include support for ACLs for native builds by default.
(From OE-Core rev: eeb3f8e893e351520f3b8e642027e0dd6ca7c08b)
Signed-off-by: Piotr Łobacz <p.lobacz@welotec.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The Xdmx server was removed from the xorg-server sources in xorg-server
21 (released Oct. 2021), so this is only useful for communicating with
Xdmx from the 1.20 and older releases.
Also remove the DEPENDS on libdmx in xdpyinfo for the same reason.
(From OE-Core rev: 09a1a0473a5ab0fb984121443f5be8f0188e8883)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The 6.4 kernel causes parselog failures when Xorg starts:
(II) FBDEV(0): checking modes against framebuffer device...
(II) FBDEV(0): mode "640x480" test failed
(II) FBDEV(0): mode "640x480" test failed
(II) FBDEV(0): mode "640x480" test failed
(II) FBDEV(0): mode "640x480" test failed
(II) FBDEV(0): mode "640x480" not found
It appears to be specific to qemuarm without GL. Until this is resolved,
pin the qemuarm BSP to 6.1.
(From OE-Core rev: 28615ad284243db4465c843c456083c9d4b3a0c4)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Enable branch protection (PAC/BTI) for all aarch64 builds. This was
previously enabled at a global level in the GCC build, but that breaks
the gcc test suite.
(From OE-Core rev: 8905639d1cdc5ce809cc5ecd9672f5e86bf8a579)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
kernel version 6.4 is the reference kernel for the fall
release.
This brings libc-headers up to date with that tested
reference
For musl, we drop one patch that has been merged upstream.
(From OE-Core rev: 8dce94b89396a99bb20a0a0ba9db0244d95db7e0)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
We've a slew of CVE_CHECK_IGNOREs in cve-extra-exclusions which are to
mark a CVE as not valid with the current default kernel. However, this
file is kernel agnostic so if someone decides to build a 6.0 kernel then
these ignores are no longer valid.
Move the ignores which are to simply reflect backports to
cve-exclusions_6.1.inc so that they're version-specific. As the kernel
is upgraded these exclusions should be made redundant and removed from
the file.
(From OE-Core rev: 157f7b62e271df5dfd8a3bc4d3821bf806fde51e)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The ptest problems reported in e21021dc00ec ("mdadm: drop from PTESTS_SLOW")
should now be fixed, so mdadm can be added back to PTESTS_SLOW (a qemux86-64
test run takes about ~12 minutes to execute with kvm).
root@qemux86-64:~# ptest-runner mdadm
START: ptest-runner
2023-06-30T08:25
BEGIN: /usr/lib/mdadm/ptest
PASS: /usr/lib/mdadm/ptest/tests/00linear
PASS: /usr/lib/mdadm/ptest/tests/00multipath
...
PASS: /usr/lib/mdadm/ptest/tests/19repair-does-not-destroy
PASS: /usr/lib/mdadm/ptest/tests/20raid5journal
PASS: /usr/lib/mdadm/ptest/tests/21raid5cache
DURATION: 723
END: /usr/lib/mdadm/ptest
2023-06-30T09:16
STOP: ptest-runner
TOTAL: 1 FAIL: 0
For the testcases to run correctly, there must be enough rootfs space to create
13 loop devices. Similar to strace and lttng-tools, add a new
IMAGE_ROOTFS_EXTRA_SPACE entry for mdadm-ptest.
(From OE-Core rev: dfefff63c547adb1add0c8e3a308b2d0bd6cfc8c)
Signed-off-by: Ovidiu Panait <ovidiu.panait@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Additionally:
- drop pseudo from INSANE_SKIP for 32bit time API check
(pseudo passes the check; it's not clear where the issue may have been)
- move rust exceptions to the cargo class, as the problem
is common across the ecosystem, and needs to be fixed in the
libc crate.
(From OE-Core rev: d3d406bf636e579c17708b408e11c12d252533ee)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The replacement cve-update-nvd2-native is working, so we can remove the
old recipe now.
(From OE-Core rev: 17eb07885147a06bf7bdd43f7869fe4411be80a0)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Until strace can handle the interface with glibc correctly with those flags,
disable there for now.
(From OE-Core rev: 5235ae1a14b71d42c1effff51e0289654bc7122a)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
There is a problem with 32 bit time looming for many 32 bit platforms
including arm, mip32, powerpc and x86 (but not riscv32) in 2038 when the
32 bit field time_t can no longer store the time value correctly due
to overflow.
Preparing for this is tricky as the ABI between libraries and binaries
will change and it isn't possible to migrate easily as structures and
return values change size.
As we're a source based system, the project has taken the decision that
we should change the compiler flags to switch to both largefile and 64
bit time_t. With OE-Core we've ironed out the issues we could spot
apart from some testing issues in strace and lttng-tools for which
discussions are ongoing upstream. There is more testing to be done
but we wanted to make this switch now in good time before our next
LTS release so we can work through any issues arrising.
We had already tried to mandate largefile everywhere before this but
this gives an opportunity to ensure that at the same time.
(From OE-Core rev: b9e0c5e750c3097e176fdc18b3b58b622f716e71)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add a new layer specific override based upon the FILE_LAYERNAME support now present
in bitbake. In particular this allows layer specific QA warnings and errors to
be made more easily.
(From OE-Core rev: 144db9241b141c3380a2b292414d04bfc39a2e20)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
rpm2cpio.sh can make calls to unzstd to uncompress the RPM payload that
conform the cpio file.
zstd is already part of HOSTTOOLS, as a link to the system installed
zstd.
This patch add unzstd in HOSTOOLS list as a non-optional binary, so is
available to rpm2cpio.sh when it is required.
(From OE-Core rev: bff58d337890e804d33d7decbaa46065a4d3bba4)
Signed-off-by: Alberto Planas <aplanas@suse.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
We were not able to get a response about availability over email, and so the recipe
has to be unassigned.
(From OE-Core rev: 56f1af6d5b3019dccbc27bb0a9692a5f1a32f87b)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
We were not able to get a response about availability over email, and so the recipes
have to be unassigned.
(From OE-Core rev: 2d2c75530fe336eda72e8ce72f994725b3a77ea0)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
We were not able to get a response about availability over email, and so the recipe
has to be unassigned.
(From OE-Core rev: 5be575577d74a3cb81594392b88df74226be9192)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
We were not able to get a response about availability over email, and so the recipe
has to be unassigned.
(From OE-Core rev: 60eda3dcbf96b5982a0e282fd0c3c13b0b4d7787)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
We were not able to get a response about availability over email, and so the recipe
has to be unassigned.
(From OE-Core rev: 3beb88060be9484cfe75dfa60f041b0b32214978)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
APM has been obsolete for a very long time, and debian no longer
packages it or carries the source tarball.
(From OE-Core rev: d987b79725eb0da2704091d22e3d16b8026fac7d)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Remove the blanket ignore and handle the CVEs individually.
CVE-2019-14899 is related to network interface configuration across
multiple operating systems, so leave this as unresolved.
-3016, -3819 and -3887 are pending CPE updates, so ignore them.
The others have accurate CPE information now so are handled correctly.
(From OE-Core rev: e46bd62a278ec0bb9da995cab9350f1c363131d1)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
All of these CVEs have been fixed in the kernel point release that we
currently ship, so ignore them.
(From OE-Core rev: 86aee302673146dca10f313d0c70b69d6c4bdc7d)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add a recipe to build the Khronos official Vulkan validation
layers that can assist developers in verifying that their
applications correctly use the Vulkan APIs.
(From OE-Core rev: 35662be85affca2b4d19112d79dfcd9223f573b2)
Signed-off-by: Vincent Davis Jr <vince@underview.tech>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
These CVEs have all been fixed <6.1.30, which is the default linux-yocto
kernel version.
(From OE-Core rev: 73f03970f0aadfb053666a1e93f6f6d5b5156ca6)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add a dependency which should have been in this list but wasn't, found
when debugging create-spdx hash issues.
(From OE-Core rev: 1075b9fc5d562dada45b3187cb737511ff8c7376)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Also add SRCPV to the list of BB_HASH_CODEPARSER_VALS for code parser
cache handling. Otherwise an empty SRC_URI in the list triggers this
exception:
bb.data_smart.ExpansionError: Failure expanding variable SRCPV, expression was ${@bb.fetch2.get_srcrev(d)} which triggered exception
FetchError: Fetcher failure: SRCREV was used yet no valid SCM was found in SRC_URI
The variable dependency chain for the failure is: SRCPV -> UBOOT_LOCALVERSION -> do_compile
(From OE-Core rev: d17f9da69f430337ee1ef9c09b731c27393eba83)
Signed-off-by: Denys Dmytriyenko <denis@denix.org>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Just like UBOOT_LOCALVERSION, an end user can set KERNEL_LOCALVERSION
to append a string to the name of the local version of the kernel
image.
(From OE-Core rev: 229435a52f36ddec5f85fb6d5ccd42044b688397)
Signed-off-by: Ming Liu <liu.ming50@gmail.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This was confirmed via private email.
(From OE-Core rev: c30e9f1972a3e1d4099f39fd6d0dfb37acb73ce1)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This was confirmed via private email.
(From OE-Core rev: cc8bb0da24419424989548ced27b2e76030340d9)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This was confirmed via private email.
(From OE-Core rev: 834519933fcd6e4ff54f24d0cf671ea9ce24398a)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Some distros e.g. gentoo have latest on gcc-13 branch and we have a
situation where libstdc++ ABI is changed between 13.1 and 13.2 so
official 13.1 release based uninative will no longer work on these
distros, therefore switch to a snapshot that includes [1] which fixes
it
[1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108969
Reported-by: Martin Jansa <Martin.Jansa@gmail.com>
(From OE-Core rev: d554c404166f6ba1aa247c377fa9d3316e53aa40)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Cc: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
