arch/s390/include/asm/arch-stackprotector.h

File Facts

System

Linux kernel

Corpus path

arch/s390/include/asm/arch-stackprotector.h

Extension

.h

Size

759 bytes

Lines

26

Domain

Architecture Layer

Bucket

arch/s390

Inferred role

Architecture Layer: implementation source

Status

source implementation candidate

Why This File Exists

CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.

• CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.

Dependency Surface

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

Detected Declarations

• function stack_protector_apply_early
• function stack_protector_apply

Annotated Snippet

#ifndef _ASM_S390_ARCH_STACKPROTECTOR_H
#define _ASM_S390_ARCH_STACKPROTECTOR_H

extern unsigned long __stack_chk_guard;
extern int stack_protector_debug;

void __stack_protector_apply_early(unsigned long kernel_start);
int __stack_protector_apply(unsigned long *start, unsigned long *end, unsigned long kernel_start);

static inline void stack_protector_apply_early(unsigned long kernel_start)
{
	if (IS_ENABLED(CONFIG_STACKPROTECTOR))
		__stack_protector_apply_early(kernel_start);
}

static inline int stack_protector_apply(unsigned long *start, unsigned long *end)
{
	if (IS_ENABLED(CONFIG_STACKPROTECTOR))
		return __stack_protector_apply(start, end, 0);
	return 0;
}

#endif /* _ASM_S390_ARCH_STACKPROTECTOR_H */

Annotation

• Detected declarations: `function stack_protector_apply_early`, `function stack_protector_apply`.
• Atlas domain: Architecture Layer / arch/s390.
• 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.