Bug 642664

Summary: "early boot" spew: 'Unable to fix label of /sys/fs/cgroup/XXXX: Operation not supported'
Product: [Fedora] Fedora Reporter: Tom London <selinux>
Component: systemdAssignee: Lennart Poettering <lpoetter>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: dwalsh, karo1170, lpoetter, metherid, mschmidt, notting, plautrba
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-10-19 17:36:22 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Tom London 2010-10-13 14:24:43 UTC
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:

Comment 1 Daniel Walsh 2010-10-13 15:17:29 UTC
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.

Comment 2 Lennart Poettering 2010-10-19 17:36:22 UTC
Fixed in git.