From: Cyril Hrubis <chrubis@suse.cz>
To: Petr Vorel <pvorel@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 1/1] keyctl30: Check module is presented before loading
Date: Tue, 22 Sep 2026 13:09:58 +0200 [thread overview]
Message-ID: <arJiBgKNC80acBfY@yuki.lan> (raw)
In-Reply-To: <20260922105840.2193537-1-pvorel@suse.cz>
Hi!
> This fixes test on the system without module:
>
> modprobe: FATAL: Module pkcs8_key_parser not found in directory /usr/lib/modules/6.12.0-160100.5-azure
> tst_cmd.c:112: TBROK: 'modprobe' exited with a non-zero code 1 at tst_cmd.c:112
>
> With the fix it TCONF as expected:
>
> tst_module.c:72: TCONF: Failed to find module 'pkcs8_key_parser'
>
> Fixes: 1bb448ed9e ("keyctl30: Test KEYCTL_PKEY_QUERY on private key")
> Signed-off-by: Petr Vorel <pvorel@suse.cz>
> ---
> FYI Cyril suggested to add into struct config_module_map:
>
> {"CONFIG_NET_SCH_INGRESS", "sch_ingress"},
> {"CONFIG_NET_CLS_MATCHALL", "cls_matchall"},
> {"CONFIG_NET_ACT_PEDIT", "act_pedit"},
> + {"CONFIG_PKCS8_PRIVATE_KEY_PARSER", "pcks8_key_parser"},
I think that this is still cleaner, this way we skip the test even
before we start running it. Maybe we should attempt to auto-generate the
table for all CONFIG_* variables used in LTP.
Also keyctl23.c and keyctl29.c have tst_modprobe("x509_key_parser",
NULL); So we need fix/mappping for x509_key_parser too.
> Although it does not harm this is IMHO just wrong function being used.
That depends, if we decide to have the checks in the tst_kconfig.c then
tst_modprobe() is the only function that should be used.
Also looiks like the primary user of the tst_module_load() are tests
that build modules in LTP tree, where it does make sense, since these
may fail to build and be missing and there are no CONFIG_ variables for
these. The rest of the tests seems to be using tst_modprobe().
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-09-22 11:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 10:58 [LTP] [PATCH 1/1] keyctl30: Check module is presented before loading Petr Vorel
2026-09-22 11:05 ` Petr Vorel
2026-09-22 11:09 ` Cyril Hrubis [this message]
2026-09-22 11:29 ` Petr Vorel
2026-09-22 12:50 ` Cyril Hrubis
2026-09-22 13:50 ` Petr Vorel
2026-09-22 14:17 ` Cyril Hrubis
2026-09-22 16:41 ` Petr Vorel
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=arJiBgKNC80acBfY@yuki.lan \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
--cc=pvorel@suse.cz \
/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.