Kaleb KEITHLEY
2016-Jan-21 22:29 UTC
[Gluster-users] [Gluster-devel] Memory leak in GlusterFS FUSE client
On 01/20/2016 04:08 AM, Oleksandr Natalenko wrote:> Yes, there are couple of messages like this in my logs too (I guess one > message per each remount): > > ==> [2016-01-18 23:42:08.742447] I [fuse-bridge.c:3875:notify_kernel_loop] 0- > glusterfs-fuse: kernel notifier loop terminated > ==>Bug reports and fixes for master and release-3.7 branches are: master) https://bugzilla.redhat.com/show_bug.cgi?id=1288857 http://review.gluster.org/12886 release-3.7) https://bugzilla.redhat.com/show_bug.cgi?id=1288922 http://review.gluster.org/12887 The release-3.7 fix will be in glusterfs-3.7.7 when it's released. I think with even with the above fixes applied there are still some issues remaining. I have submitted additional/revised fixes on top of the above fixes at: master: http://review.gluster.org/13274 release-3.7: http://review.gluster.org/13275 I invite you to review the patches in gerrit (review.gluster.org). Regards, -- Kaleb
Oleksandr Natalenko
2016-Jan-21 23:56 UTC
[Gluster-users] [Gluster-devel] Memory leak in GlusterFS FUSE client
With the proposed patches I get the following assertion while copying files to GlusterFS volume: ==glusterfs: mem-pool.c:305: __gf_free: Assertion `0xCAFEBABE == header->magic' failed. Program received signal SIGABRT, Aborted. [Switching to Thread 0x7fffe9ffb700 (LWP 12635)] 0x00007ffff6f215f8 in raise () from /usr/lib/libc.so.6 (gdb) bt #0 0x00007ffff6f215f8 in raise () from /usr/lib/libc.so.6 #1 0x00007ffff6f22a7a in abort () from /usr/lib/libc.so.6 #2 0x00007ffff6f1a417 in __assert_fail_base () from /usr/lib/libc.so.6 #3 0x00007ffff6f1a4c2 in __assert_fail () from /usr/lib/libc.so.6 #4 0x00007ffff7b6046b in __gf_free (free_ptr=0x7fffdc0b8f00) at mem-pool.c: 305 #5 0x00007ffff5144eb9 in notify_kernel_loop (data=0x63df90) at fuse-bridge.c: 3893 #6 0x00007ffff72994a4 in start_thread () from /usr/lib/libpthread.so.0 #7 0x00007ffff6fd713d in clone () from /usr/lib/libc.so.6 == On ??????, 21 ????? 2016 ?. 17:29:53 EET Kaleb KEITHLEY wrote:> On 01/20/2016 04:08 AM, Oleksandr Natalenko wrote: > > Yes, there are couple of messages like this in my logs too (I guess one > > message per each remount): > > > > ==> > [2016-01-18 23:42:08.742447] I [fuse-bridge.c:3875:notify_kernel_loop] 0- > > glusterfs-fuse: kernel notifier loop terminated > > ==> > Bug reports and fixes for master and release-3.7 branches are: > > master) > https://bugzilla.redhat.com/show_bug.cgi?id=1288857 > http://review.gluster.org/12886 > > release-3.7) > https://bugzilla.redhat.com/show_bug.cgi?id=1288922 > http://review.gluster.org/12887 > > The release-3.7 fix will be in glusterfs-3.7.7 when it's released. > > I think with even with the above fixes applied there are still some > issues remaining. I have submitted additional/revised fixes on top of > the above fixes at: > > master: http://review.gluster.org/13274 > release-3.7: http://review.gluster.org/13275 > > I invite you to review the patches in gerrit (review.gluster.org). > > Regards, > > -- > > Kaleb
Oleksandr Natalenko
2016-Jan-21 23:59 UTC
[Gluster-users] [Gluster-devel] Memory leak in GlusterFS FUSE client
I see extra GF_FREE (node); added with two patches: ==$ git diff HEAD~2 | gist https://gist.github.com/9524fa2054cc48278ea8 == Is that intentionally? I guess I face double-free issue. On ??????, 21 ????? 2016 ?. 17:29:53 EET Kaleb KEITHLEY wrote:> On 01/20/2016 04:08 AM, Oleksandr Natalenko wrote: > > Yes, there are couple of messages like this in my logs too (I guess one > > message per each remount): > > > > ==> > [2016-01-18 23:42:08.742447] I [fuse-bridge.c:3875:notify_kernel_loop] 0- > > glusterfs-fuse: kernel notifier loop terminated > > ==> > Bug reports and fixes for master and release-3.7 branches are: > > master) > https://bugzilla.redhat.com/show_bug.cgi?id=1288857 > http://review.gluster.org/12886 > > release-3.7) > https://bugzilla.redhat.com/show_bug.cgi?id=1288922 > http://review.gluster.org/12887 > > The release-3.7 fix will be in glusterfs-3.7.7 when it's released. > > I think with even with the above fixes applied there are still some > issues remaining. I have submitted additional/revised fixes on top of > the above fixes at: > > master: http://review.gluster.org/13274 > release-3.7: http://review.gluster.org/13275 > > I invite you to review the patches in gerrit (review.gluster.org). > > Regards, > > -- > > Kaleb