linux-kernel - [kmemleak] unreferenced object 0xcd9c1a80 (size 192):

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <CA+7wUsyxpHnq_POujjwEVXhJjE5GRLN9GypV+63g1OFmfq=_ZA@mail.gmail.com>
Date:   Sun, 11 Feb 2018 16:24:46 +0100
From:   Mathieu Malaterre <malat@...ian.org>
To:     Alexei Starovoitov <ast@...nel.org>,
        Daniel Borkmann <daniel@...earbox.net>,
        linux-kernel@...r.kernel.org
Subject: [kmemleak] unreferenced object 0xcd9c1a80 (size 192):

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
...