Comment # 16 on bug 1227282 from Jiri Wiesner

I have tried reproducing the issue. It cannot be reproduced without installing
the SELinux policies no matter the value of the lsm= or security= parameters. I
can reproduce it after installing the SELinux policies and passing
"lsm=bpf,selinux selinux=1" to the kernel. The system boots up when SELinux
policies are installed but SELinux is off - "lsm=bpf,selinux selinux=0" passed
to the kernel. So, it takes a specific ordering of the LSMs, SELinux policies
and SELinux being on to get a failure. I tried a simple command to search the
SELinux policies:
> grep bpf $(for p in restorecond policycoreutils setools-console selinux-policy-targeted selinux-policy-devel; do rpm -ql $p; done) 2> /dev/null
but I could not make much sense of the output. Could someone in charge of
SELinux look at this issue and clarify the root cause of the failure to boot
up?