Red Hat Bugzilla – Bug 1304597
systemd/kmod package update changes permissions of /dev/fuse
Last modified: 2017-08-03 03:25:38 EDT
Description of problem: After an upgrade to systemd-219-19.el7.x86_64 and kmod-20-5.el7.x86_64 The permissions of /dev/fuse were reset from 0666 to 0600, this appears to be the same symptoms as the systemd upgrade bug in Fedora from a year ago (Redhat BZ 1147248) I'm not sure whether systemd or kmod is culprit but based on the timestamps in yum.log and the ctime of the device node the problem appears to happen when systemd calls systemd-tmpfiles --create in %post (same as the fedora bug) and applies the permissions from /run/tmpfiles.d/kmod.conf which conflict with those in the udev config Version-Release number of selected component (if applicable): systemd-219-19.el7.x86_64 kmod-20-5.el7.x86_64 How reproducible: Unsure but I'm seeing it happen on quite a few machines, so I'd guess pretty high Steps to Reproduce: 1. yum upgrade systemd kmod Actual results: $ ls -l /dev/fuse crw-------. 1 root root 10, 229 Feb 4 15:19 /dev/fuse Expected results: $ ls -l /dev/fuse crw-rw-rw-. 1 root root 10, 229 Feb 1 13:23 /dev/fuse Additional info: $ grep fuse /run/tmpfiles.d/* /usr/lib/udev/rules.d/* | grep 06 /run/tmpfiles.d/kmod.conf:c /dev/fuse 0600 - - - 10:229 /usr/lib/udev/rules.d/50-udev-default.rules:KERNEL=="fuse", MODE="0666", OPTIONS+="static_node=fuse"