Description of problem: It is creating it with SystemHigh. (s15:c0.c1023) system_u:object_r:device_t:s15:c0.c1023 Matchpatcon says it should be s0 system_u:object_r:device_t:s0 This is causing problem on MLS machines.
(In reply to comment #0) > Description of problem: > > It is creating it with SystemHigh. (s15:c0.c1023) > system_u:object_r:device_t:s15:c0.c1023 > > Matchpatcon says it should be s0 > system_u:object_r:device_t:s0 > > This is causing problem on MLS machines. udev does not treat any devices with special rules, so it's all in your hand! Where should udev get the info on how to label the device, if not from selinux itsself?
This directory is created as a side effect I believe. Kernel tells udev to create /dev/snd/seq and udev creates /dev/snd first. Does udev ask SELinux what to label this directory or does it just create the directory and then ask how to label the device? Where in the code is this done?
libudev/libudev-util-private.c util_create_path(..) udev_selinux_setfscreatecon(udev, p, S_IFDIR|0755); ret = mkdir(p, 0755); udev_selinux_resetfscreatecon(udev);
Created attachment 400776 [details] I added this patch and I am not seeing /dev/snd go through this code path. I am not even sure udev is creating the directory.
better change "err" to "info" and set the debuglevel to "info"... err is only compiled, if udev is compiled in debug mode.
ping?
This is still there although I have no idea why. I have been working on other stuff but qa is getting around to testing it.
udev-153-4.fc13 has been submitted as an update for Fedora 13. https://admin.fedoraproject.org/updates/udev-153-4.fc13
udev-153-4.fc13 has been pushed to the Fedora 13 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update udev'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/udev-153-4.fc13
udev-153-4.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.