linux/poky.git/meta/recipes-devtools, branch yocto-3.3.2

dwarfsrcfiles: Avoid races over debug-link files

2021-07-20T18:05:45+00:00

We use dwarfsrcfiles in package.bbclass to list the source files used by a binary. This is done before they're stripped and linked to debug symbols in separate files. It is possible a binary may already have a link to separate debug symbols, e.g. some of the test binaries in lttng-tools ptest. In those cases, the linked binary may be changed by package.bbclass code whilst dwarfsrcfiles is reading it. That would result in a rare SIGBUS race causing the binary to fail. To avoid this, break the debug file search path so no other binaries are found. Also fix a segfault if no binary is specified while here. [YOCTO #14400] (From OE-Core rev: 52382a03c10a6985ecb6ada24523cb9daf9c6201) Signed-off-by: Richard Purdie (cherry picked from commit efef732859e265533acf16f2f4da3b29d50e0df4) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

go: upgrade 1.16.4 -> 1.16.5

2021-07-20T18:05:45+00:00

(From OE-Core rev: d07d0ed6b831b6cfca12e4c5db81324372ae06ce) Signed-off-by: Wang Mingyu Signed-off-by: Richard Purdie (cherry picked from commit c0c567ed2fb092cde97d03cb658d8bae93d9b28c) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

go: upgrade 1.16.3 -> 1.16.4

2021-07-20T18:05:45+00:00

(From OE-Core rev: 966ae80290b1a2daef87cf1ee2f176a8317c7c95) Signed-off-by: Wang Mingyu Signed-off-by: Richard Purdie (cherry picked from commit 1e280a596293976ac835b557dcaaa56972682480) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

binutils: Fix CVE-2021-20197

2021-07-20T18:05:45+00:00

Source: git://sourceware.org/git/binutils-gdb.git Tracking -- https://sourceware.org/bugzilla/show_bug.cgi?id=26945 Backported upstream commit id d3edaa91d4cf7202ec14342410194841e2f67f12 and its dependent commits 8e03235147a9e774d3ba084e93c2da1aa94d1cec and 8b69e61d4be276bb862698aaafddc3e779d23c8f to binutils-2.36 source. Upstream-Status: Backport [https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=8e03235147a9e774d3ba084e93c2da1aa94d1cec] Upstream-Status: Backport [https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=d3edaa91d4cf7202ec14342410194841e2f67f12] Upstream-Status: Backport [https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=8b69e61d4be276bb862698aaafddc3e779d23c8f] (From OE-Core rev: f5f831c3a76456bce543d42d0f14411b28770b45) Signed-off-by: Vinay Kumar Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

perl: correct libpth and glibpth

2021-07-20T18:05:45+00:00

Previouly there is a logic as below used to set libpth in config.sh. libpth='@LIBDIR@ @BASELIBDIR@' But after the below commits introduced, the above logic is dropped. 52f2828314 perl: add a version that builds the recipe using perl-cross, and update to 5.28.1 68552c3532 perl: remove the previous version of the recipe So correct the value of libpth and glibpth to add the dropped logic back to avoid confusing. Before the patch(on 64bits system): # perl -V:libpth libpth='/usr/lib /lib'; After the patch(on 64bits system): # perl -V:libpth libpth='/usr/lib64 /lib64'; (From OE-Core rev: afe58be55b4efc360420a00cbcf60dd5d99ed556) Signed-off-by: Mingli Yu Signed-off-by: Richard Purdie (cherry picked from commit a494de43c3ccdcf7af988765ae5c3a95bc20c567) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

valgrind: Actually install list of non-deterministic ptests

2021-06-26T14:24:08+00:00

Install list of non-deterministic threaded ptests to be run using taskset to force them to a single core. This commit works with b318944d7, which updated the testing script to run the non-deterministic tests separately but didn't install the list of tests, so these tests were being run without taskset. The taskset_nondeterministic_tests file is the list of tests that will be run separately with taskset, and ignored during the other tests. This is installed to /usr/lib/valgrind/ptest similar to the 2 existing lists for tests to skip on ARM and all architectures. Removed bar_bad and bar_bad_xml to be included separately as they cause issues on non-kvm QEMU instances. See: b318944dd7 valgrind: Improve non-deterministic ptest reliability for more info. (From OE-Core rev: f076edb7515ba2ecfc0adbfdf30ae5a9aa96e231) Signed-off-by: Tony Tascioglu Signed-off-by: Richard Purdie (cherry picked from commit 3d23985d0d653844863ed513d75d93a36359992f) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

valgrind: remove buggy ptest from arm64

2021-06-26T14:24:08+00:00

This commit removes the stack_changes ptest from aarch64 devices. This test is buggy and fails almost 100% of the time in qemuarm64. In general, many of the valgrind tests are more likely to fail on qemuarm64 vs native x86_64. This test previously worked on gatesgarth and dunfell, but has been failing since hardknott. It might be due to a recent change in the cross-compiler or glibc. The test runs fine when running natively on arm on a Raspberry Pi. Until we can find the root cause for the failures, this shorter term solution should clear up some of the noise from the autobuilder from a known failure. (From OE-Core rev: 731d0e9c6921a3ac82e5172e5c7a6088e80243ef) Signed-off-by: Tony Tascioglu Signed-off-by: Richard Purdie (cherry picked from commit 82d6411b80a46d8ec0258ca75c3c80dc6128d44e) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

valgrind: Improve non-deterministic ptest reliability

2021-06-20T08:43:39+00:00

Several of the valgrind tests (particulaly helgrind) are unreliable and can fail with a different output. Particularly, there is a higher chance of failure on QEMU instances with SMP enabled and on systems with more interrupts such as laptops on powersave. The tests have been reported upstream as being unreliable dating back over 5 years, due in part to the ordering of threads during an "unwinding" process in helgrind. https://bugs.kde.org/show_bug.cgi?id=345121 https://bugs.kde.org/show_bug.cgi?id=430321 A workaround to improve the reliability of such tests is to force them to run on a single CPU core using taskset. This greatly reduces the chance of a failure. >From my testing, I have found it can help reduce the rate of failures on both a laptop and QEMU by over 5x. Stress-testing in QEMU for several hours did not result in a failure while running the test normally did. The flaky or undeterministic thread-based tests are defined in the taskset_nondeterministic_tests file. These test cases will be run with taskset 0x00000001 to run on a single CPU core rather then the regular test. The edited run-ptest executes the flaky tests first, then ignores them to not duplicate the results from the main tests. Everything modified is restored when testing is complete. The drawback is that this isn't a foolproof solution. It helps the tests fail much less frequently, and considering how this issue has been documented for a long time, a workaround such as this is needed. (From OE-Core rev: 79ec1d73a107277586d3d8e9c0d46dfc0ac2b0d8) Signed-off-by: Tony Tascioglu Signed-off-by: Richard Purdie (cherry picked from commit b318944dd72ca7b0408e955f3599381ab3ac3ba8) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

valgrind: fix a typo

2021-06-20T08:43:39+00:00

(From OE-Core rev: d68c62bb93ab400878aecc42ee06df103356a2bf) Signed-off-by: Kai Kang Signed-off-by: Richard Purdie (cherry picked from commit 0478d9b04d6a6d10e439116b23b641a1e2553e26) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

python3: upgrade 3.9.4 -> 3.9.5

2021-06-20T08:43:39+00:00

Version 3.9.5 includes a fix for CVE-2021-29921. (From OE-Core rev: e40120185659e48f73e1aef029b699e2207e30de) Signed-off-by: Trevor Gamblin Signed-off-by: Richard Purdie (cherry picked from commit be23351f97c1a7362c0ddd240a6de0cddfca1b01) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie