Hi, On Sun, Feb 11, 2018 at 5:54 PM, Alexei Starovoitov <alexei.starovoi...@gmail.com> wrote: > On Sun, Feb 11, 2018 at 7:24 AM, Mathieu Malaterre <ma...@debian.org> wrote: >> Alexei, >> >> Could you please comment on why I am seeing those memleaks being >> reported on my ppc32 system ? Should they be marked as false positive >> ? >> >> System is Mac Mini G4, git/master (4.15.0+), ppc. >> >> Thanks for your time >> >> $ dmesg >> ... >> [ 1281.504173] kmemleak: 36 new suspected memory leaks (see >> /sys/kernel/debug/kmemleak) >> >> Where: >> >> # cat /sys/kernel/debug/kmemleak >> unreferenced object 0xdee25000 (size 192): >> comm "systemd", pid 1, jiffies 4294894348 (age 1438.580s) >> hex dump (first 32 bytes): >> c0 56 2f 88 00 00 00 00 00 00 00 0b 00 00 00 0c .V/............. >> 00 00 00 08 00 00 00 01 00 00 00 01 00 00 00 01 ................ >> backtrace: >> [<6c69baf5>] trie_alloc+0xb0/0x150 >> [<fa093284>] SyS_bpf+0x288/0x1458 >> [<82182f53>] ret_from_syscall+0x0/0x38 >> unreferenced object 0xdee25900 (size 192): >> comm "systemd", pid 1, jiffies 4294894540 (age 1437.812s) >> hex dump (first 32 bytes): >> c0 56 2f 88 00 00 00 00 00 00 00 0b 00 00 00 08 .V/............. >> 00 00 00 08 00 00 00 01 00 00 00 01 00 00 00 01 ................ >> backtrace: >> [<6c69baf5>] trie_alloc+0xb0/0x150 >> [<fa093284>] SyS_bpf+0x288/0x1458 >> [<82182f53>] ret_from_syscall+0x0/0x38 > > hmm. looks real. Is there a reproducer? > Yonghong, lpm map not cleaning after itself?
Not really. I simply boot up my machine and wait for the first kmemleak scan.
