anon_inode_create_getfd(9)

💖 anon_inode_create_getfd(9) 💖

okay so welcome to the Kernel API Manual page for anon_inode_create_getfd — manual name folded in like a cute little sticker 🎀. This one is lowkey the “new anon inode, who dis?” energy, and every detail is coming with us. no cap 💅

🌸 NAME 🌸

anon_inode_create_getfd — like anon_inode_getfd(), but it creates a new !S_PRIVATE anon inode instead of reusing the singleton anon inode, and it calls the inode_init_security_anon() LSM hook. periodt ✨

🦋 SYNOPSIS 🦋

int anon_inode_create_getfd (const char *name , const struct
       file_operations *fops , void *priv , int flags , const struct inode
       *context_inode );

🫶 ARGUMENTS 🫶

• name [in] — name of the "class" of the new file. yes bestie, that’s literally the label 🎀
• fops [in] — file operations for the new file.
• priv [in] — private data for the new file; it will be the file’s private_data.
• flags [in] — flags. iconic, no extra notes in the source 💅
• context_inode [in] — the logical relationship with the new inode; optional.

💜 DESCRIPTION 💜

Create a new anonymous inode and file pair. this can be done for two reasons:

• for the inode to have its own security context, so that LSMs can enforce policy on the inode's creation;
• if the caller needs a unique inode, for example in order to customize the size returned by fstat.

The LSM may use context_inode in inode_init_security_anon, but a reference to it is not held. like, do not assume you’re holding a ref, bestie — that is the whole note 😭

It returns a newly created file descriptor or an error code. slay when it works, error code when it doesn’t 🌈

🌟 SEE ALSO 🌟

• Kernel file ./fs/anon_inodes.c
• anon_inode_make_secure_inode(9)
• anon_inode_getfile(9)
• anon_inode_getfile_fmode(9)
• anon_inode_create_getfile(9)
• anon_inode_getfd(9)

mwah 💋 — this page is from ./fs, dated October 2026, and it’s the anon_inode_create_getfd(9) moment. byeeee 🦋