tools/testing/selftests/static_keys/test_static_keys.sh

File Facts

System

Linux kernel

Corpus path

tools/testing/selftests/static_keys/test_static_keys.sh

Extension

.sh

Size

757 bytes

Lines

31

Domain

Support Tooling And Documentation

Bucket

tools

Inferred role

Support Tooling And Documentation: tools

Status

atlas-only

Why This File Exists

Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.

• Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.

Dependency Surface

• No C-style include directives detected by the generator.

Detected Declarations

• No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

#!/bin/sh
# SPDX-License-Identifier: GPL-2.0
# Runs static keys kernel module tests

# Kselftest framework requirement - SKIP code is 4.
ksft_skip=4

if ! /sbin/modprobe -q -n test_static_key_base; then
	echo "static_keys: module test_static_key_base is not found [SKIP]"
	exit $ksft_skip
fi

if ! /sbin/modprobe -q -n test_static_keys; then
	echo "static_keys: module test_static_keys is not found [SKIP]"
	exit $ksft_skip
fi

if /sbin/modprobe -q test_static_key_base; then
	if /sbin/modprobe -q test_static_keys; then
		echo "static_keys: ok"
		/sbin/modprobe -q -r test_static_keys
		/sbin/modprobe -q -r test_static_key_base
	else
		echo "static_keys: [FAIL]"
		/sbin/modprobe -q -r test_static_key_base
	fi
else
	echo "static_keys: [FAIL]"
	exit 1
fi

Annotation

• Atlas domain: Support Tooling And Documentation / tools.
• Implementation status: atlas-only.

Implementation Notes

• This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
• Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
• Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.