On Tue, Jun 23, 2015 at 05:30:39PM +0530, Vijaikumar M wrote: > > > On Tuesday 23 June 2015 04:28 PM, Niels de Vos wrote: > >On Tue, Jun 23, 2015 at 03:45:43PM +0530, Vijaikumar M wrote: > >>I have submitted below patch which fixes this issue. I am handling memory > >>clean-up with reference countmechanism. > >> > >>http://review.gluster.org/#/c/11361 > >Is there a reason you can not use the (new) refcounting functions that > >were introduceed with http://review.gluster.org/11022 ? > > I was not aware that ref-counting patch was merged. Sure we will use these > function and re-submit my patch. Ok, thanks! Niels > > Thanks, > Vijay > > > >It would be nicer to standardize all refcounting mechanisms on one > >implementation. I hope we can replace existing refcounting with this one > >too. Introducing more refcounting ways is not going to be helpful. > > > >Thanks, > >Niels > > > >>Thanks, > >>Vijay > >> > >> > >> > >> > >>On Tuesday 23 June 2015 12:58 PM, Raghavendra G wrote: > >>>Multiple replies to same query. Pick one ;). > >>> > >>>On Tue, Jun 23, 2015 at 12:55 PM, Venky Shankar <yknev.shankar@xxxxxxxxx > >>><mailto:yknev.shankar@xxxxxxxxx>> wrote: > >>> > >>> OK. Two reverts of the same patch ;) > >>> > >>> Pick one. > >>> > >>> On Tue, Jun 23, 2015 at 12:51 PM, Raghavendra Gowdappa > >>> <rgowdapp@xxxxxxxxxx <mailto:rgowdapp@xxxxxxxxxx>> wrote: > >>> > Seems like its a memory corruption caused by: > >>> > http://review.gluster.org/11311 > >>> > > >>> > I've reverted the patch at: > >>> > http://review.gluster.org/11360 > >>> > > >>> > ----- Original Message ----- > >>> >> From: "Xavier Hernandez" <xhernandez@xxxxxxxxxx > >>> <mailto:xhernandez@xxxxxxxxxx>> > >>> >> To: "Gluster Devel" <gluster-devel@xxxxxxxxxxx > >>> <mailto:gluster-devel@xxxxxxxxxxx>> > >>> >> Sent: Tuesday, June 23, 2015 12:44:47 PM > >>> >> Subject: /tests/bugs/quota/bug-1153964.t is > >>> consistently failing > >>> >> > >>> >> Hi, > >>> >> > >>> >> the quota test bug-1153964.t is failing consistently for a totally > >>> >> unrelated patch. Is this a known issue ? > >>> >> > >>> >> > >>> http://build.gluster.org/job/rackspace-regression-2GB-triggered/11142/consoleFull > >>> >> > >>> http://build.gluster.org/job/rackspace-regression-2GB-triggered/11165/consoleFull > >>> >> > >>> http://build.gluster.org/job/rackspace-regression-2GB-triggered/11172/consoleFull > >>> >> > >>> http://build.gluster.org/job/rackspace-regression-2GB-triggered/11191/consoleFull > >>> >> > >>> >> Xavi > >>> >> _______________________________________________ > >>> >> Gluster-devel mailing list > >>> >> Gluster-devel@xxxxxxxxxxx <mailto:Gluster-devel@xxxxxxxxxxx> > >>> >> http://www.gluster.org/mailman/listinfo/gluster-devel > >>> >> > >>> > _______________________________________________ > >>> > Gluster-devel mailing list > >>> > Gluster-devel@xxxxxxxxxxx <mailto:Gluster-devel@xxxxxxxxxxx> > >>> > http://www.gluster.org/mailman/listinfo/gluster-devel > >>> _______________________________________________ > >>> Gluster-devel mailing list > >>> Gluster-devel@xxxxxxxxxxx <mailto:Gluster-devel@xxxxxxxxxxx> > >>> http://www.gluster.org/mailman/listinfo/gluster-devel > >>> > >>> > >>> > >>> > >>>-- > >>>Raghavendra G > >>> > >>> > >>>_______________________________________________ > >>>Gluster-devel mailing list > >>>Gluster-devel@xxxxxxxxxxx > >>>http://www.gluster.org/mailman/listinfo/gluster-devel > >>_______________________________________________ > >>Gluster-devel mailing list > >>Gluster-devel@xxxxxxxxxxx > >>http://www.gluster.org/mailman/listinfo/gluster-devel > _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-devel
