Bug 1415918 - Cache security.ima xattrs as well
Summary: Cache security.ima xattrs as well
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: md-cache
Version: 3.10
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On: 1416030
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-01-24 04:55 UTC by Poornima G
Modified: 2017-03-06 17:44 UTC (History)
3 users (show)

Fixed In Version: glusterfs-3.10.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1416030 (view as bug list)
Environment:
Last Closed: 2017-03-06 17:44:03 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Poornima G 2017-01-24 04:55:43 UTC
Description of problem:
From kernel version 3.X or greater, creating of a file results in removexattr call on security.ima xattr. But this xattr is not set on the file unless IMA feature is active. Hence add it in the cache to make it faster.


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Shyamsundar 2017-01-30 14:24:56 UTC
WorkerAnt had issues on 23/24th Jan. So the patch link is not posted here. Manually doing so.

Patch posted at: https://review.gluster.org/16460

Comment 2 Worker Ant 2017-01-30 14:25:07 UTC
COMMIT: https://review.gluster.org/16460 committed in release-3.10 by Shyamsundar Ranganathan (srangana) 
------
commit 9e661d9496125d03c668353a9c718e8812f3fe05
Author: Poornima G <pgurusid>
Date:   Mon Dec 26 14:28:22 2016 +0530

    md-cache: Cache security.ima xattrs
    
    Backport of http://review.gluster.org/16296
    
    From kernel version 3.X or greater, creating of a file
    results in removexattr call on security.ima xattr. But
    this xattr is not set on the file unless IMA feature
    is active. With this patch, removxattr call returns
    ENODATA if it is not found in the cache.
    
    > Change-Id: I8136096598a983aebc09901945eba1db1b2f93c9
    > Signed-off-by: Poornima G <pgurusid>
    > Reviewed-on: http://review.gluster.org/16296
    > Smoke: Gluster Build System <jenkins.org>
    > NetBSD-regression: NetBSD Build System <jenkins.org>
    > CentOS-regression: Gluster Build System <jenkins.org>
    > Reviewed-by: Raghavendra G <rgowdapp>
    > (cherry picked from commit ac629e574935a8aed6526936bc83b1c6d295ae67)
    
    Change-Id: I27abc23024c8fcf07389608df61ef6e64736d414
    BUG: 1415918
    Signed-off-by: Poornima G <pgurusid>
    Reviewed-on: https://review.gluster.org/16460
    Smoke: Gluster Build System <jenkins.org>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>
    Reviewed-by: Raghavendra G <rgowdapp>

Comment 3 Shyamsundar 2017-03-06 17:44:03 UTC
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.10.0, please open a new bug report.

glusterfs-3.10.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://lists.gluster.org/pipermail/gluster-users/2017-February/030119.html
[2] https://www.gluster.org/pipermail/gluster-users/


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