On Fri, Jul 3, 2015 at 7:58 AM, Marcel Ritter <ritter.marcel@xxxxxxxxx> wrote: > Hi, > > I've been running some btrfs tests (mainly duperemove related) with > linux kernel 4.1 for the last few days. > > Now I noticed by accident (dying processes), that all my memory (128 > GB!) is gone. > "Gone" meaning, there's no user space process allocating this memory. > > Digging deeper I found the missing memory using slabtop (see output of > /proc/slabinfo is attached): Looks like I got a lot of kernel memory > allocated by kmalloc-1024 (memory leak?). > Given the fact that the test machine does little more than btrfs > testing I think this may be btrfs related. > > I was running duperemove on a 1.5 TB volume around the time the first > "Out of memory" error were logged, so maybe the memory leak can be > found somewhere in this code path. > > I'm still waiting for a scrub run to finish, after that I'll reboot > the machine and try to reproduce this behaviour with a fresh btrfs > filesystem. > > Have there been any fixes concerning memory leaks since 4.1 release I could try? > Any other ideas how to track down this potential memory leak? Hi, We had Julian Taylor reporting the same on IRC a couple days ago (he also found what was being leaked). I just sent a fix and cc'ed you (https://patchwork.kernel.org/patch/6713301/). thanks > > Bye, > Marcel -- Filipe David Manana, "Reasonable men adapt themselves to the world. Unreasonable men adapt the world to themselves. That's why all progress depends on unreasonable men." -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
