inode_still_linked(9)

okay so bestie, this is the Kernel API Manual page for inode_still_linked(9) — manual name folded in near the top like a cute little bookmark 🎀. It’s giving very specific UBIFS replay energy, so let’s go 💅

🎀 NAME 🎀

inode_still_linked — check whether inode in question will be re-linked. That’s the vibe check, no cap 💅

✨ SYNOPSIS ✨

bool inode_still_linked (struct ubifs_info *c , struct replay_entry
       *rino );

🧚 ARGUMENTS 🧚

• c — UBIFS file-system description object. The fs lore, basically 🌸
• rino — replay entry to test. This is the entry under the microscope 🔍

🌸 DESCRIPTION 🌸

O_TMPFILE files can be re-linked, bestie — this means link count goes from 0 to 1 🔥. This case needs special care, otherwise all references to the inode will be removed upon the first replay entry of an inode with link count 0 is found. Like, that’s the whole dramatic stakes 😭

lowkey important: O_TMPFILE re-link means link count 0 → 1, and this is exactly the special-care case 💀 Don’t sleep on it.

🦋 SEE ALSO 🦋

Kernel file ./fs/ubifs/replay.c:

• struct replay_entry(9)
• struct bud_entry(9)
• set_bud_lprops(9)
• set_buds_lprops(9)
• trun_remove_range(9)
• apply_replay_entry(9)
• replay_entries_cmp(9)
• apply_replay_list(9)
• destroy_replay_list(9)
• insert_node(9)
• insert_dent(9)
• ubifs_validate_entry(9)
• is_last_bud(9)
• authenticate_sleb(9)
• replay_bud(9)
• replay_buds(9)
• destroy_bud_list(9)
• add_replay_bud(9)
• validate_ref(9)
• replay_log_leb(9)
• take_ihead(9)
• ubifs_replay_journal(9)

okay bestie, cute sign-off time: source/version is ./fs/ubifs, dated October 2026, and this was inode_still_linked(9) — periodt 💅💖