gfs2_xattr_remove(9)

💅 gfs2_xattr_remove(9) 💅

okay bestie, welcome to the Kernel API Manual entry for gfs2_xattr_remove — we're deep in kernel filesystem territory and it's giving very specific internals ✨

🌸 NAME 🌸

gfs2_xattr_remove — Remove a GFS2 extended attribute

✨ SYNOPSIS ✨

int gfs2_xattr_remove (struct gfs2_inode *ip , int type , const char *name );

🎀 ARGUMENTS 🎀

• ip — The inode, aka the main character here 💖
• type — The type of the extended attribute
• name — The name of the extended attribute

🦋 DESCRIPTION 🦋

So here's the tea: this is not called directly by the VFS. Nope, not even a little. We use the (common) scheme of making a "set with NULL data" mean a remove request.

And bestie, listen — this is different from a set with zero length data. Do not mix those two up, fr fr. One is the remove-request vibe; the other is zero-length data. They are not the same 😭

💀 RETURN 💀

0, or errno on failure.

🔥 SEE ALSO 🔥

Kernel file ./fs/gfs2/xattr.c, plus gfs2_listxattr(9), gfs2_iter_unstuffed(9), __gfs2_xattr_get(9), ea_alloc_blk(9), ea_write(9), __gfs2_xattr_set(9), and gfs2_ea_dealloc(9).

signed off from the ./fs/gfs2 source/version corner, dated October 2026, on page gfs2_xattr_remove(9) — slay and goodbye 🫶💖