Description of problem: ----------------------- There are occurrences of gf_log and gf_log_callingfn under posix. These instances should be ported to the corresponding gf_msg functions Version-Release number of selected component (if applicable): ------------------------------------------------------------- RHGS 3.1 Nightly ( glusterfs-3.7.1-8.el6rhs ) Info: ----- gf_log instances ================= [satheesaran@dhcppc1 rdma]$ grep -r "gf_log " * -A1 src/name.c: gf_log (this->name, GF_LOG_DEBUG, src/name.c- "transport.rdma.bind-path not specified " -- src/name.c: gf_log (this->name, GF_LOG_ERROR, src/name.c- "cannot bind to unix-domain socket %d (%s)", -- src/rdma.c: gf_log ("rdma", GF_LOG_WARNING, src/rdma.c- "deallocation of memory region " gf_log_callingfn instances =========================== [satheesaran@dhcppc1 rdma]$ grep -r "gf_log_callingfn " * -A1 src/rdma.c: gf_log_callingfn (GF_RDMA_LOG_NAME, GF_LOG_WARNING, src/rdma.c- "not able to get a post to send msg"); -- src/rdma.c: gf_log_callingfn (this->name, GF_LOG_DEBUG, src/rdma.c- "disconnect called (peer:%s)",
Patch posted upstream master http://review.gluster.org/#/c/11607/
Patch is merged.
*** Bug 1252274 has been marked as a duplicate of this bug. ***
Hi Vivek, I have posted the patch to release-3.7 branch. http://review.gluster.org/#/c/11878/ (Release - 3.7) https://code.engineering.redhat.com/gerrit/#/c/54855/ (Downstream)
Thanks Manikandan.
Patch upstream : http://review.gluster.org/#/c/11607/ Patch release-3.7 :http://review.gluster.org/11878
Verified with the latest code as available under RHGS 3.1.2 downstream branch. There were no instances of gf_log or gf_log_callingfn Marking this bug as VERIFIED
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-0193.html