drivers/usb/mon/mon_stat.c

File Facts

System

Linux kernel

Corpus path

drivers/usb/mon/mon_stat.c

Extension

.c

Size

1579 bytes

Lines

71

Domain

Driver Families

Bucket

drivers/usb

Inferred role

Driver Families: operation-table or driver-model contract

Status

pattern 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 an operation table; this is where Linux turns generic core objects into subsystem-specific behavior.
• 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

• linux/kernel.h
• linux/slab.h
• linux/export.h
• linux/usb.h
• linux/fs.h
• linux/uaccess.h
• usb_mon.h

Detected Declarations

• struct snap
• function mon_stat_open
• function mon_stat_read
• function mon_stat_release

Annotated Snippet

const struct file_operations mon_fops_stat = {
	.owner =	THIS_MODULE,
	.open =		mon_stat_open,
	.read =		mon_stat_read,
	/* .write =	mon_stat_write, */
	/* .poll =		mon_stat_poll, */
	/* .unlocked_ioctl =	mon_stat_ioctl, */
	.release =	mon_stat_release,
};

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/slab.h`, `linux/export.h`, `linux/usb.h`, `linux/fs.h`, `linux/uaccess.h`, `usb_mon.h`.
• Detected declarations: `struct snap`, `function mon_stat_open`, `function mon_stat_read`, `function mon_stat_release`.
• Atlas domain: Driver Families / drivers/usb.
• Implementation status: pattern 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.