public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Hangbin Liu <liuhangbin@gmail.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org
Subject: [Need Help] tls selftest failed
Date: Fri, 18 Nov 2022 16:09:48 +0800	[thread overview]
Message-ID: <Y3c9zMbKsR+tcLHk@Laptop-X1> (raw)


Hi Jakub,

The RedHat CKI got failures when run the net/tls selftest on net-next 6.1.0-rc4
and mainline 6.1.0-rc5 kernel. Here is an example failure[1] with mainline
6.1.0-rc5 kernel[2]. The config link is here[3]. Would you please help
check if there is issue with the test? Please tell me if you can't
access the URLs, then I will attach the config file.

ok 200 tls.13_chacha.shutdown_unsent
#  RUN           tls.13_chacha.shutdown_reuse ...
#            OK  tls.13_chacha.shutdown_reuse
ok 201 tls.13_chacha.shutdown_reuse
#  RUN           tls.13_sm4_gcm.sendfile ...
# tls.c:323:sendfile:Expected ret (-1) == 0 (0)
# sendfile: Test terminated by assertion
#          FAIL  tls.13_sm4_gcm.sendfile
not ok 202 tls.13_sm4_gcm.sendfile
#  RUN           tls.13_sm4_gcm.send_then_sendfile ...
# tls.c:323:send_then_sendfile:Expected ret (-1) == 0 (0)
# send_then_sendfile: Test terminated by assertion
#          FAIL  tls.13_sm4_gcm.send_then_sendfile
not ok 203 tls.13_sm4_gcm.send_then_sendfile
#  RUN           tls.13_sm4_gcm.multi_chunk_sendfile ...
# tls.c:323:multi_chunk_sendfile:Expected ret (-1) == 0 (0)
# multi_chunk_sendfile: Test terminated by assertion
#          FAIL  tls.13_sm4_gcm.multi_chunk_sendfile
not ok 204 tls.13_sm4_gcm.multi_chunk_sendfile
#  RUN           tls.13_sm4_gcm.recv_max ...
# tls.c:323:recv_max:Expected ret (-1) == 0 (0)
# recv_max: Test terminated by assertion
#          FAIL  tls.13_sm4_gcm.recv_max
not ok 205 tls.13_sm4_gcm.recv_max
[...snip...]
not ok 298 tls.13_sm4_ccm.shutdown_unsent
#  RUN           tls.13_sm4_ccm.shutdown_reuse ...
# tls.c:323:shutdown_reuse:Expected ret (-1) == 0 (0)
# shutdown_reuse: Test terminated by assertion
#          FAIL  tls.13_sm4_ccm.shutdown_reuse
not ok 299 tls.13_sm4_ccm.shutdown_reuse
#  RUN           tls.12_aes_ccm.sendfile ...
#            OK  tls.12_aes_ccm.sendfile
ok 300 tls.12_aes_ccm.sendfile

[1] https://s3.amazonaws.com/arr-cki-prod-trusted-artifacts/trusted-artifacts/698017956/test%20x86_64%20debug/3340789088/artifacts/run.done.02/results_0001/RESULTS_J%3A7251979_0_R_12962453_T_38_test-kselftest/kselftests.6..82%20selftests%3A%20net%3Atls%20%5BFAIL%5D/resultoutputfile.log
[2] https://datawarehouse.cki-project.org/kcidb/checkouts/60286
[3] https://s3.amazonaws.com/arr-cki-prod-trusted-artifacts/index.html?prefix=trusted-artifacts/698017956/build%20x86_64%20debug/3340789060/artifacts/

Thanks
Hangbin

             reply	other threads:[~2022-11-18  8:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-18  8:09 Hangbin Liu [this message]
2022-11-18 16:13 ` [Need Help] tls selftest failed Jakub Kicinski
2022-11-20  3:17   ` Hangbin Liu
2022-11-21 17:33     ` Jakub Kicinski
2022-11-22  6:30       ` Hangbin Liu

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=Y3c9zMbKsR+tcLHk@Laptop-X1 \
    --to=liuhangbin@gmail.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.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