{"push_id":850415668,"size":4,"distinct_size":4,"ref":"refs/heads/release-3.7","head":"3d3176958b7da48dbacb1a5a0fedf26322a38297","before":"e3b48d847492b831487a8539e3e726706959ac2f","commits":[{"sha":"9a0e3a7ecc61e47a0780708f86efc0170b8a85db","author":{"email":"411ac29a97bdb332e7e6a7946f7898a5dd9a3b55@redhat.com","name":"Ashish Pandey"},"message":"cluster/ec: update version and size on good bricks\n\nProblem: readdir/readdirp fops calls [f]xattrop with\nfop->good which contain only one brick for these operations.\nThat causes xattrop to be failed as it requires at least\n\"minimum\" number of brick.\n\nSolution: Use lock->good_mask to call xattrop. lock->good_mask\ncontain all the good locked bricks on which the previous write\nopearion was successfull.\n\nChange-Id: If1b500391aa6fca6bd863702e030957b694ab499\nBUG: 1272404\nSigned-off-by: Ashish Pandey <aspandey@redhat.com>\nReviewed-on: http://review.gluster.org/12419\nTested-by: NetBSD Build System <jenkins@build.gluster.org>\nReviewed-by: Xavier Hernandez <xhernandez@datalab.es>\nTested-by: Xavier Hernandez <xhernandez@datalab.es>\nReviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>\nReviewed-on: http://review.gluster.org/12440\nTested-by: Gluster Build System <jenkins@build.gluster.com>","distinct":true,"url":"https://api.github.com/repos/anoopcs9/glusterfs/commits/9a0e3a7ecc61e47a0780708f86efc0170b8a85db"},{"sha":"43d819bc99874ee900a03a27c79cd8523423d9b6","author":{"email":"4016c024458812ad0ed1ccc433aff0daf07d9647@redhat.com","name":"Raghavendra G"},"message":"mount/fuse: use a queue instead of pipe to communicate with thread\ndoing inode/entry invalidations.\n\nWriting to pipe can block if pipe is full. This can lead to deadlocks\nin some situations. Consider following situation:\n\n1. Kernel sends a write on an inode. Client is waiting for a response\n   to write from brick.\n2. A lookup happens on behalf of different application/thread on the\n   same inode. In response, mdc tries to invalidate the inode.\n3. fuse_invalidate_inode is called. It writes a invalidation request\n   to pipe. Another thread which reads from this pipe writes the\n   request to /dev/fuse. The invalidate code in fuse-kernel-module,\n   tries to acquire lock on all pages for the inode and is blocked as\n   a write is in progress on same inode (step 1)\n4. Now, poller thread is blocked in invalidate notification and cannot\n   receive any messages from same socket (on which lookup response\n   came). But client is expecting a response for write from same\n   socket (again step1) and we've a deadlock.\n\nThe deadlock can be solved in two ways:\n1. Use a queue (and a conditional variable for notifications) to pass\n   invalidation requests from poller to invalidate thread. This is a\n   variant of using non-blocking pipe, but doesn't have any limit on the\n   amount of data (worst case we run out of memory and error out).\n\n2. Allow events from sockets, immediately after we read one\n   rpc-msg. Currently we disallow events till that rpc-msg is read from\n   socket, processed and handled by higher layers. That way we won't run\n   into these kind of issues. Also, it'll increase parallelism in way of\n   reading from sockets.\n\nThis patch implements solution 1 above.\n\nChange-Id: I8e8199fd7f4da9eab46a719d9292f35c039967e1\nBUG: 1276550\nSigned-off-by: Raghavendra G <rgowdapp@redhat.com>\nReviewed-on: http://review.gluster.org/12402\n(cherry picked from commit 4f65f894ab1c19618383ba212dc0f0df48675823)\nReviewed-on: http://review.gluster.org/12466\nTested-by: Gluster Build System <jenkins@build.gluster.com>","distinct":true,"url":"https://api.github.com/repos/anoopcs9/glusterfs/commits/43d819bc99874ee900a03a27c79cd8523423d9b6"},{"sha":"0b6f0e09715fb2ba8f86bd80b05d552ae75aeda9","author":{"email":"9b70a715983960700df84e6820ee03dd0ee9e457@redhat.com","name":"Mohamed Ashiq"},"message":"cli : 'gluster volume help' output sorted alphabetically\n\n'gluster volume help' output is not sorted alphabetically.\nThis makes little harder for the user to search or get to know of\nfew gluster volume commands usage just from gluster cli.\n\n    Backport of http://review.gluster.org/11663\n\nCherry picked from 323e71617fee5020324540776d0d4469577f0afe\nChange-Id: I855da2e4748a5c2ff3be319c50fa9548d676ee8a\nBUG: 1276208\nSigned-off-by: Mohamed Ashiq <mliyazud@redhat.com>\n>Reviewed-on: http://review.gluster.org/11663\n>Tested-by: Gluster Build System <jenkins@build.gluster.com>\n>Reviewed-by: Manikandan Selvaganesh <mselvaga@redhat.com>\n>Reviewed-by: Anand Nekkunti <anekkunt@redhat.com>\nReviewed-on: http://review.gluster.org/12452\nTested-by: NetBSD Build System <jenkins@build.gluster.org>\nTested-by: Gluster Build System <jenkins@build.gluster.com>\nReviewed-by: Anand Nekkunti <anekkunt@redhat.com>","distinct":true,"url":"https://api.github.com/repos/anoopcs9/glusterfs/commits/0b6f0e09715fb2ba8f86bd80b05d552ae75aeda9"},{"sha":"3d3176958b7da48dbacb1a5a0fedf26322a38297","author":{"email":"36ab91862badf129e22a0765506a8b181227d4e1@redhat.com","name":"vmallika"},"message":"quota: add version to quota xattrs\n\nThis is a backport of http://review.gluster.org/#/c/12386/\n\nWhen a quota is disable and the clean-up process terminated\nwithout completely cleaning-up the quota xattrs.\nNow when quota is enabled again, this can mess-up the accounting\n\nA version number is suffixed for all quota xattrs and this version\nnumber is specific to marker xaltor, i.e when quota xattrs are\nrequested by quotad/client marker will remove the version suffix in the\nkey before sending the response\n\n> Change-Id: I1ca2c11460645edba0f6b68db70d476d8d26e1eb\n> BUG: 1272411\n> Signed-off-by: vmallika <vmallika@redhat.com>\n> Reviewed-on: http://review.gluster.org/12386\n> Tested-by: NetBSD Build System <jenkins@build.gluster.org>\n> Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>\n> Tested-by: Gluster Build System <jenkins@build.gluster.com>\n> Reviewed-by: Manikandan Selvaganesh <mselvaga@redhat.com>\n> Reviewed-by: Raghavendra G <rgowdapp@redhat.com>\n\nChange-Id: I67b1b930b28411d76b2d476a4e5250c52aa495a0\nBUG: 1277080\nSigned-off-by: vmallika <vmallika@redhat.com>\nReviewed-on: http://review.gluster.org/12487\nTested-by: NetBSD Build System <jenkins@build.gluster.org>\nTested-by: Gluster Build System <jenkins@build.gluster.com>\nReviewed-by: Raghavendra G <rgowdapp@redhat.com>\nTested-by: Raghavendra G <rgowdapp@redhat.com>","distinct":true,"url":"https://api.github.com/repos/anoopcs9/glusterfs/commits/3d3176958b7da48dbacb1a5a0fedf26322a38297"}]}