[PATCH] fw_load0[12]: Skip on Lockdown and Secure Boot

Avinesh Kumar via ltp <[email protected]>
Newsgroups gmane.linux.ltp
Message-ID <[email protected]>
looks like these checks were lost in the recent commit converting
these tests to new API.

tst_module.c:139: TINFO: module signature enforcement: off
insmod: ERROR: could not insert module ltp_fw_load.ko: Key was rejected by service

Fixes: fd2c4d2c25d3 ("fw_load: rewrite test using new LTP API")
Signed-off-by: Avinesh Kumar <avinesh.kumar-IBi9RG/[email protected]>
---
 testcases/kernel/firmware/fw_load/fw_load01.c | 3 +++
 testcases/kernel/firmware/fw_load/fw_load02.c | 3 +++
 2 files changed, 6 insertions(+)

diff --git a/testcases/kernel/firmware/fw_load/fw_load01.c b/testcases/kernel/firmware/fw_load/fw_load01.c
index 4b30a3b40..c3d0c8c28 100644
--- a/testcases/kernel/firmware/fw_load/fw_load01.c
+++ b/testcases/kernel/firmware/fw_load/fw_load01.c
@@ -57,6 +57,9 @@ static void setup(void)
 		tst_brk(TCONF, "Skipping test due to read-only %s",
 			LIB_PATH);
 
+	if (tst_lockdown_enabled() > 0 || tst_secureboot_enabled() > 0)
+			tst_brk(TCONF, "Cannot load unsigned modules in Lockdown/Secure Boot");
+
 	tst_requires_module_signature_disabled();
 
 	snprintf(fw_size_param, sizeof(fw_size_param), "fw_size=%d", FW_SIZE);
diff --git a/testcases/kernel/firmware/fw_load/fw_load02.c b/testcases/kernel/firmware/fw_load/fw_load02.c
index 8d2063772..0a3a614d0 100644
--- a/testcases/kernel/firmware/fw_load/fw_load02.c
+++ b/testcases/kernel/firmware/fw_load/fw_load02.c
@@ -54,6 +54,9 @@ static void setup(void)
 	char fw_size_param[32];
 	char *tmpdir = tst_tmpdir_path();
 
+	if (tst_lockdown_enabled() > 0 || tst_secureboot_enabled() > 0)
+			tst_brk(TCONF, "Cannot load unsigned modules in Lockdown/Secure Boot");
+
 	tst_requires_module_signature_disabled();
 
 	SAFE_FILE_PRINTF(FW_PATH, "%s", tmpdir);
-- 
2.54.0


-- 
Mailing list info: https://lists.linux.it/listinfo/ltp
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.