fs_context_for_submount(9)
okay bestie, welcome to fs_context_for_submount(9) from the Kernel API Manual β yes, that's the manual name, and yes, we're getting into it π
β¨
β¨ NAME β¨
fs_context_for_submount β allocate a new fs_context for a submount. that's the whole name situation, and it's literally exactly what it sounds like π«Ά
πΈ SYNOPSIS πΈ
struct fs_context * fs_context_for_submount (struct file_system_type
*type , struct dentry *reference );
π ARGUMENTS π
typeβfile_system_typeof the new context. it's giving "blueprint for the new context" energy πreferenceβ referencedentryfrom which to copy relevant info. this is the reference dentry, and the relevant info gets copied from it, no cap π¦
π DESCRIPTION π
okay so here's the vibe: this one allocates a new fs_context that's suitable for a submount. slay, iconic, periodt β¨
it also ensures that the fc->security object is inherited from reference β but only if needed, bestie. that's the important little detail, don't skip it π
π SEE ALSO π
like, go read these too, iykyk π
- Kernel file
./fs/fs_context.c vfs_parse_fs_param_source(9)vfs_parse_fs_param(9)vfs_parse_fs_qstr(9)vfs_parse_monolithic_sep(9)generic_parse_monolithic(9)alloc_fs_context(9)vfs_dup_fs_context(9)logfc(9)put_fs_context(9)
okay that's the page bestie! source/version: ./fs; date: October 2026; page: fs_context_for_submount(9) β mwah, signing off ππ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms