From: Denis Kenzior <denkenz@gmail.com>
To: iwd@lists.01.org
Subject: Re: iwd 1.17 test suite is failing
Date: Mon, 23 Aug 2021 08:58:54 -0500 [thread overview]
Message-ID: <c4b50311-84ab-236a-e3cd-49371a9d7eb4@gmail.com> (raw)
In-Reply-To: <CABB28CwPkyQcCrznB2MbEGN5TKMoSvCnaPH5DSY5SJ-YaJe47w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3921 bytes --]
Hi Tomasz,
On 8/22/21 1:55 PM, Tomasz Kłoczko wrote:
> Hi,
>
> I think that it started around 1.15.
> iwd and eel compiled with LTO.
>
> [tkloczko(a)barrel iwd-1.17]$ make check
> make --no-print-directory check-am
> make --no-print-directory check-TESTS
> PASS: unit/test-cmac-aes
> PASS: unit/test-hmac-md5
> PASS: unit/test-hmac-sha1
> PASS: unit/test-hmac-sha256
> PASS: unit/test-prf-sha1
> PASS: unit/test-kdf-sha256
> PASS: unit/test-crypto
> ./build-aux/test-driver: line 107: 3860965 Aborted (core dumped)
> "$@" > $log_file 2>&1
> FAIL: unit/test-eapol
There was indeed a failure that slipped through the cracks. This was due to the
test not being updated and is now fixed upstream with commit ed10b00afa3f
("unit: Fix eapol IP Allocation test failure")
> PASS: unit/test-mpdu
> PASS: unit/test-ie
> PASS: unit/test-util
> PASS: unit/test-ssid-security
> PASS: unit/test-arc4
> PASS: unit/test-wsc
> PASS: unit/test-eap-mschapv2
> PASS: unit/test-eap-sim
> /bin/sh ./libtool --tag=CC --mode=link /usr/bin/gcc -fvisibility=hidden
> -DUNITDIR=\""./unit/"\" -DCERTDIR=\""./unit/"\" -O2 -g -grecord-gcc-switches
> -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2
> -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1
> -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64
> -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection
> -fcf-protection -fdata-sections -ffunction-sections -flto=auto
> -flto-partition=none -Os -Wl,-wrap,l_ecc_supported_ike_groups -Wl,-z,relro
> -Wl,--as-needed -Wl,--gc-sections -Wl,-z,now
> -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -flto=auto -flto-partition=none
> -fuse-linker-plugin -o unit/test-sae unit/test-sae.o src/sae.o src/crypto.o
> src/ie.o src/handshake.o src/erp.o src/util.o src/mpdu.o -lell
> libtool: link: /usr/bin/gcc -fvisibility=hidden -DUNITDIR=\"./unit/\"
> -DCERTDIR=\"./unit/\" -O2 -g -grecord-gcc-switches -pipe -Wall
> -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS
> -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong
> -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic
> -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection
> -fdata-sections -ffunction-sections -flto=auto -flto-partition=none -Os
> -Wl,-wrap -Wl,l_ecc_supported_ike_groups -Wl,-z -Wl,relro -Wl,--as-needed
> -Wl,--gc-sections -Wl,-z -Wl,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld
> -flto=auto -flto-partition=none -fuse-linker-plugin -o unit/test-sae
> unit/test-sae.o src/sae.o src/crypto.o src/ie.o src/handshake.o src/erp.o
> src/util.o src/mpdu.o -lell
> /usr/bin/ld: /tmp/cc8uiWzL.lto.o: in function `sae_choose_next_group':
> /home/tkloczko/rpmbuild/BUILD/iwd-1.17/src/sae.c:139: undefined reference to
> `__wrap_l_ecc_supported_ike_groups'
> /usr/bin/ld: /tmp/cc8uiWzL.lto.o: in function `handshake_state_free':
> /home/tkloczko/rpmbuild/BUILD/iwd-1.17/src/handshake.c:48: undefined reference
> to `__wrap_l_ecc_supported_ike_groups'
> /usr/bin/ld: /tmp/cc8uiWzL.lto.o: in function `sae_rx_authenticate':
> /home/tkloczko/rpmbuild/BUILD/iwd-1.17/src/sae.c:161: undefined reference to
> `__wrap_l_ecc_supported_ike_groups'
This would have shown up earliest at iwd 1.16. However, I'm not sure what this
is about? We use
unit_test_sae_LDFLAGS = -Wl,-wrap,l_ecc_supported_ike_groups
Perhaps LTO somehow interferes with that? ell has a unit test that uses the
same mechanism for quite some time...
>
> BTW is it possible to organize iwd/eel mirrors on github/gitlab to be able
> submit such an issue without being forced to subscribe to yet another mailing
> list or put in README files details how to submit the issue?
>
We'll look into it.
Regards,
-Denis
next prev parent reply other threads:[~2021-08-23 13:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-22 18:55 iwd 1.17 test suite is failing Tomasz =?unknown-8bit?q?K=C5=82oczko?=
2021-08-23 13:58 ` Denis Kenzior [this message]
[not found] <fdd0ba77-54d3-955c-80bb-80e9e2deaa8a@gmail.com>
2021-08-23 16:58 ` Tomasz =?unknown-8bit?q?K=C5=82oczko?=
2021-08-23 17:05 ` Denis Kenzior
2021-08-23 17:25 ` Tomasz =?unknown-8bit?q?K=C5=82oczko?=
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c4b50311-84ab-236a-e3cd-49371a9d7eb4@gmail.com \
--to=denkenz@gmail.com \
--cc=iwd@lists.01.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox