b60e852b74
Solves CVE-2025-0395 git log: 662516aca8 stdlib: Test using setenv with updated environ [BZ #32588] 1432850ad8 malloc: obscure calloc use in tst-calloc c1f7bfbe08 Hide all malloc functions from compiler [BZ #32366] 808a84a8b8 Fix underallocation of abort_msg_s struct (CVE-2025-0395) 994b129a35 x86/string: Fixup alignment of main loop in str{n}cmp-evex [BZ #32212] 61daaa7639 x86: Improve large memset perf with non-temporal stores [RHEL-29312] 2c8a7f14fa x86: Avoid integer truncation with large cache sizes (bug 32470) 2c882bf9c1 math: Exclude internal math symbols for tests [BZ #32414] 51da74a97e malloc: add indirection for malloc(-like) functions in tests [BZ #32366] aa8768999e Pass -nostdlib -nostartfiles together with -r [BZ #31753] 350db28393 nptl: initialize cpu_id_start prior to rseq registration 9a0e174a39 nptl: initialize rseq area prior to registration test results: Before After Diff FAIL 208 210 +2 PASS 4906 4905 -1 UNSUPPORTED 230 230 0 XFAIL 16 16 0 XPASS 4 4 0 failed test changes: - nptl/tst-mutexpi8-static - stdlib/tst-qsort4 + malloc/tst-dynarray-fail-mem + malloc/tst-malloc_info + malloc/tst-malloc_info-malloc-check + malloc/tst-malloc_info-malloc-hugetlb2 (From OE-Core rev: 54181d6ca63a720dcebb241892e76e9cdd75260c) Signed-off-by: Peter Marko <peter.marko@siemens.com> Signed-off-by: Steve Sakoman <steve@sakoman.com>
Poky
Poky is an integration of various components to form a pre-packaged build system and development environment which is used as a development and validation tool by the Yocto Project. It features support for building customised embedded style device images and custom containers. There are reference demo images ranging from X11/GTK+ to Weston, commandline and more. The system supports cross-architecture application development using QEMU emulation and a standalone toolchain and SDK suitable for IDE integration.
Additional information on the specifics of hardware that Poky supports is available in README.hardware. Further hardware support can easily be added in the form of BSP layers which extend the systems capabilities in a modular way. Many layers are available and can be found through the layer index.
As an integration layer Poky consists of several upstream projects such as BitBake, OpenEmbedded-Core, Yocto documentation, the 'meta-yocto' layer which has configuration and hardware support components. These components are all part of the Yocto Project and OpenEmbedded ecosystems.
The Yocto Project has extensive documentation about the system including a reference manual which can be found at https://docs.yoctoproject.org/
OpenEmbedded is the build architecture used by Poky and the Yocto project. For information about OpenEmbedded, see the OpenEmbedded website.
Contribution Guidelines
Please refer to our contributor guide here: https://docs.yoctoproject.org/dev/contributor-guide/ for full details on how to submit changes.
Where to Send Patches
As Poky is an integration repository (built using a tool called combo-layer), patches against the various components should be sent to their respective upstreams:
OpenEmbedded-Core (files in meta/, meta-selftest/, meta-skeleton/, scripts/):
- Git repository: https://git.openembedded.org/openembedded-core/
- Mailing list: openembedded-core@lists.openembedded.org
BitBake (files in bitbake/):
- Git repository: https://git.openembedded.org/bitbake/
- Mailing list: bitbake-devel@lists.openembedded.org
Documentation (files in documentation/):
- Git repository: https://git.yoctoproject.org/cgit/cgit.cgi/yocto-docs/
- Mailing list: docs@lists.yoctoproject.org
meta-yocto (files in meta-poky/, meta-yocto-bsp/):
- Git repository: https://git.yoctoproject.org/cgit/cgit.cgi/meta-yocto
- Mailing list: poky@lists.yoctoproject.org
If in doubt, check the openembedded-core git repository for the content you intend to modify as most files are from there unless clearly one of the above categories. Before sending, be sure the patches apply cleanly to the current git repository branch in question.