Confirmed to be fixed with the current SRU cycle's hirsute/linux kernel:

Before (5.11.0-24.25):
# #  RUN           tls.12_chacha.bidir ...
# # tls.c:845:bidir:Expected ret (-1) == 0 (0)
# # bidir: Test terminated by assertion
# #          FAIL  tls.12_chacha.bidir
# not ok 123 tls.12_chacha.bidir

Latest kernel (5.11.0-26.28):
# #  RUN           tls.12_chacha.bidir ...
# #            OK  tls.12_chacha.bidir
# ok 123 tls.12_chacha.bidir

** Tags removed: verification-needed-hirsute
** Tags added: verification-done-hirsute

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1933268

Title:
  net kselftest failures in the tls bidir test case

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Hirsute:
  Fix Committed

Bug description:
  [Impact]

  The tls bidir test from the network kselftests fails with the ChaCha
  cipher:

   #  RUN           tls.12_chacha.bidir ...
   # tls.c:845:bidir:Expected ret (-1) == 0 (0)
   # bidir: Test terminated by assertion
   #          FAIL  tls.12_chacha.bidir

  This is a problem with the test. The test fixture setup configures tls
  in one direction on the test socket pair according to the cipher being
  tested. The test case configures tls in the other direction, however
  it always configures for GCM regardless of the cipher being tested.
  When the test cipher is ChaCha the setsockopt() calls fail as the
  cipher is required to be the same in both directions.

  [Test Plan]

  Run the tls test from the net kselftests and confirm that the bidir
  test now passes when the test cipher is ChaCha.

  [Where problems could occur]

  This is a fix for a test case and should have no user impact. A
  serious problem in the test case might cause passing test cases to
  fail or prevent subsequent test cases from running. Any such issues
  should be caught during testing in -proposed before releasing kernels
  to users.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933268/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to