lib/is_single_threaded.c

File Facts

System

Linux kernel

Corpus path

lib/is_single_threaded.c

Extension

.c

Size

1202 bytes

Lines

55

Domain

Kernel Services

Bucket

lib

Inferred role

Kernel Services: implementation source

Status

source implementation candidate

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.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/sched/signal.h
• linux/sched/task.h
• linux/sched/mm.h

Detected Declarations

• function Copyright
• function for_each_thread

Annotated Snippet

for_each_thread(p, t) {
			if (unlikely(t->mm == mm))
				goto found;
			if (likely(t->mm))
				break;
			/*
			 * t->mm == NULL. Make sure next_thread/next_task
			 * will see other CLONE_VM tasks which might be
			 * forked before exiting.
			 */
			smp_rmb();
		}
	}
	ret = true;
found:
	rcu_read_unlock();

	return ret;
}

Annotation

• Immediate include surface: `linux/sched/signal.h`, `linux/sched/task.h`, `linux/sched/mm.h`.
• Detected declarations: `function Copyright`, `function for_each_thread`.
• Atlas domain: Kernel Services / lib.
• Implementation status: source implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.

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.