Accessing to arm64 for investing issues in TLS error.

[shigeki]

For further investigation of arm64 issues fo TLS error, I need to access and work on arm64 as commented in nodejs/node#23913 (comment).

CC @refack
Ref: nodejs/node#23913

[gdams]

I personally have no objections, can someone else from @nodejs/build approve as well?

[Trott]

+1

[refack]

+1
Will get to it later.

[refack]

Someone else already put the keys in 147.75.74.174

[shigeki]

Oops, I've forgot the same issue of #842 in the Node-v8 and it occurs again in the current Node. My key is still remained. I will check if binaries as I did before.

[shigeki]

I've checked asm binaries have no difference between Node-v10 and bare openssl-1.1.0i as below.

oot@test-packetnet-ubuntu1604-arm64-2:/var/tmp/shigeki/node# ls -l out/Release/obj.target/openssl/deps/openssl/config/archs/linux-aarch64/asm/crypto/*/*.o
-rw-r--r-- 1 root root   3576 Nov 13 06:50 out/Release/obj.target/openssl/deps/openssl/config/archs/linux-aarch64/asm/crypto/aes/aesv8-armx.o
-rw-r--r-- 1 root root   5344 Nov 13 06:50 out/Release/obj.target/openssl/deps/openssl/config/archs/linux-aarch64/asm/crypto/aes/vpaes-armv8.o
-rw-r--r-- 1 root root   5592 Nov 13 06:50 out/Release/obj.target/openssl/deps/openssl/config/archs/linux-aarch64/asm/crypto/bn/armv8-mont.o
-rw-r--r-- 1 root root   8152 Nov 13 06:50 out/Release/obj.target/openssl/deps/openssl/config/archs/linux-aarch64/asm/crypto/chacha/chacha-armv8.o
-rw-r--r-- 1 root root 162168 Nov 13 06:50 out/Release/obj.target/openssl/deps/openssl/config/archs/linux-aarch64/asm/crypto/ec/ecp_nistz256-armv8.o
-rw-r--r-- 1 root root   1520 Nov 13 06:50 out/Release/obj.target/openssl/deps/openssl/config/archs/linux-aarch64/asm/crypto/modes/ghashv8-armx.o
-rw-r--r-- 1 root root   3784 Nov 13 06:50 out/Release/obj.target/openssl/deps/openssl/config/archs/linux-aarch64/asm/crypto/poly1305/poly1305-armv8.o
-rw-r--r-- 1 root root   5712 Nov 13 06:50 out/Release/obj.target/openssl/deps/openssl/config/archs/linux-aarch64/asm/crypto/sha/sha1-armv8.o
-rw-r--r-- 1 root root   5544 Nov 13 06:50 out/Release/obj.target/openssl/deps/openssl/config/archs/linux-aarch64/asm/crypto/sha/sha256-armv8.o
-rw-r--r-- 1 root root   5296 Nov 13 06:50 out/Release/obj.target/openssl/deps/openssl/config/archs/linux-aarch64/asm/crypto/sha/sha512-armv8.o

root@test-packetnet-ubuntu1604-arm64-2:/var/tmp/shigeki/node# ls -l ../openssl-1.1.0i/crypto/*/*.o |grep arm
-rw-r--r-- 1 root root   3576 Nov 13 06:02 ../openssl-1.1.0i/crypto/aes/aesv8-armx.o
-rw-r--r-- 1 root root   5344 Nov 13 06:02 ../openssl-1.1.0i/crypto/aes/vpaes-armv8.o
-rw-r--r-- 1 root root   5592 Nov 13 06:02 ../openssl-1.1.0i/crypto/bn/armv8-mont.o
-rw-r--r-- 1 root root   8152 Nov 13 06:02 ../openssl-1.1.0i/crypto/chacha/chacha-armv8.o
-rw-r--r-- 1 root root 162168 Nov 13 06:02 ../openssl-1.1.0i/crypto/ec/ecp_nistz256-armv8.o
-rw-r--r-- 1 root root   1520 Nov 13 06:02 ../openssl-1.1.0i/crypto/modes/ghashv8-armx.o
-rw-r--r-- 1 root root   3784 Nov 13 06:02 ../openssl-1.1.0i/crypto/poly1305/poly1305-armv8.o
-rw-r--r-- 1 root root   5712 Nov 13 06:02 ../openssl-1.1.0i/crypto/sha/sha1-armv8.o
-rw-r--r-- 1 root root   5544 Nov 13 06:02 ../openssl-1.1.0i/crypto/sha/sha256-armv8.o
-rw-r--r-- 1 root root   5296 Nov 13 06:02 ../openssl-1.1.0i/crypto/sha/sha512-armv8.o

In above, they are build with Configure linux-aarch64 not config in order to omit -Wa,--noexecstack option that would be resolved in OpenSSL-1.1.1.

I had an only once test failure of TLS error during several CIi tests. I could not succeed to reproduce the TLS error after many retries of tests by hand and TLS connection scripts. It seems to have more tests to reproduce it.

@refack Could you move the arm64 machine of test-packetnet-ubuntu1604-arm64-2 out of CI for I'd like to run many CI tests and TLS connection tests for reproduction of TLS errors.

[refack]

@refack Could you move the arm64 machine of test-packetnet-ubuntu1604-arm64-2 out of CI for I'd like to run many CI tests and TLS connection tests for reproduction of TLS errors.

Done.
https://ci.nodejs.org/computer/test-packetnet-ubuntu1604-arm64-2/

[shigeki]

@refack Thanks. I'm going to run parallel tests with SSL debugging in /var/tmp/shigeki/shigeki_node/node/run_test_ci.sh for days to see if TLS errors are reproduced.

[refack]

Sill working on this?

[shigeki]

Yes, I can reproduce the issue but cannot identify its cause. It still need more time for me to investigate it.

[refack]

I had an idea, to minimize interaction with CI please stop the Jenkins agent when doing manual testing and restarting it when done.

[mhdawson]

@shigeki still working on this now ?

[shigeki]

@mhdawson Yes, I currently continue to run tests on the CI arm64 server to see if the issue is really resolved in the current master HEAD.

[mhdawson]

k thanks.

[github-actions]

This issue is stale because it has been open many days with no activity. It will be closed soon unless the stale label is remove or a comment is made.