net/ceph/auth_x.h
Source file repositories/reference/linux-study-clean/net/ceph/auth_x.h
File Facts
- System
- Linux kernel
- Corpus path
net/ceph/auth_x.h- Extension
.h- Size
- 1013 bytes
- Lines
- 55
- 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/rbtree.hlinux/ceph/auth.hcrypto.hauth_x_protocol.h
Detected Declarations
struct ceph_x_ticket_handlerstruct ceph_x_authorizerstruct ceph_x_info
Annotated Snippet
struct ceph_x_ticket_handler {
struct rb_node node;
unsigned int service;
struct ceph_crypto_key session_key;
bool have_key;
u64 secret_id;
struct ceph_buffer *ticket_blob;
time64_t renew_after, expires;
};
#define CEPHX_AU_ENC_BUF_LEN 128 /* big enough for encrypted blob */
struct ceph_x_authorizer {
struct ceph_authorizer base;
struct ceph_crypto_key session_key;
struct ceph_buffer *buf;
unsigned int service;
u64 nonce;
u64 secret_id;
char enc_buf[CEPHX_AU_ENC_BUF_LEN] __aligned(8);
};
struct ceph_x_info {
struct ceph_crypto_key secret;
bool starting;
u64 server_challenge;
unsigned int have_keys;
struct rb_root ticket_handlers;
struct ceph_x_authorizer auth_authorizer;
};
int ceph_x_init(struct ceph_auth_client *ac);
#endif
Annotation
- Immediate include surface: `linux/rbtree.h`, `linux/ceph/auth.h`, `crypto.h`, `auth_x_protocol.h`.
- Detected declarations: `struct ceph_x_ticket_handler`, `struct ceph_x_authorizer`, `struct ceph_x_info`.
- 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.