ATTR_REMOVE(3)

💖 ATTR_REMOVE(3) 💖

okay bestie, welcome to the XFS Compatibility API corner of section 3 of the manual — yes, that's the (3) in the title, we're in library-call territory, not commands. sit down, grab a strawberry 🍓, and let's talk about deleting attributes.

---

✨ NAME ✨

attr_remove, attr_removef — remove a user attribute of a filesystem object. yeah. that's the whole gig. deleting vibes only 💅

---

🌸 C SYNOPSIS 🌸

#include <attr/attributes.h>

int attr_remove (const char *path, const char *attrname, int flags);

int attr_removef (int fd, const char *attrname, int flags);

look at her. two functions, one dream. ✨

---

🦋 DESCRIPTION 🦋

so basically, attr_remove and attr_removef give you a way to remove attributes that were previously created from filesystem objects. like, the attribute was there, it had a moment, it served looks, and now it's leaving the group chat. 👑

path points to a path name for a filesystem object, and fd refers to the file descriptor associated with a file. if the attribute attrname exists, the attribute name and value will be removed from the filesystem object. both of them. name and value. the whole fit. 😭

the flags argument can contain the following symbols bitwise OR'ed together:

• ATTR_ROOT — look for attrname in the root address space, not in the user address space. > heads up bestie: this one is limited to use by super-user only. super-user energy, no gatekeeping. 👑
• ATTR_DONTFOLLOW — do not follow symbolic links when resolving a path on an attr_remove function call. the default is to follow symbolic links. so if you don't say anything, she's following. she's always following. 🧚

---

💀 attr_remove will fail if one or more of the following are true 💀

• [ENOATTR] — the attribute name given is not associated with the indicated filesystem object. (nothing to remove, nothing to slay, empty handed 😔)
• [ENOENT] — the named file does not exist. girl. where. where is she. 🙈
• [EPERM] — the effective user ID does not match the owner of the file and the effective user ID is not super-user.
• [ENOTDIR] — a component of the path prefix is not a directory.
• [EACCES] — search permission is denied on a component of the path prefix.
• [EINVAL] — a bit was set in the flag argument that is not defined for this system call.
• [EFAULT] — path points outside the allocated address space of the process.
• [ELOOP] — a path name lookup involved too many symbolic links.
• [ENAMETOOLONG] — the length of path exceeds {MAXPATHLEN}, or a pathname component is longer than {MAXNAMELEN}.

---

🌈 attr_removef will fail if 🌈

• [ENOATTR] — the attribute name given is not associated with the indicated filesystem object.
• [EINVAL] — a bit was set in the flag argument that is not defined for this system call, or fd refers to a socket, not a file. not me accidentally passing a socket 💀
• [EFAULT] — attrname points outside the allocated address space of the process.
• [EBADF] — fd does not refer to a valid descriptor.

---

⭐ DIAGNOSTICS ⭐

on success, zero is returned. on error, -1 is returned, and errno is set appropriately. that's it. that's the vibe check. ✨

---

🫶 SEE ALSO 🫶

• attr(1)
• attr_get(3)
• attr_list(3)
• attr_multi(3)
• attr_set(3)

iykyk, the whole extended attributes friendship circle 💜

---

and that's a wrap, bestie! this page came from the Extended Attributes era, dated Dec 2001, and the source/version line is literally just Extended Attributes — so yeah, she's vintage, she's iconic, she's still holding it down. periodt. 💅🎀🌟