[Bugs] [Bug 1242333] New: rdma : pending - porting log messages to a new framework
bugzilla at redhat.com
bugzilla at redhat.com
Mon Jul 13 06:28:51 UTC 2015
https://bugzilla.redhat.com/show_bug.cgi?id=1242333
Bug ID: 1242333
Summary: rdma : pending - porting log messages to a new
framework
Product: GlusterFS
Version: mainline
Component: logging
Severity: medium
Assignee: bugs at gluster.org
Reporter: mselvaga at redhat.com
CC: annair at redhat.com, bugs at gluster.org,
gluster-bugs at redhat.com, rhs-bugs at redhat.com,
sasundar at redhat.com
Depends On: 1242022
Blocks: 1241957
+++ This bug was initially created as a clone of Bug #1242022 +++
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 at 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 at 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)",
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1241957
[Bug 1241957] [ TRACKER ] : Tracker for porting pending log messages
porting to new framework
https://bugzilla.redhat.com/show_bug.cgi?id=1242022
[Bug 1242022] rdma : pending - porting log messages to a new framework
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Bugs
mailing list