On 02/16/2017 03:35 AM, Xavier Hernandez wrote:
- 1421649: Ashis/Niels when can we expect a fix to land for this?
I think this will require more thinking and participation from experts
on security and selinux to come up with a good and clean solution. Not
sure if this can be done before 3.10 release.
There is a workaround (set disperse.cpu-extensions = none) and a
mitigating solution (patch https://review.gluster.org/16614) though.
Acknowledged, tracker updated accordingly.
- 1421956: Xavi, I guess you would backport the fix on mainline once
that is merged into 3.10, right?
Yes. It's on review on master (https://review.gluster.org/16614). As
soon as it's merged I'll backport it to 3.10.
Pranith/Anoop/Ashish, can one of you finish the review of the above
patch on master please, so that we can get the backport going!
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/gluster-devel
