{"push_id":778298792,"size":1,"distinct_size":1,"ref":"refs/heads/release-3.7","head":"3dbcb230ba833b108bd4cb35614ec6875d62eefa","before":"9f3ee74959853f1d92c3302ac72231bd75d293c6","commits":[{"sha":"3dbcb230ba833b108bd4cb35614ec6875d62eefa","author":{"email":"10460665c63c1e41b922ea2cdf63084aa1a91e2a@redhat.com","name":"Ravishankar N"},"message":"afr: Unset dirty xattr after setting pending xattr during post-op\n\nBackport of http://review.gluster.org/#/c/12078\n\nIn AFR transaction, in the pre-op, the dirty xattr is set. In the\npost-op, if the transaction fails on one of the bricks, then on the\nhealthy brick, the dirty xattr is unset and then the pending xattr (for\nthe brick that went down) is set in that order. If the brick crashes\nafter unsetting the dirty xattr, we have lost information about a\npending heal. Hence we need to reverse the order, i.e. set pending xattr\nfirst followed by unsetting the dirty.\n\nChange-Id: I0b8a872cb4579a1bad602f70c76f09691bd582b2\nBUG: 1258845\nSigned-off-by: Ravishankar N <ravishankar@redhat.com>\nReviewed-on: http://review.gluster.org/12079\nTested-by: NetBSD Build System <jenkins@build.gluster.org>\nReviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>\nTested-by: Gluster Build System <jenkins@build.gluster.com>\nReviewed-by: Anuradha Talur <atalur@redhat.com>\nReviewed-by: Krutika Dhananjay <kdhananj@redhat.com>","distinct":true,"url":"https://api.github.com/repos/gluster/glusterfs/commits/3dbcb230ba833b108bd4cb35614ec6875d62eefa"}]}