lib/test_fortify/Makefile

File Facts

System

Linux kernel

Corpus path

lib/test_fortify/Makefile

Extension

[no extension]

Size

800 bytes

Lines

26

Domain

Kernel Services

Bucket

lib

Inferred role

Kernel Services: build/configuration rule

Status

atlas-only

Why This File Exists

Shared kernel service surface used by multiple subsystems, including helpers, cryptography, virtualization support, and async I/O infrastructure.

• Shared kernel service surface used by multiple subsystems, including helpers, cryptography, virtualization support, and async I/O infrastructure.

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

# SPDX-License-Identifier: GPL-2.0

ccflags-y := $(call cc-disable-warning,fortify-source)

quiet_cmd_test_fortify = TEST    $@
      cmd_test_fortify = $(CONFIG_SHELL) $(src)/test_fortify.sh \
			$< $@ "$(NM)" $(CC) $(c_flags) -DKBUILD_EXTRA_WARN1

$(obj)/%.log: $(src)/%.c $(src)/test_fortify.sh FORCE
	$(call if_changed_dep,test_fortify)

logs = $(patsubst $(src)/%.c, %.log, $(wildcard $(src)/*-*.c))
targets += $(logs)

quiet_cmd_gen_fortify_log = CAT     $@
      cmd_gen_fortify_log = cat $(or $(real-prereqs),/dev/null) > $@

$(obj)/test_fortify.log: $(addprefix $(obj)/, $(logs)) FORCE
	$(call if_changed,gen_fortify_log)

always-y += test_fortify.log

# Some architectures define __NO_FORTIFY if __SANITIZE_ADDRESS__ is undefined.
# Pass CFLAGS_KASAN to avoid warnings.
KASAN_SANITIZE := y

Annotation

• Atlas domain: Kernel Services / lib.
• 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.