drivers/acpi/acpica/utalloc.c

File Facts

System

Linux kernel

Corpus path

drivers/acpi/acpica/utalloc.c

Extension

.c

Size

8905 bytes

Lines

358

Domain

Driver Families

Bucket

drivers/acpi

Inferred role

Driver Families: implementation source

Status

source implementation candidate

Why This File Exists

Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.

• Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• acpi/acpi.h
• accommon.h
• acdebug.h

Detected Declarations

• function Copyright
• function acpi_ut_create_caches
• function acpi_ut_delete_caches
• function acpi_ut_validate_buffer
• function acpi_ut_initialize_buffer

Annotated Snippet

if (input_buffer_length < required_length) {
			return (AE_BUFFER_OVERFLOW);
		}
		break;
	}

	/* Validate allocation from above or input buffer pointer */

	if (!buffer->pointer) {
		return (AE_NO_MEMORY);
	}

	/* Have a valid buffer, clear it */

	memset(buffer->pointer, 0, required_length);
	return (AE_OK);
}

Annotation

• Immediate include surface: `acpi/acpi.h`, `accommon.h`, `acdebug.h`.
• Detected declarations: `function Copyright`, `function acpi_ut_create_caches`, `function acpi_ut_delete_caches`, `function acpi_ut_validate_buffer`, `function acpi_ut_initialize_buffer`.
• Atlas domain: Driver Families / drivers/acpi.
• Implementation status: source 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.