kernel/kcsan/.kunitconfig

File Facts

System

Linux kernel

Corpus path

kernel/kcsan/.kunitconfig

Extension

[no extension]

Size

798 bytes

Lines

25

Domain

Core OS

Bucket

Scheduler, Processes, Timers, Sync, And Syscalls

Inferred role

Core OS: Scheduler, Processes, Timers, Sync, And Syscalls

Status

atlas-only

Why This File Exists

Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.

• Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.

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

# Note that the KCSAN tests need to run on an SMP setup.
# Under kunit_tool, this can be done by using the --qemu_args
# option to configure a machine with several cores. For example:
# ./tools/testing/kunit/kunit.py run --kunitconfig=kernel/kcsan \
# 				 --arch=x86_64 --qemu_args="-smp 8"

CONFIG_KUNIT=y

CONFIG_DEBUG_KERNEL=y

# Need some level of concurrency to test a concurrency sanitizer.
CONFIG_SMP=y

CONFIG_KCSAN=y
CONFIG_KCSAN_KUNIT_TEST=y

# Set these if you want to run test_barrier_nothreads
#CONFIG_KCSAN_STRICT=y
#CONFIG_KCSAN_WEAK_MEMORY=y

# This prevents the test from timing out on many setups. Feel free to remove
# (or alter) this, in conjunction with setting a different test timeout with,
# for example, the --timeout kunit_tool option.
CONFIG_KCSAN_REPORT_ONCE_IN_MS=100

Annotation

• Atlas domain: Core OS / Scheduler, Processes, Timers, Sync, And Syscalls.
• 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.