ima_post_path_mknod(9)

🌸 NAME 🌸

okay so bestie, welcome to ima_post_path_mknod(9) from the Kernel API Manual — this page is giving “one tiny job, done cute.” The function is ima_post_path_mknod, and its whole NAME flex is mark as a new inode. No cap, that’s the moment. ✨

✨ SYNOPSIS ✨

here’s the signature, copied exactly so u can trust it:

void ima_post_path_mknod (struct mnt_idmap *idmap , struct dentry
       *dentry );

🎀 ARGUMENTS 🎀

• idmap — idmap of the mount the inode was found from. That’s the context for where this inode came from.
• dentry — newly created dentry. Fresh dentry energy, literally.

🦋 DESCRIPTION 🦋

so the whole vibe is: mark files created via the mknodat syscall as new, so that the file data can be written later. that’s the job — mark it new now, write data later. slay. 💅

💜 SEE ALSO 💜

the page points u at this kernel file and a whole squad of API pages — collect them, bestie:

• Kernel file ./security/integrity/ima/ima_main.c
• ima_file_free(9)
• ima_file_mmap(9)
• ima_file_mprotect(9)
• ima_bprm_check(9)
• ima_creds_check(9)
• ima_bprm_creds_for_exec(9)
• ima_file_check(9)
• ima_file_hash(9)
• ima_inode_hash(9)
• ima_post_create_tmpfile(9)
• ima_read_file(9)
• ima_post_read_file(9)
• ima_load_data(9)
• ima_post_load_data(9)
• process_buffer_measurement(9)
• ima_kexec_cmdline(9)
• ima_measure_critical_data(9)
• ima_measure_raw_policy(9)
• ima_kernel_module_request(9)

xoxo, ur kernel bestie 🫶💖 — source/version: ./security/integrity/ima; date: October 2026; page: ima_post_path_mknod(9). periodt. 🎀