<p dir="ltr">-Atin<br>
Sent from one plus one<br>
On 04-Mar-2016 6:12 am, "Joseph Fernandes" <<a href="mailto:josferna@redhat.com">josferna@redhat.com</a>> wrote:<br>
><br>
> Hi Ajil,<br>
><br>
> Well few things,<br>
><br>
> 1. Whenever you see a crash its better to send across the Backtrace(BT) using gdb and attach the log files (or share it via some cloud drive)<br>
><br>
> 2. About the memory leak, What kind of tools are you using for profiling memory, valgrind ? if so please attach the valgrind reports.<br>
> $> glusterd --xlator-option *.run-with-valgrind=yes<br>
><br>
> 3. Well I am not sure if glusterd uses any of the mempools as we do in client and brick processes, Atin can shed some light on this.<br>
> Well In that case you can used the statedump mechanism check for mem-leaks check the glusterfs/doc/debugging/<a href="http://statedump.md">statedump.md</a><br>
GlusterD does use mempool and it has infra for capturing statedump as well. I am aware of few bytes of memory leaks in few paths which is really not a huge concern but it shouldn't crash.<br>
><br>
> Hope this helps<br>
><br>
> ~Joe<br>
><br>
><br>
> ----- Original Message -----<br>
> > From: "Ajil Abraham" <<a href="mailto:ajil95.abraham@gmail.com">ajil95.abraham@gmail.com</a>><br>
> > To: "Atin Mukherjee" <<a href="mailto:atin.mukherjee83@gmail.com">atin.mukherjee83@gmail.com</a>><br>
> > Cc: "Gluster Devel" <<a href="mailto:gluster-devel@gluster.org">gluster-devel@gluster.org</a>><br>
> > Sent: Thursday, March 3, 2016 10:48:56 PM<br>
> > Subject: Re: [Gluster-devel] glusterd crashing<br>
> ><br>
> > Hi Atin,<br>
> ><br>
> > The inputs I use are as per the requirements of a project I am working on for<br>
> > one of the large finance institutions in Dubai. I will try to handle the<br>
> > input validation within my code. I uncovered some of the issues while doing<br>
> > a thorough testing of my code.<br>
> ><br>
> > I tried with 3.7.6 and also my own build from master branch. I will check<br>
> > with my superiors before sending you backtrace and other details. So far, I<br>
> > have seen memory leak in 100s of KBs.<br>
> ><br>
> > -Ajil<br>
> ><br>
> ><br>
> > On Thu, Mar 3, 2016 at 10:17 PM, Atin Mukherjee < <a href="mailto:atin.mukherjee83@gmail.com">atin.mukherjee83@gmail.com</a><br>
> > > wrote:<br>
> ><br>
> ><br>
> ><br>
> ><br>
> > Hi Ajil,<br>
> ><br>
> > Its good to see that you are doing a thorough testing gluster. From your mail<br>
> > it looks like your automation focuses on mostly negative tests. I need few<br>
> > additional details to get to know whether they are known:<br>
> ><br>
> > 1. Version of gluster<br>
> > 2. Backtrace of the crash along with reproducer<br>
> > 3. Amount of memory leak in terms of bytes/KB/MB?? Have you already<br>
> > identified them?<br>
> ><br>
> > -Atin<br>
> > Sent from one plus one<br>
> > On 03-Mar-2016 10:01 pm, "Ajil Abraham" < <a href="mailto:ajil95.abraham@gmail.com">ajil95.abraham@gmail.com</a> > wrote:<br>
> ><br>
> ><br>
> ><br>
> > For my project, I am trying to do some automation using glusterd. It is very<br>
> > frustrating to see it crashing frequently. Looks like input validation is<br>
> > the culprit. I also see lot of buffer overflow and memory leak issues.<br>
> > Making a note of these and will try to fix them. Surprised to see such basic<br>
> > issues still existing in Gluster.<br>
> ><br>
> > -Ajil<br>
> ><br>
> > _______________________________________________<br>
> > Gluster-devel mailing list<br>
> > <a href="mailto:Gluster-devel@gluster.org">Gluster-devel@gluster.org</a><br>
> > <a href="http://www.gluster.org/mailman/listinfo/gluster-devel">http://www.gluster.org/mailman/listinfo/gluster-devel</a><br>
> ><br>
> ><br>
> > _______________________________________________<br>
> > Gluster-devel mailing list<br>
> > <a href="mailto:Gluster-devel@gluster.org">Gluster-devel@gluster.org</a><br>
> > <a href="http://www.gluster.org/mailman/listinfo/gluster-devel">http://www.gluster.org/mailman/listinfo/gluster-devel</a><br>
</p>