From: Wake Liu via ltp <ltp@lists.linux.it>
To: Li Wang <li.wang@linux.dev>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v4 4/4] testcases: drop manual tst_modprobe() now handled by tst_kconfig
Date: Wed, 14 Oct 2026 09:31:55 +0000 [thread overview]
Message-ID: <20261014-keyctl23-tst-modprobe-1-wakel@google.com> (raw)
In-Reply-To: <20261014061202.56362-5-li.wang@linux.dev>
Hi Li,
> Drop the explicit tst_modprobe() calls, and the now unused
> tst_module.h includes, from:
>
> - cve-2026-46331.c: sch_ingress, cls_matchall, act_pedit
> - sctphantom.c: sctp
> - keyctl29.c: x509_key_parser
> - keyctl30.c: pkcs8_key_parser
Could you please drop the tst_modprobe() call from keyctl23.c in this
patch as well?
keyctl23 still calls tst_modprobe("x509_key_parser", NULL) in setup(),
but it requires CONFIG_X509_CERTIFICATE_PARSER=y, so the parser is
always built in and there is nothing to load. With the call gone, the
tst_module.h include and the "Requires root (CAP_SYS_MODULE) to load
the x509_key_parser module" line in the doc comment can go as well.
On most distributions the call is harmless, since modprobe returns 0
for built-in modules, but on Android it breaks the test. Without -d,
Android's modprobe scans /lib/modules/, which does not exist on Android
devices, so it always fails and tst_modprobe() turns that into TBROK:
modprobe: Failed to scan dir /lib/modules/: No such file or directory
lib/tst_cmd.c:114: TBROK: 'modprobe' exited with a non-zero code 1
keyctl29 fails the same way today, and this series fixes it since
modprobe is no longer called when the parser is built in. With keyctl23
covered too, we can re-enable both tests in Android VTS. If you would
rather keep this series as is, I can send a separate patch for keyctl23.
Thanks,
Wake
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2026-10-14 9:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 6:11 [LTP] [PATCH v4 0/4] tst_kconfig: automatic module load/unload for CONFIG_*=m Li Wang
2026-10-14 6:11 ` [LTP] [PATCH v4 1/4] lib: add module is loaded check Li Wang
2026-10-14 7:41 ` [LTP] " linuxtestproject.agent
2026-10-14 6:12 ` [LTP] [PATCH v4 2/4] tst_kconfig: load and unload kernel modules for CONFIG_*=m Li Wang
2026-10-14 6:12 ` [LTP] [PATCH v4 3/4] tst_kconfig: add module mappings for vsock/vsock_loopback Li Wang
2026-10-14 6:12 ` [LTP] [PATCH v4 4/4] testcases: drop manual tst_modprobe() now handled by tst_kconfig Li Wang
2026-10-14 9:31 ` Wake Liu via ltp [this message]
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=20261014-keyctl23-tst-modprobe-1-wakel@google.com \
--to=ltp@lists.linux.it \
--cc=li.wang@linux.dev \
--cc=wakel@google.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