net/bluetooth/hidp/core.c

File Facts

System

Linux kernel

Corpus path

net/bluetooth/hidp/core.c

Extension

.c

Size

40595 bytes

Lines

1523

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.
• 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/kref.h
• linux/module.h
• linux/file.h
• linux/kthread.h
• linux/hidraw.h
• net/bluetooth/bluetooth.h
• net/bluetooth/hci_core.h
• net/bluetooth/l2cap.h
• hidp.h

Detected Declarations

• function hidp_copy_session
• function hidp_send_message
• function hidp_send_ctrl_message
• function hidp_send_intr_message
• function hidp_input_event
• function hidp_input_report
• function hidp_get_raw_report
• function hidp_set_raw_report
• function hidp_output_report
• function hidp_raw_request
• function hidp_idle_timeout
• function hidp_set_timer
• function hidp_del_timer
• function hidp_process_report
• function hidp_process_handshake
• function hidp_process_hid_control
• function hidp_process_data
• function hidp_recv_ctrl_frame
• function hidp_recv_intr_frame
• function hidp_send_frame
• function hidp_process_transmit
• function hidp_setup_input
• function hidp_open
• function hidp_close
• function hidp_start
• function hidp_stop
• function hidp_setup_hid
• function hidp_session_dev_init
• function hidp_session_dev_destroy
• function hidp_session_dev_add
• function hidp_session_dev_del
• function hidp_session_dev_work
• function hidp_session_new
• function hidp_session_get
• function session_free
• function hidp_session_put
• function list_for_each_entry
• function __hidp_session_find
• function hidp_session_new
• function hipd_session_stop_sync
• function hidp_session_terminate
• function hidp_session_probe
• function hidp_session_remove
• function l2cap_unregister_user
• function hidp_session_run
• function hidp_session_wake_function
• function hidp_session_run
• function hidp_verify_sockets

Annotated Snippet

module_init(hidp_init);
module_exit(hidp_exit);

MODULE_AUTHOR("Marcel Holtmann <marcel@holtmann.org>");
MODULE_AUTHOR("David Herrmann <dh.herrmann@gmail.com>");
MODULE_DESCRIPTION("Bluetooth HIDP ver " VERSION);
MODULE_VERSION(VERSION);
MODULE_LICENSE("GPL");
MODULE_ALIAS("bt-proto-6");

Annotation

• Immediate include surface: `linux/kref.h`, `linux/module.h`, `linux/file.h`, `linux/kthread.h`, `linux/hidraw.h`, `net/bluetooth/bluetooth.h`, `net/bluetooth/hci_core.h`, `net/bluetooth/l2cap.h`.
• Detected declarations: `function hidp_copy_session`, `function hidp_send_message`, `function hidp_send_ctrl_message`, `function hidp_send_intr_message`, `function hidp_input_event`, `function hidp_input_report`, `function hidp_get_raw_report`, `function hidp_set_raw_report`, `function hidp_output_report`, `function hidp_raw_request`.
• 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.