tools/testing/selftests/mm/mseal_helpers.h
Source file repositories/reference/linux-study-clean/tools/testing/selftests/mm/mseal_helpers.h
File Facts
- System
- Linux kernel
- Corpus path
tools/testing/selftests/mm/mseal_helpers.h- Extension
.h- Size
- 861 bytes
- Lines
- 42
- Domain
- Support Tooling And Documentation
- Bucket
- tools
- Inferred role
- Support Tooling And Documentation: implementation source
- Status
- source implementation candidate
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
if (!(test_passed)) { \
ksft_test_result_fail("%s: line:%d\n", \
__func__, __LINE__); \
return; \
} \
} while (0)
#define SKIP_TEST_IF_FALSE(test_passed) \
do { \
if (!(test_passed)) { \
ksft_test_result_skip("%s: line:%d\n", \
__func__, __LINE__); \
return; \
} \
} while (0)
#define REPORT_TEST_PASS() ksft_test_result_pass("%s\n", __func__)
#ifndef PKEY_DISABLE_ACCESS
#define PKEY_DISABLE_ACCESS 0x1
#endif
#ifndef PKEY_DISABLE_WRITE
#define PKEY_DISABLE_WRITE 0x2
#endif
#ifndef PKEY_BITS_PER_PKEY
#define PKEY_BITS_PER_PKEY 2
#endif
#ifndef PKEY_MASK
#define PKEY_MASK (PKEY_DISABLE_ACCESS | PKEY_DISABLE_WRITE)
#endif
#ifndef u64
#define u64 unsigned long long
#endif
Annotation
- Atlas domain: Support Tooling And Documentation / tools.
- Implementation status: source implementation candidate.
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.