Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Paul Barker <paul@pbarker.dev>
To: Trevor Woerner <twoerner@gmail.com>,
	 openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v2 1/2] oeqa/sdk: update cryptodev to a revision that builds on kernel 6.18
Date: Sun, 16 Aug 2026 12:12:49 +0100	[thread overview]
Message-ID: <7fc0bf78c8046ad9c23e49f80d8ed93103db3317.camel@pbarker.dev> (raw)
In-Reply-To: <20260813030515.1028627-2-twoerner@gmail.com>

On Wed, 2026-08-12 at 23:05 -0400, Trevor Woerner wrote:
> The out-of-tree kernel module test pins a cryptodev-linux revision from
> before the 1.14 release, which predates the removal of
> crypto_ahash_alignmask() from the kernel and so no longer compiles:
> 
>   cryptlib.c:384:28: error: implicit declaration of function
>   'crypto_ahash_alignmask' [-Wimplicit-function-declaration]
> 
> Move to upstream's "Fix build for Linux 6.18-rc1", which is the revision
> that restores compatibility.
> 
> AI-Generated: codex/claude-opus 5 (xhigh)
> Signed-off-by: Trevor Woerner <twoerner@gmail.com>
> ---
> changes in v2:
> - none
> ---
>  meta/lib/oeqa/sdk/cases/kmod.py | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/meta/lib/oeqa/sdk/cases/kmod.py b/meta/lib/oeqa/sdk/cases/kmod.py
> index 0c4d8ddb543f..1be23e994fd2 100644
> --- a/meta/lib/oeqa/sdk/cases/kmod.py
> +++ b/meta/lib/oeqa/sdk/cases/kmod.py
> @@ -31,8 +31,8 @@ class KernelModuleTest(OESDKTestCase):
>  
>          with tempfile.TemporaryDirectory(prefix="cryptodev", dir=self.tc.sdk_dir) as testdir:
>              git_url = "https://github.com/cryptodev-linux/cryptodev-linux"
> -            # This is a knnown-good commit post-1.13 that builds with kernel 6.7+
> -            git_sha = "bb8bc7cf60d2c0b097c8b3b0e807f805b577a53f"
> +            # This is a known-good commit post-1.14 that builds with kernel 6.18+
> +            git_sha = "08644db02d43478f802755903212f5ee506af73b"
>  
>              sourcedir = os.path.join(testdir, "cryptodev-linux")
>              subprocess.check_output(["git", "clone", git_url, sourcedir], stderr=subprocess.STDOUT)

Hi Trevor,

I'm wondering why we haven't spotted this issue previously, we've been
using Linux 6.18 for months now. Are we missing a test case?

Best regards,

-- 
Paul Barker



  reply	other threads:[~2026-08-16 11:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-13  3:05 [PATCH v2 0/2] fix the SDK kernel module test Trevor Woerner
2026-08-13  3:05 ` [PATCH v2 1/2] oeqa/sdk: update cryptodev to a revision that builds on kernel 6.18 Trevor Woerner
2026-08-16 11:12   ` Paul Barker [this message]
2026-08-17 10:51     ` [OE-core] " Alexander Kanavin
2026-08-17 12:48       ` Richard Purdie
2026-08-22 15:00         ` Trevor Woerner
2026-08-22 14:52     ` Trevor Woerner
2026-08-24  7:26       ` Paul Barker
2026-08-13  3:05 ` [PATCH v2 2/2] oeqa/sdk: build the kernel's host tools with a host pkg-config Trevor Woerner

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=7fc0bf78c8046ad9c23e49f80d8ed93103db3317.camel@pbarker.dev \
    --to=paul@pbarker.dev \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=twoerner@gmail.com \
    /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