lib/kunit/try-catch.c

File Facts

System

Linux kernel

Corpus path

lib/kunit/try-catch.c

Extension

.c

Size

2456 bytes

Lines

92

Domain

Kernel Services

Bucket

lib

Inferred role

Kernel Services: exported/initcall integration point

Status

integration 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.
• Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• kunit/test.h
• linux/completion.h
• linux/kernel.h
• linux/kthread.h
• linux/sched/task.h
• try-catch-impl.h

Detected Declarations

• function Copyright
• function kunit_generic_run_threadfn_adapter
• function kunit_try_catch_run
• export kunit_try_catch_throw
• export kunit_try_catch_run

Annotated Snippet

else if (exit_code == -EINTR) {
		if (test->last_seen.file)
			kunit_err(test, "try faulted: last line seen %s:%d\n",
				  test->last_seen.file, test->last_seen.line);
		else
			kunit_err(test, "try faulted\n");
	} else if (exit_code == -ETIMEDOUT)
		kunit_err(test, "try timed out\n");
	else if (exit_code)
		kunit_err(test, "Unknown error: %d\n", exit_code);

	try_catch->catch(try_catch->context);
}
EXPORT_SYMBOL_GPL(kunit_try_catch_run);

Annotation

• Immediate include surface: `kunit/test.h`, `linux/completion.h`, `linux/kernel.h`, `linux/kthread.h`, `linux/sched/task.h`, `try-catch-impl.h`.
• Detected declarations: `function Copyright`, `function kunit_generic_run_threadfn_adapter`, `function kunit_try_catch_run`, `export kunit_try_catch_throw`, `export kunit_try_catch_run`.
• Atlas domain: Kernel Services / lib.
• Implementation status: integration implementation candidate.

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.