Hi all, there are still quite some patches that did not get suffient reviews before getting merged in the 3.5 stable branch. I would appreciate it if some reviews can be done on the following patches [1]: (Change-Number: Subject) #8248: afr : Added xdata flags to indicate probable existence of stale index. #9056: api: versioned symbols in libgfapi.so for compatibility #9068: cluster/afr: Metadata self-heal should filter trusted.afr.* #9088: cluster/afr: Preserve errno in case of failures on all subvols #9091: features/marker: Filter internal xattrs in lookup #9096: libglusterfs: brick crashed after failing to send RPC reply, client_t #9155: rdma: mount hangs for rdma type transport. #9156: rdma: glusterd crash if rdma_disconnect is called as soon as connect a request. #9157: rdma:setting rdma REUSEADDR flag to rdma id. #9158: rdma:rdma fuse mount hangs for tcp,rdma volumes if brick is down. #9159: rdma:client process will hang if server is started to send the request before completing connection establishment #9160: rdma: client connection establishment takes more time #9161: mount: Verify mount failure in mount.glusterfs wrapper. #9162: mount:Handle -o transport option in mount.glusterfs #9163: rdma: Wrong volfile fetch on fuse mounting tcp,rdma volume via rdma #9164: rdma: Client volfile name change for supporting rdma #9165: rdma :mount fails for nfs protocol in rdma volumes #9166: rdma: glusterfsd SEGV at volume start #9189: rdma:process crash if address family is not specified #9199: pkg-config: make the version in gluster-api.pc backwards compatible #9352: features/locks: Add lk-owner checks in entrylk #9374: cluster/afr: serialize inode locks In addition to the reviews that are needed, several bugs still need work in the form of patches and/or backports. The bugs that have been proposed for the next release can be found through the glusterfs-3.5.4 blocker bug [2]. These are the ones pending: #1117888: Problem when enabling quota : Could not start quota auxiliary mount #1134050: Glfs_fini() not freeing the resources #1166862: rmtab file is a bottleneck when lot of clients are accessing a volume through NFS It is well possible that patches for these bugs have not landed in the master and release-3.6 branches. In that case, the bugs would have an additional dependency in their 'depends on' field. A further expanded bug tree [3] displays those dependencies. There currently is no schedule for the 3.5.4 release, but it would be nice to be able to merge the patches that fix bugs which our users have reported. Thanks for your assistance! Niels 1. http://review.gluster.org/#/q/project:glusterfs+branch:release-3.5+status:open+%28label:Code-Review%253D%252B1+OR+label:Code-Review%253D%252B2+OR+label:Verified%253D%252B1%29+NOT+topic:rfc+NOT+label:Code-Review%253D-2,n,z 2. https://bugzilla.redhat.com/showdependencytree.cgi?maxdepth=1&id=glusterfs-3.5.4&hide_resolved=1 3. https://bugzilla.redhat.com/showdependencytree.cgi?maxdepth=3&id=glusterfs-3.5.4&hide_resolved=1
Attachment:
pgpY9v9bDGr85.pgp
Description: PGP signature
_______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-devel
