net/mac80211/wep.c

File Facts

System

Linux kernel

Corpus path

net/mac80211/wep.c

Extension

.c

Size

8541 bytes

Lines

308

Domain

Networking Core

Bucket

Sockets, Protocols, Packet Path, And Network Policy

Inferred role

Networking Core: implementation source

Status

source 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.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/netdevice.h
• linux/types.h
• linux/random.h
• linux/compiler.h
• linux/crc32.h
• linux/crypto.h
• linux/err.h
• linux/mm.h
• linux/scatterlist.h
• linux/slab.h
• linux/unaligned.h
• net/mac80211.h
• ieee80211_i.h
• wep.h

Detected Declarations

• function Copyright
• function ieee80211_wep_weak_iv
• function ieee80211_wep_get_iv
• function ieee80211_wep_remove_iv
• function ieee80211_wep_encrypt_data
• function space
• function ieee80211_wep_decrypt_data
• function ICV
• function ieee80211_crypto_wep_decrypt
• function wep_encrypt_skb
• function ieee80211_crypto_wep_encrypt
• function skb_queue_walk

Annotated Snippet

if (wep_encrypt_skb(tx, skb) < 0) {
			I802_DEBUG_INC(tx->local->tx_handlers_drop_wep);
			return TX_DROP;
		}
	}

	return TX_CONTINUE;
}

Annotation

• Immediate include surface: `linux/netdevice.h`, `linux/types.h`, `linux/random.h`, `linux/compiler.h`, `linux/crc32.h`, `linux/crypto.h`, `linux/err.h`, `linux/mm.h`.
• Detected declarations: `function Copyright`, `function ieee80211_wep_weak_iv`, `function ieee80211_wep_get_iv`, `function ieee80211_wep_remove_iv`, `function ieee80211_wep_encrypt_data`, `function space`, `function ieee80211_wep_decrypt_data`, `function ICV`, `function ieee80211_crypto_wep_decrypt`, `function wep_encrypt_skb`.
• Atlas domain: Networking Core / Sockets, Protocols, Packet Path, And Network Policy.
• Implementation status: source implementation candidate.

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.