Bug 456921 - ext4dev has no policy entry to use xattrs in RHEL5
Summary: ext4dev has no policy entry to use xattrs in RHEL5
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: selinux-policy-targeted
Version: 5.3
Hardware: All
OS: Linux
low
low
Target Milestone: rc
: ---
Assignee: Daniel Walsh
QA Contact:
URL:
Whiteboard:
Depends On: 373931
Blocks: 447797
TreeView+ depends on / blocked
 
Reported: 2008-07-28 16:42 UTC by Eric Sandeen
Modified: 2008-07-28 18:35 UTC (History)
1 user (show)

Fixed In Version: u2
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-07-28 18:35:28 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Eric Sandeen 2008-07-28 16:42:30 UTC
+++ This bug was initially created as a clone of Bug #373931 +++

(AFAIK RHEL5.3 still needs this for ext4 tech preview?)

Mounting ext4dev filesystems gets:

SELinux: initialized (dev sdb5, type ext4dev), not configured for labeling

Can we add both "ext4dev" and "ext4" (which will be the eventual name) to the
policy as "should use xattrs?"

Thanks,

-Eric

-- Additional comment from dwalsh on 2007-11-10 07:40 EST --
Fixed in selinux-policy-3.1.1-1.fc9

Comment 1 RHEL Program Management 2008-07-28 16:51:44 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update
release.

Comment 2 Eric Sandeen 2008-07-28 17:03:21 UTC
Oh, on the other hand it looks like policy-20061106.patch maybe already
addresses this?  If so please close but wanted to be sure all the ext4 support
was really properly in place, since I don't think we ever had an explicit bug
for it.

Thanks,
-Eric


Note You need to log in before you can comment on or make changes to this bug.