Ask Your Question
0

Why so many "SELinux: xxx not defined in policy" errors in dmesg?

asked 2017-11-18 07:46:07 -0600

aiwha gravatar image
  • Fedora 26, Keeping update.
  • Kernel: 4.13.12-200.fc26.x86_64
  • SELinux: 3.13.1-260.14.fc26

Screenshot<em>2017-11-18</em>21-42-41.png

Should I reset selinux policy to the default to remove those errors? and how to reset to default?

Thanks a lot for your reply...

edit retag flag offensive close merge delete

2 Answers

Sort by ยป oldest newest most voted
0

answered 2017-11-18 16:45:52 -0600

sideburns gravatar image

I don't know if this will help, but try running this command in a terminal:

sudo touch /.autorelabel

Then, reboot, but be patient, as SELinux will be restoring everything's context. It may not be what you need, but it's worth a shot, especially if you reboot just before you have to be away from your computer for a while. Good luck to both of you, and let us know if this does any good.

edit flag offensive delete link more

Comments

According to my understanding, "/.autorelabel" means to relabel all file context, not rebuild policy....

aiwha gravatar imageaiwha ( 2017-11-18 23:01:59 -0600 )edit
0

answered 2017-11-18 14:51:42 -0600

villykruse gravatar image

This is normal. The SELinux rules are rather complex and it would not be easy to fix these messages. On my system I get the same messages.

edit flag offensive delete link more

Comments

yes, I know it is very hard, so I don't change anything. But Fedora 25 is no problem, both 26 and 27 has same problem.

aiwha gravatar imageaiwha ( 2017-11-18 23:06:59 -0600 )edit

You might consider writing a bugzilla report for this.

villykruse gravatar imagevillykruse ( 2017-11-18 23:35:06 -0600 )edit

Question Tools

1 follower

Stats

Asked: 2017-11-18 07:26:05 -0600

Seen: 141 times

Last updated: Nov 18 '17