drivers/gpu/drm/i915/i915_user_extensions.c

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/i915/i915_user_extensions.c

Extension

.c

Size

1125 bytes

Lines

62

Domain

Driver Families

Bucket

drivers/gpu

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.
• Touches user memory; correctness depends on fault-safe copying and privilege boundary handling.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/nospec.h
• linux/sched/signal.h
• linux/uaccess.h
• uapi/drm/i915_drm.h
• i915_user_extensions.h
• i915_utils.h

Detected Declarations

• function i915_user_extensions

Annotated Snippet

if (name < count) {
			name = array_index_nospec(name, count);
			if (tbl[name])
				err = tbl[name](ext, data);
		}
		if (err)
			return err;

		if (get_user(next, &ext->next_extension) ||
		    overflows_type(next, uintptr_t))
			return -EFAULT;

		ext = u64_to_user_ptr(next);
	}

	return 0;
}

Annotation

• Immediate include surface: `linux/nospec.h`, `linux/sched/signal.h`, `linux/uaccess.h`, `uapi/drm/i915_drm.h`, `i915_user_extensions.h`, `i915_utils.h`.
• Detected declarations: `function i915_user_extensions`.
• Atlas domain: Driver Families / drivers/gpu.
• Implementation status: source implementation candidate.
• This snippet crosses the user/kernel memory boundary; validate fault handling and access checks before translating the pattern.

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.