Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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.

Bug 977047

Summary: feature request: add zfs to the list of xattr supported file systems
Product: Red Hat Enterprise Linux 6 Reporter: steven.merrill
Component: selinux-policyAssignee: Miroslav Grepl <mgrepl>
Status: CLOSED ERRATA QA Contact: Michal Trunecka <mtruneck>
Severity: low Docs Contact:
Priority: unspecified    
Version: 6.4CC: beaaegicfqmq6rykaqaakty3lqcg6btv, bellboyc, deadshort, dwalsh, ebenes, mmalik, mtruneck, steven.merrill, tlavigne
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 811532 Environment:
Last Closed: 2013-11-21 10:31:35 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Patch to re-enable ZFS xattr support in RHEL 6.4's SELinux policy. none

Description steven.merrill 2013-06-22 22:15:10 UTC
Created attachment 764195 [details]
Patch to re-enable ZFS xattr support in RHEL 6.4's SELinux policy.

+++ This bug was initially created as a clone of Bug #811532 +++

The solution from bug #811532 appears to have regressed in RHEL 6.4 (or at some point after 3.7.19-146, in any case.)

When I build selinux-policy-3.7.19-195.el6_4.1.src.rpm, I can confirm that the serefpolicy-3.7.19/policy/modules/kernel/filesystem.te file does not contain the necessary "fs_use_xattr" line for zfs.

I have rebuilt the selinux-policy-3.7.19-195.el6_4.1.src.rpm with the attached patch and after installing the result, I can properly use ZFS with SELinux.

Comment 2 steven.merrill 2013-06-23 02:01:12 UTC
In looking at this a little more, I don't see the appropriate "fs_use_xattr" line for ZFS when I do an `rpmbuild -bp` on  http://ftp.redhat.com/redhat/linux/enterprise/6Server/en/os/SRPMS/selinux-policy-3.7.19-154.el6.src.rpm, which was the release that supposedly fixed bug #811532.

Comment 3 Daniel Walsh 2013-06-24 15:11:45 UTC
We have added this line to Fedora.

Comment 5 deadshort 2013-11-11 21:26:45 UTC
 [ Gentle prod to reapply this lost/regressed fix... ] The one line patch does still work on 6.4, applied to the recent selinux-policy-3.7.19-195.el6_4.18.src.rpm. It would be convenient and appreciated to have in the official RHEL update stream. Especially since RH has already decided to publish the fix, back for RHBA-2012:0780-1.

Comment 6 errata-xmlrpc 2013-11-21 10:31:35 UTC
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.

http://rhn.redhat.com/errata/RHBA-2013-1598.html