ENUM RFKILL_HARD_BLOCK_REASONS(9)

💅 enum rfkill_hard_block_reasons(9) — the Kernel API Manual, bestie edition

okay so picture this: you're deep in the kernel docs, the man page is literally called enum rfkill_...lock_reasons(9) because even the title bar got truncated by the vibes, and you just want to know why your radio is hard-blocked. say less. this page is short, it's sweet, and it's giving "tiny enum, big responsibilities." 🎀

---

✨ NAME ✨

enum rfkill_hard_block_reasons — literally just the reasons a hard block can happen. that's it. that's the whole name. no cap. 💅

---

🦋 SYNOPSIS 🦋

enum rfkill_hard_block_reasons {
    RFKILL_HARD_BLOCK_SIGNAL ,
    RFKILL_HARD_BLOCK_NOT_OWNER

};

look at her. two constants, zero filler, main character energy. copy it exactly, bestie, every character matters. ✨

---

🌸 Constants 🌸

• RFKILL_HARD_BLOCK_SIGNAL — the hardware rfkill signal is active. like, the actual physical switch / signal is doing its thing and there is nothing you can do about it from software. it's real, it's hardware, it ate. 🔥
• RFKILL_HARD_BLOCK_NOT_OWNER — the NIC is not owned by the host. bestie the network card literally belongs to somebody else, it's not your host's, so. not yours. hands off. 🙈

---

👑 SEE ALSO 👑

go touch grass in ./include/uapi/linux/rfkill.h — that's the kernel file, the source of truth, the mother ship 💖. and while you're there, the whole friend group:

• enum rfkill_type(9)
• enum rfkill_operation(9)
• struct rfkill_event(9)
• struct rfkill_event_ext(9)
• Extensibility(9)

all of them. click through. iykyk. 🫶

---

ngl this page is tiny but don't sleep on it — if you're matching on hard block reasons and you mix these two up, that's a vibe check you will fail. 😭

---

okay that's the whole page, mwah 🍓 — this iconic little entry lives in ./include/uapi/linux, dated October 2026, and it answers to the name enum rfkill_...lock_reasons(9) (yes, with the dots, she's mysterious like that). take care of her, she's family now. 💜✨