Description of problem:

Xattr flipping is the mechanism we use to circumvent kernel's protection of the "trusted" xattr namespace in the case when we want to give control over some such attrs to unprivileged user (case of unprivileged geo-rep slaves).

For this reason, we treat these attrs addressable also in the "system" namespace (mapped back to trusted before hitting the platter). The unified behavior for system and trusted namespaces is now broken -- in trusted, setxattrs take effect
as one would expect, in system they are just no-ops.

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

From http://review.gluster.com/3687 on.

How reproducible:

Very.

Steps to Reproduce:
1. set up glusterfs, create a volume called, say, "poc"
2. gluster vol set poc indexing on
3. mount poc with this command:
   glusterfs -s localhost --volfile-id=poc --client-pid=-1 /mnt/gluster
4. setfattr -h -n system.glusterfs.whatever.xtime -v something /mnt/gluster
5. getfattr -h -m. -n system.glusterfs.whatever.xtime /mnt/gluster

Actual results:

/mnt/gluster: system.glusterfs.whatever.xtime: No such attribute

Expected results:

# file: mnt/gluster
system.glusterfs.whatever.xtime="something"