net/bluetooth/af_bluetooth.c

File Facts

System

Linux kernel

Corpus path

net/bluetooth/af_bluetooth.c

Extension

.c

Size

22402 bytes

Lines

1027

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.
• Touches IRQ or DMA behavior; this matters for the representative real-device path.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/module.h
• linux/debugfs.h
• linux/stringify.h
• linux/sched/signal.h
• asm/ioctls.h
• net/bluetooth/bluetooth.h
• linux/proc_fs.h
• linux/ethtool.h
• linux/sockios.h
• leds.h
• selftest.h

Detected Declarations

• function bt_sock_reclassify_lock
• function bt_sock_register
• function bt_sock_unregister
• function bt_sock_create
• function bt_sock_link
• function bt_sock_unlink
• function bt_sock_linked
• function sk_for_each
• function bt_accept_enqueue
• function bt_sk
• function bt_accept_unlink
• function bt_sock_recvmsg
• function bt_sock_data_wait
• function bt_sock_stream_recvmsg
• function skb_walk_frags
• function bt_accept_poll
• function bt_sock_poll
• function bt_ethtool_get_ts_info
• function bt_ethtool
• function bt_dev_ioctl
• function bt_sock_ioctl
• function bt_sock_wait_state
• function bt_sock_wait_ready
• function bt_seq_stop
• function bt_seq_show
• function bt_procfs_init
• function bt_procfs_cleanup
• function bt_procfs_init
• function bt_procfs_cleanup
• function __stringify
• function bt_exit
• module init bt_init
• export bt_sock_reclassify_lock
• export bt_sock_register
• export bt_sock_unregister
• export bt_sock_alloc
• export bt_sock_link
• export bt_sock_unlink
• export bt_sock_linked
• export bt_accept_enqueue
• export bt_accept_unlink
• export bt_accept_dequeue
• export bt_sock_recvmsg
• export bt_sock_stream_recvmsg
• export bt_sock_poll
• export bt_sock_ioctl
• export bt_sock_wait_state
• export bt_sock_wait_ready

Annotated Snippet

subsys_initcall(bt_init);
module_exit(bt_exit);

MODULE_AUTHOR("Marcel Holtmann <marcel@holtmann.org>");
MODULE_DESCRIPTION("Bluetooth Core ver " VERSION);
MODULE_VERSION(VERSION);
MODULE_LICENSE("GPL");
MODULE_ALIAS_NETPROTO(PF_BLUETOOTH);

Annotation

• Immediate include surface: `linux/module.h`, `linux/debugfs.h`, `linux/stringify.h`, `linux/sched/signal.h`, `asm/ioctls.h`, `net/bluetooth/bluetooth.h`, `linux/proc_fs.h`, `linux/ethtool.h`.
• Detected declarations: `function bt_sock_reclassify_lock`, `function bt_sock_register`, `function bt_sock_unregister`, `function bt_sock_create`, `function bt_sock_link`, `function bt_sock_unlink`, `function bt_sock_linked`, `function sk_for_each`, `function bt_accept_enqueue`, `function bt_sk`.
• 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.
• IRQ or DMA behavior appears here, which is relevant to the selected PCIe/NVMe device path.

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.