put_binfmt_handler(9)

okay bestie, welcome to put_binfmt_handler(9) from the Kernel API Manual — the page about putting a binary handler entry, and it is lowkey all about cleanup 💅.

✨ NAME ✨

put_binfmt_handler — put binary handler entry 🎀

🦋 SYNOPSIS 🦋

void put_binfmt_handler (struct binfmt_misc_entry *e );

🌸 ARGUMENTS 🌸

• e — entry to put. That's the whole argument, fr fr. 🫶

💖 DESCRIPTION 💖

So the way that this works: it frees the entry while syncing with load_misc_binary, and it defers the final free to load_misc_binary in case that function is using the binary type handler we were requested to remove. No cap — the final free is handed off there, not just done and dusted on the spot.

It's also the teardown for a registration that fails before add_entry publishes the entry. So if registration doesn't make it out the door, this is the cleanup vibe check that handles it. 😭

🔥 SEE ALSO 🔥

• Kernel file ./fs/binfmt_misc.c
• struct binfmt_misc_flag(9)
• search_binfmt_handler(9)
• get_binfmt_handler(9)
• binfmt_misc_find_interp(9)
• entry_attach_interpreter(9)
• current_binfmt_misc(9)
• entry_select_interpreter(9)
• entry_invocation_flags(9)
• entry_open_interpreter(9)
• build_interp_argv(9)
• i_binfmt_misc(9)
• bm_evict_inode(9)
• unlink_binfmt_handler(9)
• remove_binfmt_handler(9)
• bm_unlink(9)
• bm_entry_add_interp(9)

made with 🫶 — source/version: ./fs, date: October 2026, manual: put_binfmt_handler(9) — bye bestie, slay your cleanup era 💅✨