drivers/usb/usbip/vudc_rx.c

File Facts

System

Linux kernel

Corpus path

drivers/usb/usbip/vudc_rx.c

Extension

.c

Size

5658 bytes

Lines

244

Domain

Driver Families

Bucket

drivers/usb

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

Dependency Surface

• net/sock.h
• linux/list.h
• linux/kthread.h
• usbip_common.h
• vudc.h

Detected Declarations

• function Copyright
• function v_recv_cmd_unlink
• function v_recv_cmd_submit
• function v_rx_pdu
• function v_rx_loop

Annotated Snippet

if (ret < 0) {
			pr_warn("v_rx exit with error %d", ret);
			break;
		}
	}
	return ret;
}

Annotation

• Immediate include surface: `net/sock.h`, `linux/list.h`, `linux/kthread.h`, `usbip_common.h`, `vudc.h`.
• Detected declarations: `function Copyright`, `function v_recv_cmd_unlink`, `function v_recv_cmd_submit`, `function v_rx_pdu`, `function v_rx_loop`.
• Atlas domain: Driver Families / drivers/usb.
• 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.