net/vmw_vsock/virtio_transport.c

File Facts

System

Linux kernel

Corpus path

net/vmw_vsock/virtio_transport.c

Extension

.c

Size

24917 bytes

Lines

988

Domain

Networking Core

Bucket

Sockets, Protocols, Packet Path, And Network Policy

Inferred role

Networking Core: exported/initcall integration point

Status

integration implementation candidate

Why This File Exists

Networking stack implementation surface: socket APIs, protocol dispatch, packet flow, routing, filtering, and network namespaces.

• Networking stack implementation surface: socket APIs, protocol dispatch, packet flow, routing, filtering, and network namespaces.
• Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
• 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

• linux/spinlock.h
• linux/module.h
• linux/list.h
• linux/atomic.h
• linux/virtio.h
• linux/virtio_ids.h
• linux/virtio_config.h
• linux/virtio_vsock.h
• linux/dma-mapping.h
• net/sock.h
• linux/mutex.h
• net/af_vsock.h

Detected Declarations

• struct virtio_vsock
• function virtio_transport_get_local_cid
• function virtio_transport_send_skb
• function virtio_transport_send_pkt_work
• function virtio_transport_send_skb_fast_path
• function virtio_transport_send_pkt
• function and
• function virtio_transport_cancel_pkt
• function virtio_vsock_rx_fill
• function virtio_transport_tx_work
• function virtio_transport_more_replies
• function virtio_vsock_event_fill_one
• function virtio_vsock_event_fill
• function virtio_vsock_reset_sock
• function virtio_vsock_update_guest_cid
• function virtio_vsock_event_handle
• function virtio_transport_event_work
• function virtio_vsock_event_done
• function virtio_vsock_tx_done
• function virtio_vsock_rx_done
• function virtio_transport_can_msgzerocopy
• function virtio_transport_msgzerocopy_allow
• function virtio_transport_stream_allow
• function virtio_transport_has_remote_cid
• function virtio_transport_seqpacket_allow
• function virtio_transport_rx_work
• function virtio_vsock_vqs_init
• function virtio_vsock_vqs_start
• function virtio_vsock_vqs_del
• function virtio_vsock_probe
• function lockdep_is_held
• function virtio_vsock_remove
• function virtio_vsock_freeze
• function virtio_vsock_restore
• function lockdep_is_held
• function virtio_vsock_init
• function virtio_vsock_exit
• module init virtio_vsock_init

Annotated Snippet

module_init(virtio_vsock_init);
module_exit(virtio_vsock_exit);
MODULE_LICENSE("GPL v2");
MODULE_AUTHOR("Asias He");
MODULE_DESCRIPTION("virtio transport for vsock");
MODULE_DEVICE_TABLE(virtio, id_table);

Annotation

• Immediate include surface: `linux/spinlock.h`, `linux/module.h`, `linux/list.h`, `linux/atomic.h`, `linux/virtio.h`, `linux/virtio_ids.h`, `linux/virtio_config.h`, `linux/virtio_vsock.h`.
• Detected declarations: `struct virtio_vsock`, `function virtio_transport_get_local_cid`, `function virtio_transport_send_skb`, `function virtio_transport_send_pkt_work`, `function virtio_transport_send_skb_fast_path`, `function virtio_transport_send_pkt`, `function and`, `function virtio_transport_cancel_pkt`, `function virtio_vsock_rx_fill`, `function virtio_transport_tx_work`.
• Atlas domain: Networking Core / Sockets, Protocols, Packet Path, And Network Policy.
• Implementation status: integration 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.