net/phonet/pep.c

File Facts

System

Linux kernel

Corpus path

net/phonet/pep.c

Extension

.c

Size

31256 bytes

Lines

1405

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.
• Touches user memory; correctness depends on fault-safe copying and privilege boundary handling.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/kernel.h
• linux/sched/signal.h
• linux/slab.h
• linux/socket.h
• net/sock.h
• net/tcp_states.h
• asm/ioctls.h
• linux/phonet.h
• linux/module.h
• net/phonet/phonet.h
• net/phonet/pep.h
• net/phonet/gprs.h

Detected Declarations

• function Copyright
• function pep_reply
• function pep_indicate
• function pipe_handler_request
• function pipe_handler_send_created_ind
• function pep_accept_conn
• function pep_reject_conn
• function pep_ctrlreq_error
• function pipe_snd_status
• function pipe_grant_credits
• function pipe_rcv_status
• function pipe_rcv_created
• function pipe_do_rcv
• function pipe_destruct
• function pipe_negotiate_fc
• function pep_connresp_rcv
• function pep_enableresp_rcv
• function pipe_start_flow_control
• function pipe_handler_do_rcv
• function sk_for_each
• function sock
• function pipe_do_remove
• function pep_sock_close
• function pep_sock_connect
• function pep_sock_enable
• function pep_first_packet_length
• function pep_ioctl
• function pep_init
• function pep_setsockopt
• function pep_getsockopt
• function pipe_skb_send
• function pep_sendmsg
• function pep_writeable
• function pep_write
• function pep_recvmsg
• function pep_sock_unhash
• function pep_register
• function pep_unregister
• module init pep_register

Annotated Snippet

module_init(pep_register);
module_exit(pep_unregister);
MODULE_AUTHOR("Remi Denis-Courmont, Nokia");
MODULE_DESCRIPTION("Phonet pipe protocol");
MODULE_LICENSE("GPL");
MODULE_ALIAS_NET_PF_PROTO(PF_PHONET, PN_PROTO_PIPE);

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/sched/signal.h`, `linux/slab.h`, `linux/socket.h`, `net/sock.h`, `net/tcp_states.h`, `asm/ioctls.h`, `linux/phonet.h`.
• Detected declarations: `function Copyright`, `function pep_reply`, `function pep_indicate`, `function pipe_handler_request`, `function pipe_handler_send_created_ind`, `function pep_accept_conn`, `function pep_reject_conn`, `function pep_ctrlreq_error`, `function pipe_snd_status`, `function pipe_grant_credits`.
• Atlas domain: Networking Core / Sockets, Protocols, Packet Path, And Network Policy.
• Implementation status: integration implementation candidate.
• This snippet crosses the user/kernel memory boundary; validate fault handling and access checks before translating the pattern.
• 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.