RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

ProtectSystem sets /home read-only instead of /usr. This has been fixed upstream already, see "Additional Info".


Version-Release number of selected component (if applicable):
219


How reproducible:
Setting ProtectSystem for a service unit that writes to /home will result in IO error due to /home being read-only. /usr is not read-only and writes are possible altough it should be read-only instead


Steps to Reproduce:
1. Set ProtectSystem to true or full in systemd service unit that writes to /home.
2. Start the unit
3. See journal for error messages when the process tries to write to /home


Actual results:
/home read-only
/usr not protected and in the same state as without ProtectSystem set


Expected results:
/home accessible as usual for process
/usr read-only for process


Additional info:
This bug seems to be introduced in systemd v220[1] and fixed in v221[2].

[1] https://github.com/systemd/systemd/commit/ee818b89f4890b3a00e93772249fce810f60811e
[2] https://github.com/systemd/systemd/commit/d38e01dc96c5cae1986561c4f3bc7f760560bf2a

https://github.com/lnykryn/systemd-rhel/pull/142

fix merged to staging branch -> https://github.com/lnykryn/systemd-rhel/pull/142 -> post

*** Bug 1494430 has been marked as a duplicate of this bug. ***

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:0711