tools/testing/selftests/futex/functional/run.sh

File Facts

System

Linux kernel

Corpus path

tools/testing/selftests/futex/functional/run.sh

Extension

.sh

Size

983 bytes

Lines

54

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/sh
# SPDX-License-Identifier: GPL-2.0-or-later

###############################################################################
#
#   Copyright © International Business Machines  Corp., 2009
#
# DESCRIPTION
#      Run tests in the current directory.
#
# AUTHOR
#      Darren Hart <dvhart@linux.intel.com>
#
# HISTORY
#      2009-Nov-9: Initial version by Darren Hart <dvhart@linux.intel.com>
#      2010-Jan-6: Add futex_wait_uninitialized_heap and futex_wait_private_mapped_file
#                  by KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
#
###############################################################################

echo
./futex_requeue_pi

echo
./futex_requeue_pi_mismatched_ops

echo
./futex_requeue_pi_signal_restart

echo
./futex_wait_timeout

echo
./futex_wait_wouldblock

echo
./futex_wait_uninitialized_heap
./futex_wait_private_mapped_file

echo
./futex_wait

echo
./futex_requeue

echo
./futex_waitv

echo
./futex_priv_hash

echo
./futex_numa_mpol

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.