+Mohit
Mohit had written a similar script to RCA an issue couple of months back.
It would help if we placed the scripts, tapsets in the source tree itself (maybe in a directory under glusterfs/extras/).
We could also have the tapset packaged into debuginfo packages and deployed under /usr/share/systemtap/ path upon installation.
We could also have the tapset packaged into debuginfo packages and deployed under /usr/share/systemtap/ path upon installation.
Regards,
Sanoj
On Fri, Mar 31, 2017 at 12:44 PM, Sonal Arora <sarora@xxxxxxxxxx> wrote:
Hi,I am working on finding ways to indentify ref leaks in glusterfs.Description of Issue : https://bugzilla.redhat.com/show_bug.cgi?id=1417539 Goal : To make script which could detect all kind of ref leaks.The above script is a POC program to depict the idea of how to identify leaks. Script is probing dict_ref() and dict_unref() and keeping a track of the pointers, back traces which are referenced/dereferenced by above functions. If the count of refs is unequal to unrefs for each pointer,it will print all the traces corresponding to the leaked pointer.I am working on post processing the output - to filter only the leaked traces and to write the output after every few hours into a file.The script can be extended to all objects being referenced (like inodes/fds).End Goal : Future goal is to make it more versatile, dynamic and light weight so that it can be even utilized on production environments without utilizing much of the system resources.Request your comments and suggestions.Best-Sonal
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/gluster-devel
_______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://lists.gluster.org/mailman/listinfo/gluster-devel
