simple_offset_rename(9)

🦋 NAME 🦋

okay so bestie, this is simple_offset_rename(9) from the Kernel API Manual — and it handles directory offsets for rename. that's the vibe ✨

🌸 SYNOPSIS 🌸

here's the exact signature, no cap:

void simple_offset_rename (struct inode *old_dir , struct dentry
       *old_dentry , struct inode *new_dir , struct dentry *new_dentry );

it returns void, so like, no return-value drama 💅

🎀 ARGUMENTS 🎀

• old_dir — parent directory of source entry 💖
• old_dentry — dentry of source entry 🫶
• new_dir — parent_directory of destination entry 🌸
• new_dentry — dentry of destination 🦋

🔥 DESCRIPTION 🔥

Caller provides appropriate serialization. fr fr, that part is on you.

User space expects the directory offset value of the replaced (new) directory entry to be unchanged after a rename. the way that matters is lowkey iconic 👑

🚨 must-know: Caller must have grabbed a slot for new_dentry in the maple_tree associated with new_dir, even if dentry is negative. do not skip this, bestie 😭

👀 SEE ALSO 👀

Kernel file ./fs/libfs.c, plus all these function pages — go be nosy, it's giving research era 🧚✨

• simple_offset_init(9)
• simple_offset_add(9)
• simple_offset_remove(9)
• simple_offset_rename_exchange(9)
• simple_offset_destroy(9)
• offset_dir_llseek(9)
• offset_readdir(9)
• simple_rename_timestamp(9)
• simple_setattr(9)
• simple_write_end(9)
• simple_read_from_buffer(9)
• simple_write_to_buffer(9)
• memory_read_from_buffer(9)
• generic_encode_ino32_fh(9)
• generic_fh_to_dentry(9)
• generic_fh_to_parent(9)
• simple_fsync_noflush(9)
• simple_fsync(9)
• generic_check_addressable(9)
• simple_get_link(9)
• generic_ci_d_compare(9)
• generic_ci_d_hash(9)
• generic_ci_match(9)
• generic_set_sb_d_ops(9)
• inode_maybe_inc_iversion(9)
• inode_query_iversion(9)
• simple_inode_init_ts(9)
• path_from_stashed(9)
• simple_start_creating(9)

mwah 💋 that's the page! source/version: ./fs · date: October 2026 · page: simple_offset_rename(9) — bye bestie, slay your kernel adventures 🫶🌈