kernel/bpf/offload.c

File Facts

System

Linux kernel

Corpus path

kernel/bpf/offload.c

Extension

.c

Size

20279 bytes

Lines

867

Domain

Core OS

Bucket

Scheduler, Processes, Timers, Sync, And Syscalls

Inferred role

Core OS: exported/initcall integration point

Status

integration implementation candidate

Why This File Exists

Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.

• Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.
• 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.
• 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/bpf.h
• linux/bpf_verifier.h
• linux/bug.h
• linux/kdev_t.h
• linux/list.h
• linux/lockdep.h
• linux/netdevice.h
• linux/printk.h
• linux/proc_ns.h
• linux/rhashtable.h
• linux/rtnetlink.h
• linux/rwsem.h
• net/netdev_lock.h
• net/xdp.h

Detected Declarations

• struct bpf_offload_dev
• struct bpf_offload_netdev
• struct ns_get_path_bpf_prog_args
• struct ns_get_path_bpf_map_args
• function bpf_dev_offload_check
• function bpf_offload_find_netdev
• function __bpf_offload_dev_netdev_register
• function __bpf_prog_offload_destroy
• function bpf_map_offload_ndo
• function __bpf_map_offload_destroy
• function __bpf_offload_dev_netdev_unregister
• function __bpf_prog_dev_bound_init
• function bpf_prog_dev_bound_init
• function bpf_prog_dev_bound_inherit
• function bpf_prog_offload_verifier_prep
• function bpf_prog_offload_verify_insn
• function bpf_prog_offload_finalize
• function bpf_prog_offload_replace_insn
• function bpf_prog_offload_remove_insns
• function bpf_prog_dev_bound_destroy
• function bpf_prog_offload_translate
• function bpf_prog_warn_on_exec
• function bpf_prog_offload_compile
• function bpf_prog_offload_info_fill
• function bpf_map_offload_map_free
• function bpf_map_offload_map_mem_usage
• function bpf_map_offload_lookup_elem
• function bpf_map_offload_update_elem
• function bpf_map_offload_delete_elem
• function bpf_map_offload_get_next_key
• function bpf_map_offload_info_fill
• function __bpf_offload_dev_match
• function bpf_offload_dev_match
• function bpf_prog_dev_bound_match
• function bpf_offload_prog_map_match
• function bpf_offload_dev_netdev_register
• function bpf_offload_dev_netdev_unregister
• function bpf_offload_dev_create
• function bpf_offload_dev_destroy
• function bpf_dev_bound_netdev_unregister
• function bpf_dev_bound_kfunc_check
• function bpf_offload_init
• module init bpf_offload_init
• export bpf_offload_dev_match
• export bpf_offload_dev_netdev_register
• export bpf_offload_dev_netdev_unregister
• export bpf_offload_dev_create
• export bpf_offload_dev_destroy

Annotated Snippet

core_initcall(bpf_offload_init);

Annotation

• Immediate include surface: `linux/bpf.h`, `linux/bpf_verifier.h`, `linux/bug.h`, `linux/kdev_t.h`, `linux/list.h`, `linux/lockdep.h`, `linux/netdevice.h`, `linux/printk.h`.
• Detected declarations: `struct bpf_offload_dev`, `struct bpf_offload_netdev`, `struct ns_get_path_bpf_prog_args`, `struct ns_get_path_bpf_map_args`, `function bpf_dev_offload_check`, `function bpf_offload_find_netdev`, `function __bpf_offload_dev_netdev_register`, `function __bpf_prog_offload_destroy`, `function bpf_map_offload_ndo`, `function __bpf_map_offload_destroy`.
• Atlas domain: Core OS / Scheduler, Processes, Timers, Sync, And Syscalls.
• Implementation status: integration implementation candidate.
• This snippet crosses the user/kernel memory boundary; validate fault handling and access checks before translating the pattern.

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.