Test results for aarch64, cfarm425, crypto_sign/dilithium5aes

[Page version: 20261005 22:53:57]

TIMECOP error (can be valgrind bug)

error 1
Conditional jump or move depends on uninitialised value(s)
   at 0x...: rej_uniform (poly.c:348)
   by 0x...: crypto_sign_dilithium5aes_ref_constbranchindex_poly_uniform (poly.c:380)
   by 0x...: crypto_sign_dilithium5aes_ref_constbranchindex_polyvec_matrix_expand (polyvec.c:22)
   by 0x...: crypto_sign_dilithium5aes_ref_constbranchindex_keypair (sign.c:39)
   by 0x...: test (try.c:128)
   by 0x...: main (try-anything.c:344)
 Uninitialised value was created by a client request
   at 0x...: randombytes_callback (try-anything.c:308)
   by 0x...: crypto_sign_dilithium5aes_ref_constbranchindex_keypair (sign.c:32)
   by 0x...: test (try.c:128)
   by 0x...: main (try-anything.c:344)

Conditional jump or move depends on uninitialised value(s)
   at 0x...: rej_uniform (poly.c:348)
   by 0x...: crypto_sign_dilithium5aes_ref_constbranchindex_poly_uniform (poly.c:389)
   by 0x...: crypto_sign_dilithium5aes_ref_constbranchindex_polyvec_matrix_expand (polyvec.c:22)
   by 0x...: crypto_sign_dilithium5aes_ref_constbranchindex_keypair (sign.c:39)
   by 0x...: test (try.c:128)
   by 0x...: main (try-anything.c:344)
 Uninitialised value was created by a client request
   at 0x...: randombytes_callback (try-anything.c:308)
   by 0x...: crypto_sign_dilithium5aes_ref_constbranchindex_keypair (sign.c:32)
   by 0x...: test (try.c:128)
   by 0x...: main (try-anything.c:344)

Conditional jump or move depends on uninitialised value(s)
   at 0x...: rej_eta (poly.c:422)
   by 0x...: crypto_sign_dilithium5aes_ref_constbranchindex_poly_uniform_eta (poly.c:470)
   by 0x...: crypto_sign_dilithium5aes_ref_constbranchindex_polyvecl_uniform_eta (polyvec.c:40)
   by 0x...: crypto_sign_dilithium5aes_ref_constbranchindex_keypair (sign.c:42)
   by 0x...: test (try.c:128)
   by 0x...: main (try-anything.c:344)
 Uninitialised value was created by a client request
   at 0x...: randombytes_callback (try-anything.c:308)
   by 0x...: crypto_sign_dilithium5aes_ref_constbranchindex_keypair (sign.c:32)
   by 0x...: test (try.c:128)
   by 0x...: main (try-anything.c:344)

Conditional jump or move depends on uninitialised value(s)
   at 0x...: rej_eta (poly.c:426)
   by 0x...: crypto_sign_dilithium5aes_ref_constbranchindex_poly_uniform_eta (poly.c:470)
   by 0x...: crypto_sign_dilithium5aes_ref_constbranchindex_polyvecl_uniform_eta (polyvec.c:40)
   by 0x...: crypto_sign_dilithium5aes_ref_constbranchindex_keypair (sign.c:42)
   by 0x...: test (try.c:128)
   by 0x...: main (try-anything.c:344)
 Uninitialised value was created by a client request
   at 0x...: randombytes_callback (try-anything.c:308)
   by 0x...: crypto_sign_dilithium5aes_ref_constbranchindex_keypair (sign.c:32)
   by 0x...: test (try.c:128)
   by 0x...: main (try-anything.c:344)

Conditional jump or move depends on uninitialised value(s)
   at 0x...: rej_eta (poly.c:422)
   by 0x...: crypto_sign_dilithium5aes_ref_constbranchindex_poly_uniform_eta (poly.c:470)
   by 0x...: crypto_sign_dilithium5aes_ref_constbranchindex_polyveck_uniform_eta (polyvec.c:173)
   by 0x...: crypto_sign_dilithium5aes_ref_constbranchindex_keypair (sign.c:43)
   by 0x...: test (try.c:128)
   by 0x...: main (try-anything.c:344)
 Uninitialised value was created by a client request
   at 0x...: randombytes_callback (try-anything.c:308)
   by 0x...: crypto_sign_dilithium5aes_ref_constbranchindex_keypair (sign.c:32)
   by 0x...: test (try.c:128)
   by 0x...: main (try-anything.c:344)

Conditional jump or move depends on uninitialised value(s)
   at 0x...: rej_eta (poly.c:426)
   by 0x...: crypto_sign_dilithium5aes_ref_constbranchindex_poly_uniform_eta (poly.c:470)
   by 0x...: crypto_sign_dilithium5aes_ref_constbranchindex_polyveck_uniform_eta (polyvec.c:173)
   by 0x...: crypto_sign_dilithium5aes_ref_constbranchindex_keypair (sign.c:43)
   by 0x...: test (try.c:128)
   by 0x...: main (try-anything.c:344)
 Uninitialised value was created by a client request
   at 0x...: randombytes_callback (try-anything.c:308)
   by 0x...: crypto_sign_dilithium5aes_ref_constbranchindex_keypair (sign.c:32)
   by 0x...: test (try.c:128)
   by 0x...: main (try-anything.c:344)

vex: priv/host_arm64_defs.c:2832 (genSpill_ARM64): Assertion `offsetB < 4096' failed.
vex storage: T total 261395144 bytes allocated
vex storage: P total 0 bytes allocated
valgrind: the 'impossible' happened:
LibVEX called failure_exit().
host stacktrace:
   at 0x...: ??? (in /usr/libexec/valgrind/memcheck-arm64-linux)
   by 0x...: ??? (in /usr/libexec/valgrind/memcheck-arm64-linux)
   by 0x...: ??? (in /usr/libexec/valgrind/memcheck-arm64-linux)
   by 0x...: ??? (in /usr/libexec/valgrind/memcheck-arm64-linux)
   by 0x...: ??? (in /usr/libexec/valgrind/memcheck-arm64-linux)
   by 0x...: ??? (in /usr/libexec/valgrind/memcheck-arm64-linux)
   by 0x...: ??? (in /usr/libexec/valgrind/memcheck-arm64-linux)
   by 0x...: ??? (in /usr/libexec/valgrind/memcheck-arm64-linux)
   by 0x...: ??? (in /usr/libexec/valgrind/memcheck-arm64-linux)
   by 0x...: ??? (in /usr/libexec/valgrind/memcheck-arm64-linux)
   by 0x...: ??? (in /usr/libexec/valgrind/memcheck-arm64-linux)
   by 0x...: ??? (in /usr/libexec/valgrind/memcheck-arm64-linux)
   by 0x...: ??? (in /usr/libexec/valgrind/memcheck-arm64-linux)
   by 0x...: ??? (in /usr/libexec/valgrind/memcheck-arm64-linux)
   by 0x...: ???
sched status:
running_tid=1
Thread 1: status = VgTs_Runnable (lwpid 200279)
   at 0x...: crypto_sign_dilithium5aes_ref_constbranchindex_polyeta_pack (poly.c:555)
   by 0x...: crypto_sign_dilithium5aes_ref_constbranchindex_pack_sk (packing.c:88)
   by 0x...: crypto_sign_dilithium5aes_ref_constbranchindex_keypair (sign.c:62)
   by 0x...: test (try.c:128)
   by 0x...: main (try-anything.c:344)
client stack range: [0x1FFEFE7000 0x1FFF000FFF] client SP: 0x1FFEFE7EC0
valgrind stack range: [0x100929C000 0x100939BFFF] top usage: 20144 of 1048576
Note: see also the FAQ in the source distribution.
It contains workarounds to several common problems.
In particular, if Valgrind aborted or crashed after
identifying problems in your program, there's a good chance
that fixing those problems will prevent Valgrind aborting or
crashing, especially if it happened in m_mallocfree.c.
If that doesn't help, please report this bug to: www.valgrind.org
In the bug report, send all the above text, the valgrind
version, and what OS and version you are using.  Thanks.