Description of problem: Every time I boot, I notice the following messages in boot.log: [1;31mUnable to fix label of /sys/fs/cgroup/systemd: Operation not supported[0m [1;31mUnable to fix label of /sys/fs/cgroup/cpuset: Operation not supported[0m [1;31mUnable to fix label of /sys/fs/cgroup/ns: Operation not supported[0m [1;31mUnable to fix label of /sys/fs/cgroup/cpu: Operation not supported[0m [1;31mUnable to fix label of /sys/fs/cgroup/cpuacct: Operation not supported[0m [1;31mUnable to fix label of /sys/fs/cgroup/memory: Operation not supported[0m [1;31mUnable to fix label of /sys/fs/cgroup/devices: Operation not supported[0m [1;31mUnable to fix label of /sys/fs/cgroup/freezer: Operation not supported[0m [1;31mUnable to fix label of /sys/fs/cgroup/net_cls: Operation not supported[0m [1;31mUnable to fix label of /sys/fs/cgroup/blkio: Operation not supported[0m Welcome to Fedora Could systemd be trying to fix the labels on a file system that does not support labeling? So it is doing setfilecon("cgroup_t") and getting back an error ENOSUP and reporting this as a bug? Should systemd check ENOSUP and not put out an error message? Version-Release number of selected component (if applicable): systemd-11-1.fc15.x86_64 How reproducible: Every boot Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Lennart, I think the problem here is the cgroupfs does not support labeling so if you are calling the setfilecon on each directory it is returning ENOSUP errno. In this case your code should just ignore the error and move on.
Fixed in git.