On 9/14/23 17:04, Siddhesh Poyarekar wrote:
On 2023-09-14 16:32, ci_notify@linaro.org wrote:
Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain@lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel.
In CI config tcwg_glibc_check/master-arm after:
| glibc patch https://patchwork.sourceware.org/patch/75959 | Author: Siddhesh Poyarekar siddhesh@sourceware.org | Date: Thu Sep 14 06:13:02 2023 -0400 | | getaddrinfo: Fix use after free in getcanonname (CVE-2023-4806) | | When an NSS plugin only implements the _gethostbyname2_r and | _getcanonname_r callbacks, getaddrinfo could use memory that was freed | during tmpbuf resizing, through h_name in a previous query response. | Fix this by copying h_name over and freeing it at the end. | | ... 3 lines of the commit log omitted. | ... applied on top of baseline commit: | 803f4073cc Add MOVE_MOUNT_BENEATH from Linux 6.5 to sys/mount.h
FAIL: 1 regressions
regressions.sum: === glibc tests ===
Running glibc:nss ... FAIL: nss/tst-nss-gai-hv2-canonname
=== Results Summary ===
You can find the failure logs in *.log.1.xz files in - https://ci.linaro.org/job/tcwg_glibc_check--master-arm-precommit/703/artifac... . The full lists of regressions and progressions are in - https://ci.linaro.org/job/tcwg_glibc_check--master-arm-precommit/703/artifac... . The list of [ignored] baseline and flaky failures are in - https://ci.linaro.org/job/tcwg_glibc_check--master-arm-precommit/703/artifac... .
-----------------8<--------------------------8<--------------------------8<-------------------------- The information below can be used to reproduce a debug environment:
Current build : https://ci.linaro.org/job/tcwg_glibc_check--master-arm-precommit/703/artifac... Reference build : https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/612/artifact/ar...
Hello,
I'm looking at the logs and all it has is:
original exit status 127 running post-clean rsync
for the new test. It looks like other NSS tests also fail in the same way. Is this a known issue on arm?
I saw this too when I was doing the review for the patch.
And what I noticed was this:
Running glibc:nss ... FAIL: nss/tst-nss-compat1 FAIL: nss/tst-nss-db-endgrent FAIL: nss/tst-nss-db-endpwent FAIL: nss/tst-nss-files-hosts-getent FAIL: nss/tst-nss-files-hosts-long FAIL: nss/tst-nss-files-hosts-v4mapped FAIL: nss/tst-nss-gai-actions FAIL: nss/tst-nss-test3 FAIL: nss/tst-reload1 FAIL: nss/tst-reload2
Which means...
75 tests-container := \ 76 tst-nss-compat1 \ 77 tst-nss-db-endgrent \ 78 tst-nss-db-endpwent \ 79 tst-nss-files-hosts-long \ 80 tst-nss-files-hosts-v4mapped \ 81 tst-nss-gai-actions \ 82 tst-nss-test3 \ 83 tst-reload1 \ 84 tst-reload2 \ 85 # tests-container
... all the container tests fail.
Note that tst-nss-files-hosts-getent is *not* a container test, but it does use support_become_root() and xchroot() which means it is one of the containerized tests using variant test infrastructure.
So this looked like either an infrastructure issue or permission issues with running those tests.
I did my own testing on x86_64 and i686 and it was clean.