fs/smb/server/misc.h

File Facts

System

Linux kernel

Corpus path

fs/smb/server/misc.h

Extension

.h

Size

2068 bytes

Lines

67

Domain

Core OS

Bucket

VFS And Filesystem Core

Inferred role

Core OS: implementation source

Status

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

Dependency Surface

• linux/proc_fs.h

Detected Declarations

• struct ksmbd_share_config
• struct nls_table
• struct kstat
• struct ksmbd_file
• struct ksmbd_dir_info
• struct ksmbd_const_name
• function ksmbd_proc_init

Annotated Snippet

struct ksmbd_const_name {
	unsigned int const_value;
	const char *name;
};

void ksmbd_proc_init(void);
void ksmbd_proc_cleanup(void);
void ksmbd_proc_reset(void);
struct proc_dir_entry *ksmbd_proc_create(const char *name,
					 int (*show)(struct seq_file *m, void *v),
			     void *v);
void ksmbd_proc_show_flag_names(struct seq_file *m,
				const struct ksmbd_const_name *table,
				int count,
				unsigned int flags);
void ksmbd_proc_show_const_name(struct seq_file *m,
				const char *format,
				const struct ksmbd_const_name *table,
				int count,
				unsigned int const_value);
#else
static inline void ksmbd_proc_init(void) {}
static inline void ksmbd_proc_cleanup(void) {}
static inline void ksmbd_proc_reset(void) {}
#endif
#endif /* __KSMBD_MISC_H__ */

Annotation

• Immediate include surface: `linux/proc_fs.h`.
• Detected declarations: `struct ksmbd_share_config`, `struct nls_table`, `struct kstat`, `struct ksmbd_file`, `struct ksmbd_dir_info`, `struct ksmbd_const_name`, `function ksmbd_proc_init`.
• Atlas domain: Core OS / VFS And Filesystem Core.
• 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.