net/sunrpc/auth_gss/auth_gss.c
Source file repositories/reference/linux-study-clean/net/sunrpc/auth_gss/auth_gss.c
File Facts
- System
- Linux kernel
- Corpus path
net/sunrpc/auth_gss/auth_gss.c- Extension
.c- Size
- 58756 bytes
- Lines
- 2307
- 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/module.hlinux/init.hlinux/types.hlinux/slab.hlinux/sched.hlinux/pagemap.hlinux/sunrpc/clnt.hlinux/sunrpc/auth.hlinux/sunrpc/auth_gss.hlinux/sunrpc/gss_krb5.hlinux/sunrpc/svcauth_gss.hlinux/sunrpc/gss_err.hlinux/workqueue.hlinux/sunrpc/rpc_pipe_fs.hlinux/sunrpc/gss_api.hlinux/uaccess.hlinux/hashtable.hauth_gss_internal.h../netns.htrace/events/rpcgss.h
Detected Declarations
struct gss_pipestruct gss_authstruct gss_upcall_msgstruct gss_alloc_pdofunction gss_get_ctxfunction gss_put_ctxfunction gss_cred_set_ctxfunction gss_cred_get_ctxfunction gss_alloc_contextfunction gss_fill_contextfunction get_pipe_versionfunction put_pipe_versionfunction gss_release_msgfunction __gss_find_upcallfunction gss_add_msgfunction __gss_unhash_msgfunction gss_unhash_msgfunction gss_handle_downcall_resultfunction gss_upcall_callbackfunction gss_encode_v0_msgfunction gss_v0_upcallfunction gss_encode_v1_msgfunction gss_v1_upcallfunction gss_alloc_msgfunction gss_setup_upcallfunction warn_gssdfunction gss_refresh_upcallfunction gss_create_upcallfunction gss_find_downcallfunction gss_pipe_downcallfunction gss_pipe_openfunction gss_pipe_open_v0function gss_pipe_open_v1function gss_pipe_releasefunction gss_pipe_destroy_msgfunction gss_pipe_dentry_destroyfunction gss_pipe_dentry_createfunction gss_pipe_match_pdofunction __gss_pipe_freefunction __gss_pipe_releasefunction gss_pipe_freefunction flavorfunction gss_freefunction gss_free_callbackfunction gss_put_authfunction gss_destroyfunction gss_auth_find_or_add_hashedfunction gss_create_hashed
Annotated Snippet
module_init(init_rpcsec_gss)
module_exit(exit_rpcsec_gss)Annotation
- Immediate include surface: `linux/module.h`, `linux/init.h`, `linux/types.h`, `linux/slab.h`, `linux/sched.h`, `linux/pagemap.h`, `linux/sunrpc/clnt.h`, `linux/sunrpc/auth.h`.
- Detected declarations: `struct gss_pipe`, `struct gss_auth`, `struct gss_upcall_msg`, `struct gss_alloc_pdo`, `function gss_get_ctx`, `function gss_put_ctx`, `function gss_cred_set_ctx`, `function gss_cred_get_ctx`, `function gss_alloc_context`, `function gss_fill_context`.
- 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.