bpf_remove_d...xattr_locked(9)

💅 bpf_remove_d...xattr_locked(9) 💅

Ok bestie, welcome to the Kernel API Manual — this page is all about bpf_remove_dentry_xattr_locked, and yes the title is abbreviated because terminal life is rough. 🫶

🌸 NAME 🌸

bpf_remove_dentry_xattr_locked — remove a xattr of a dentry.

✨ SYNOPSIS ✨

int bpf_remove_dentry_xattr_locked (struct dentry *dentry , const char *name__str );

🎀 ARGUMENTS 🎀

• dentry — dentry to get xattr from.
• name__str — name of the xattr.

🦋 DESCRIPTION 🦋

Rmove xattr name__str of dentry. (Yep, “Rmove” is literally what the original says — we’re keeping the typo, it’s part of the lore. 💀)

For security reasons, only name__str with prefix "security.bpf." is allowed. No cap, that prefix is not optional. 🔥

The caller already locked dentry->d_inode. So like… don’t come in here unlocked, bestie. 💅

👑 RETURN 👑

0 on success, a negative value on error.

🌈 SEE ALSO 🌈

• Kernel file ./fs/bpf_fs_kfuncs.c
• bpf_get_task_exe_file(9)
• bpf_put_file(9)
• bpf_path_d_path(9)
• bpf_get_dentry_xattr(9)
• bpf_get_file_xattr(9)
• bpf_set_dentry_xattr_locked(9)
• bpf_set_dentry_xattr(9)
• bpf_remove_dentry_xattr(9)
• bpf_cgroup_read_xattr(9)
• bpf_sock_read_xattr(9)
• bpf_real_data_inode(9)

Cute sign-off: source/version is ./fs, date is October 2026, and the page is bpf_remove_d...xattr_locked(9). Slay, you made it to the end. 💖✨