__vfs_removexattr_locked(9)

🌸 __vfs_removexattr_locked 💅

okay bestie, so this is a page from the Kernel API Manual and it's about __vfs_removexattr_locked — the locked, locked-in, main-character version of removing an extended attribute. ✨

---

✨ NAME ✨

__vfs_removexattr_locked — set an extended attribute while holding the inode lock

yes, the description literally says "set" even though the whole function is about removing — we don't ask questions, we copy the facts fr fr 🙈

---

🎀 SYNOPSIS 🎀

int __vfs_removexattr_locked (struct mnt_idmap *idmap , struct dentry
*dentry , const char *name , struct delegated_inode *delegated_inode );

it's giving "returns an int" and takes four things. slay. 💜

---

🦋 ARGUMENTS 🦋

• idmap — the idmap of the mount of the target inode. iykyk. 🌈
• dentry — the object you're gonna perform setxattr on. that's the target, bestie. 🎯
• name — the name of the xattr to remove. literally just a string, do with that what you will. 🍓
• delegated_inode — on return, this will contain an inode pointer that a delegation was broken on, and NULL if none. so lowkey it's an out-param situation 👀

---

💖 SEE ALSO 💖

• Kernel file ./fs/xattr.c
• may_write_xattr(9)
• __vfs_setxattr_noperm(9)
• __vfs_setxattr_locked(9)
• vfs_listxattr(9)
• generic_listxattr(9)
• xattr_full_name(9)
• simple_xattr_space(9)
• simple_xattr_free(9)
• simple_xattr_free_rcu(9)
• simple_xattr_alloc(9)
• simple_xattr_get(9)
• simple_xattr_set(9)
• simple_xattr_set_limited(9)
• simple_xattr_list(9)
• simple_xattr_add(9)
• simple_xattr_add_limited(9)
• simple_xattrs_free(9)
• simple_xattr_cache_cleanup(9)

---

🫶 that's the whole page, no cap. every single one of those cross-refs stays, because they ate and left no crumbs. 🔥

---

and that's a wrap, bestie!! this came to you from ./fs, dated October 2026, straight outta the Kernel API Manual — go forth and remove those xattrs (while holding the inode lock, obviously) 👑💅🧚