drivers/net/netconsole.c

File Facts

System

Linux kernel

Corpus path

drivers/net/netconsole.c

Extension

.c

Size

66230 bytes

Lines

2498

Domain

Driver Families

Bucket

drivers/net

Inferred role

Driver Families: exported/initcall integration point

Status

integration 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.
• 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.
• Touches IRQ or DMA behavior; this matters for the representative real-device path.
• 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/mm.h
• linux/init.h
• linux/module.h
• linux/slab.h
• linux/console.h
• linux/moduleparam.h
• linux/kernel.h
• linux/string.h
• linux/ip.h
• linux/ipv6.h
• linux/udp.h
• linux/netpoll.h
• linux/inet.h
• linux/unaligned.h
• net/ip6_checksum.h
• linux/configfs.h
• linux/etherdevice.h
• linux/hex.h
• linux/u64_stats_sync.h
• linux/utsname.h
• linux/rtnetlink.h
• linux/workqueue.h

Detected Declarations

• struct netconsole_target_stats
• struct netconsole_target
• struct userdatum
• struct userdata
• enum console_type
• enum sysdata_feature
• enum target_state
• function option_setup
• function dynamic_netconsole_init
• function dynamic_netconsole_exit
• function hierarchy
• function netconsole_target_put
• function dynamic_netconsole_mutex_lock
• function dynamic_netconsole_mutex_unlock
• function dynamic_netconsole_init
• function dynamic_netconsole_exit
• function netcons_release_dev
• function resume_target
• function deactivated_target_match
• function process_resume_target
• function netconsole_process_cleanups_core
• function netconsole_print_banner
• function netpoll_parse_ip_addr
• function netconsole_process_cleanups
• function trim_newline
• function enabled_show
• function extended_show
• function release_show
• function dev_name_show
• function local_port_show
• function remote_port_show
• function local_ip_show
• function remote_ip_show
• function local_mac_show
• function remote_mac_show
• function transmit_errors_show
• function sysdata_cpu_nr_enabled_show
• function sysdata_taskname_enabled_show
• function sysdata_release_enabled_show
• function unregister_netcons_consoles
• function sysdata_msgid_enabled_show
• function enabled
• function release_store
• function extended_store
• function dev_name_store
• function local_port_store
• function remote_port_store
• function local_ip_store

Annotated Snippet

* late_initcall() and module_init() are identical if built as module.
 */
late_initcall(init_netconsole);
module_exit(cleanup_netconsole);

Annotation

• Immediate include surface: `linux/mm.h`, `linux/init.h`, `linux/module.h`, `linux/slab.h`, `linux/console.h`, `linux/moduleparam.h`, `linux/kernel.h`, `linux/string.h`.
• Detected declarations: `struct netconsole_target_stats`, `struct netconsole_target`, `struct userdatum`, `struct userdata`, `enum console_type`, `enum sysdata_feature`, `enum target_state`, `function option_setup`, `function dynamic_netconsole_init`, `function dynamic_netconsole_exit`.
• Atlas domain: Driver Families / drivers/net.
• Implementation status: integration implementation candidate.
• 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.