i_gid_needs_update(9)

💅 i_gid_needs_update(9) — the kernel API manual, bestie edition 🎀

okay so this is the manual page for i_gid_needs_update, a kernel API function, and yes it's from the (9) section which is the fancy "kernel internals" section, iykyk. sit down, hydrate, and let's get into it 💖

---

✨ NAME ✨

i_gid_needs_update — check whether inode's i_gid needs to be updated. that's it, that's the whole vibe check 🌸

---

✨ SYNOPSIS ✨

bool i_gid_needs_update (struct mnt_idmap *idmap , const struct iattr
*attr , const struct inode *inode );

like, it literally returns a bool. yes or no. true or false. iconic behavior honestly 👑

---

🦋 ARGUMENTS 🦋

• idmap — the idmap of the mount that the inode was found from. it's giving "where did you come from, bestie" energy 🗺️
• attr — the new attributes of the inode. the glow-up it might be getting ✨
• inode — the inode to update. the main character of this whole operation 💅

---

🌈 DESCRIPTION 🌈

okay so here's the tea ☕: this function checks whether the $inode's i_gid field needs to be updated, and it does this taking idmapped mounts into account if the filesystem supports it. no cap, that's the whole deal. it's not doing the update, it's just doing the vibe check first, and honestly that's so valid of it 🫶

---

⭐ RETURN ⭐

returns true if the inode's i_gid field needs to be updated, and false if not. literally that simple, bestie 💀

---

🎀 SEE ALSO 🎀

the kernel file ./include/linux/fs.h, plus this whole friend group right here — they're all linked, it's a whole squad 🧚:

• enum positive_aop_returns(9)
• struct address_space(9)
• struct file_ra_state(9)
• struct file(9)
• i_uid_into_vfsuid(9)
• i_uid_needs_update(9)
• i_uid_update(9)
• i_gid_into_vfsgid(9)
• i_gid_update(9)
• inode_fsuid_set(9)
• inode_fsgid_set(9)
• fsuidgid_has_mapping(9)
• inode_set_ctime(9)
• file_write_started(9)
• file_write_not_started(9)
• struct renamedata(9)
• is_mgtime(9)
• iput_if_not_last(9)
• is_idmapped_mnt(9)
• file_start_write(9)
• file_end_write(9)
• kiocb_start_write(9)
• kiocb_end_write(9)
• name_is_dot_dotdot(9)
• name_contains_dotdot(9)
• inode_dio_begin(9)
• inode_dio_end(9)
• generic_ci_validate_strict_name(9)

like, go read them too? they're all lowkey serving 🍓

---

and that's the page!! this one lives in the ./include/linux directory, it's dated October 2026, and yeah — the whole thing is filed under i_gid_needs_update(9). mwah, go touch some inodes 💜✨