tools/testing/selftests/powerpc/mm/stress_code_patching.sh
Source file repositories/reference/linux-study-clean/tools/testing/selftests/powerpc/mm/stress_code_patching.sh
File Facts
- System
- Linux kernel
- Corpus path
tools/testing/selftests/powerpc/mm/stress_code_patching.sh- Extension
.sh- Size
- 1062 bytes
- Lines
- 50
- 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/bash
# SPDX-License-Identifier: GPL-2.0-or-later
TIMEOUT=30
DEBUFS_DIR=`cat /proc/mounts | grep debugfs | awk '{print $2}'`
if [ ! -e "$DEBUFS_DIR" ]
then
echo "debugfs not found, skipping" 1>&2
exit 4
fi
if [ ! -e "$DEBUFS_DIR/tracing/current_tracer" ]
then
echo "Tracing files not found, skipping" 1>&2
exit 4
fi
echo "Testing for spurious faults when mapping kernel memory..."
if grep -q "FUNCTION TRACING IS CORRUPTED" "$DEBUFS_DIR/tracing/trace"
then
echo "FAILED: Ftrace already dead. Probably due to a spurious fault" 1>&2
exit 1
fi
dmesg -C
START_TIME=`date +%s`
END_TIME=`expr $START_TIME + $TIMEOUT`
while [ `date +%s` -lt $END_TIME ]
do
echo function > $DEBUFS_DIR/tracing/current_tracer
echo nop > $DEBUFS_DIR/tracing/current_tracer
if dmesg | grep -q 'ftrace bug'
then
break
fi
done
echo nop > $DEBUFS_DIR/tracing/current_tracer
if dmesg | grep -q 'ftrace bug'
then
echo "FAILED: Mapping kernel memory causes spurious faults" 1>&2
exit 1
else
echo "OK: Mapping kernel memory does not cause spurious faults"
exit 0
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.