feat_selinux only gets tested in the Build/SELinux job, which boots a Fedora VM with SELinux on purpose. feat_smack isn't built in CI at all. So the 'not enabled' code paths never run anywhere.
Found this in #13311 — a stale Cargo.toml comment claimed both features need an enabled kernel to run, which isn't true, and that wrong assumption hid a real bug where mkdir's SMACK branch silently ignored --context instead of warning. Would be good to have a plain ubuntu-latest job building with both features where neither kernel module is actually on.
feat_selinux only gets tested in the Build/SELinux job, which boots a Fedora VM with SELinux on purpose. feat_smack isn't built in CI at all. So the 'not enabled' code paths never run anywhere.
Found this in #13311 — a stale Cargo.toml comment claimed both features need an enabled kernel to run, which isn't true, and that wrong assumption hid a real bug where mkdir's SMACK branch silently ignored --context instead of warning. Would be good to have a plain ubuntu-latest job building with both features where neither kernel module is actually on.