fs/smb/client/cifs_spnego_negtokeninit.asn1
Source file repositories/reference/linux-study-clean/fs/smb/client/cifs_spnego_negtokeninit.asn1
File Facts
- System
- Linux kernel
- Corpus path
fs/smb/client/cifs_spnego_negtokeninit.asn1- Extension
.asn1- Size
- 698 bytes
- Lines
- 41
- Domain
- Core OS
- Bucket
- VFS And Filesystem Core
- Inferred role
- Core OS: VFS And Filesystem Core
- Status
- atlas-only
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.
Dependency Surface
- No C-style include directives detected by the generator.
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
GSSAPI ::=
[APPLICATION 0] IMPLICIT SEQUENCE {
thisMech
OBJECT IDENTIFIER ({cifs_gssapi_this_mech}),
negotiationToken
NegotiationToken
}
MechType ::= OBJECT IDENTIFIER ({cifs_neg_token_init_mech_type})
MechTypeList ::= SEQUENCE OF MechType
NegHints ::= SEQUENCE {
hintName
[0] GeneralString OPTIONAL,
hintAddress
[1] OCTET STRING OPTIONAL
}
NegTokenInit2 ::=
SEQUENCE {
mechTypes
[0] MechTypeList OPTIONAL,
reqFlags
[1] BIT STRING OPTIONAL,
mechToken
[2] OCTET STRING OPTIONAL,
negHints
[3] NegHints OPTIONAL,
mechListMIC
[3] OCTET STRING OPTIONAL
}
NegotiationToken ::=
CHOICE {
negTokenInit
[0] NegTokenInit2,
negTokenTarg
[1] ANY
}
Annotation
- Atlas domain: Core OS / VFS And Filesystem Core.
- Implementation status: atlas-only.
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.