REVIEW: http://review.gluster.org/15801 (posix-acl: check dictionary before using it) posted (#1) for review on release-3.9 by Rajesh Joseph (rjoseph)

REVIEW: http://review.gluster.org/15801 (posix-acl: check dictionary before using it) posted (#2) for review on release-3.9 by Rajesh Joseph (rjoseph)

COMMIT: http://review.gluster.org/15801 committed in release-3.9 by Raghavendra Talur (rtalur) 
------
commit d20a4a82d4832274b68015e74233430a49901baf
Author: Rajesh Joseph <rjoseph>
Date:   Thu Nov 3 14:21:28 2016 +0530

    posix-acl: check dictionary before using it
    
    If extended attributes are not present in md-cache it returns NULL as xattr.
    posix acl xlator should check for NULL before using xattr.
    
    If normal and default ACLs are not set on file then md-cache will not contain
    system.posix_acl_access and system.posix_acl_default extended attributes in
    its cache.
    
    Therefore posix_acl_lookup_cbk should check xattr before using it, otherwise
    the logs will get filled with dictionary errors.
    
    > Reviewed-on: http://review.gluster.org/15769
    > Reviewed-by: Raghavendra Talur <rtalur>
    > Smoke: Gluster Build System <jenkins.org>
    > Reviewed-by: jiffin tony Thottan <jthottan>
    > NetBSD-regression: NetBSD Build System <jenkins.org>
    > Reviewed-by: Vijay Bellur <vbellur>
    > CentOS-regression: Gluster Build System <jenkins.org>
    
    (cherry picked from commit de7fe24663713fff364cfc2b52b675e3e979ee68)
    
    Change-Id: Icebf73cf0b313bd3e82ca8cbda63786dd0fa47da
    BUG: 1392869
    Signed-off-by: Rajesh Joseph <rjoseph>
    Reviewed-on: http://review.gluster.org/15801
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>
    Smoke: Gluster Build System <jenkins.org>
    Reviewed-by: Raghavendra Talur <rtalur>

This bug is getting closed because GlusterFS-3.9 has reached its end-of-life [1].

Note: This bug is being closed using a script. No verification has been performed to check if it still exists on newer releases of GlusterFS.
If this bug still exists in newer GlusterFS releases, please open a new bug against the newer release.

[1]: https://www.gluster.org/community/release-schedule/