All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: Nico Pache <npache@redhat.com>
To: linux-nfs@vger.kernel.org, kunit-dev@googlegroups.com
Subject: [BUG REPORT] not ok 1 Derive Kc subkey for camellia128-cts-cmac
Date: Thu,  7 Mar 2024 07:09:23 -0700	[thread overview]
Message-ID: <20240307140923.16598-1-npache@redhat.com> (raw)

Hi,

One of the RFC 6803 key derivation kunit subtests is failing.

cki-project data warehouse : https://datawarehouse.cki-project.org/issue/2514

Arches: X86_64, ARM64, S390x, ppc64le
First Appeared: ~6.8.rc2

TRACE:
# Subtest: RFC 6803 key derivation
    # RFC 6803 key derivation: ASSERTION FAILED at net/sunrpc/auth_gss/gss_krb5_test.c:63
    Expected err == 0, but
        err == -110 (0xffffffffffffff92)
        not ok 1 Derive Kc subkey for camellia128-cts-cmac
        ok 2 Derive Ke subkey for camellia128-cts-cmac
        ok 3 Derive Ki subkey for camellia128-cts-cmac
        ok 4 Derive Kc subkey for camellia256-cts-cmac
        ok 5 Derive Ke subkey for camellia256-cts-cmac
        ok 6 Derive Ki subkey for camellia256-cts-cmac
    # RFC 6803 key derivation: pass:5 fail:1 skip:0 total:6
    not ok 1 RFC 6803 key derivation
-- 
2.44.0


             reply	other threads:[~2024-03-07 14:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-07 14:09 Nico Pache [this message]
2024-03-19 17:51 ` [BUG REPORT] not ok 1 Derive Kc subkey for camellia128-cts-cmac Scott Mayhew
2024-03-20 20:16   ` Nico Pache
2024-03-21 14:24     ` Scott Mayhew
2024-03-21 14:32     ` [PATCH] kunit: bail out early in __kunit_test_suites_init() if there are no suites to test Scott Mayhew
2024-03-21 23:22       ` Rae Moar
2024-03-23  5:24       ` David Gow
2024-04-30 13:58         ` Scott Mayhew
2024-05-02  0:01           ` David Gow

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=20240307140923.16598-1-npache@redhat.com \
    --to=npache@redhat.com \
    --cc=kunit-dev@googlegroups.com \
    --cc=linux-nfs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.