security_fs_use(9)

💅 security_fs_use(9) — the Kernel API Manual tea 🫖

okay so welcome to the Kernel API Manual corner of the group chat, bestie. This is the page for security_fs_use(9), and it's giving filesystem labeling decisions — very demure, very security-coded. ✨

---

🌸 NAME 🌸

security_fs_use — Determine how to handle labeling for a filesystem. 🗂️💖

Like, literally that's the whole vibe: it determines how to handle labeling for a filesystem. No cap. 🫶

---

✨ SYNOPSIS ✨

int security_fs_use (struct super_block *sb );

---

🎀 ARGUMENTS 🎀

• sb — the superblock in question, bestie. That's the superblock we're looking at. 👀💅

---

🦋 SEE ALSO 🦋

Kernel file: ./security/selinux/ss/services.c

and then the whole SEE ALSO squad pulls up, in this exact order:

• security_compute_av(9)
• security_sid_to_context(9)
• security_sid_to_context_inval(9)
• security_context_to_sid(9)
• security_context_to_sid_default(9)
• security_transition_sid(9)
• security_member_sid(9)
• security_change_sid(9)
• services_convert_context(9)
• security_load_policy(9)
• ocontext_to_sid(9)
• security_port_sid(9)
• security_ib_pkey_sid(9)
• security_ib_endport_sid(9)
• security_netif_sid(9)
• security_node_sid(9)
• __security_genfs_sid(9)
• security_genfs_sid(9)
• security_net_peersid_resolve(9)
• security_policycap_supported(9)
• security_netlbl_cache_add(9)
• security_netlbl_secattr_to_sid(9)
• security_netlbl_sid_to_secattr(9)
• __security_read_policy(9)
• security_read_policy(9)
• security_read_state_kernel(9)

---

mwah 💋 this lil page is from source/version ./security/selinux/ss, dated October 2026, and it's called security_fs_use(9) — periodt. 👑💖