mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Alexei Starovoitov <ast@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>
Cc: "open list:XDP SOCKETS (AF_XDP)" <bpf@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: bpf leaking memory
Date: Fri, 1 Aug 2025 10:31:48 -0600	[thread overview]
Message-ID: <97100307-8297-45b2-8f0b-d3b7ef109805@kernel.dk> (raw)

Hi,

Current -git (any within the last day or two) leaks memory at boot,
as reported by kmemleak, see below. This is running debian unstable
on aarc64.

unreferenced object 0xffff0000c820d000 (size 64):
  comm "systemd", pid 1, jiffies 4294667980
  hex dump (first 32 bytes):
    01 00 00 00 00 00 ff ff 00 00 00 00 00 00 00 00  ................
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  backtrace (crc 84021ac):
    kmemleak_alloc+0x3c/0x50
    __kmalloc_node_track_caller_noprof+0x370/0x500
    krealloc_noprof+0x238/0x300
    kvrealloc_noprof+0x44/0x100
    do_check_common+0x2668/0x2d50
    bpf_check+0x2464/0x2ec0
    bpf_prog_load+0x5c8/0xba8
    __sys_bpf+0x9c0/0x20a0
    __arm64_sys_bpf+0x24/0x60
    invoke_syscall.constprop.0+0x44/0x100
    el0_svc_common.constprop.0+0x3c/0xe0
    do_el0_svc+0x20/0x30
    el0_svc+0x30/0xe0
    el0t_64_sync_handler+0x98/0xe0
    el0t_64_sync+0x170/0x178
unreferenced object 0xffff0000c8ccd900 (size 64):
  comm "systemd", pid 1, jiffies 4294667983
  hex dump (first 32 bytes):
    01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  backtrace (crc 8e80d088):
    kmemleak_alloc+0x3c/0x50
    __kmalloc_node_track_caller_noprof+0x370/0x500
    krealloc_noprof+0x238/0x300
    kvrealloc_noprof+0x44/0x100
    do_check_common+0x2668/0x2d50
    bpf_check+0x2464/0x2ec0
    bpf_prog_load+0x5c8/0xba8
    __sys_bpf+0x9c0/0x20a0
    __arm64_sys_bpf+0x24/0x60
    invoke_syscall.constprop.0+0x44/0x100
    el0_svc_common.constprop.0+0x3c/0xe0
    do_el0_svc+0x20/0x30
    el0_svc+0x30/0xe0
    el0t_64_sync_handler+0x98/0xe0
    el0t_64_sync+0x170/0x178
unreferenced object 0xffff0000c8fc0300 (size 64):
  comm "systemd", pid 1, jiffies 4294668000
  hex dump (first 32 bytes):
    01 00 00 00 29 00 00 20 00 00 00 00 00 00 00 00  ....).. ........
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  backtrace (crc 335bd269):
    kmemleak_alloc+0x3c/0x50
    __kmalloc_node_track_caller_noprof+0x370/0x500
    krealloc_noprof+0x238/0x300
    kvrealloc_noprof+0x44/0x100
    do_check_common+0x2668/0x2d50
    bpf_check+0x2464/0x2ec0
    bpf_prog_load+0x5c8/0xba8
    __sys_bpf+0x9c0/0x20a0
    __arm64_sys_bpf+0x24/0x60
    invoke_syscall.constprop.0+0x44/0x100
    el0_svc_common.constprop.0+0x3c/0xe0
    do_el0_svc+0x20/0x30
    el0_svc+0x30/0xe0
    el0t_64_sync_handler+0x98/0xe0
    el0t_64_sync+0x170/0x178
unreferenced object 0xffff0000c8c84980 (size 64):
  comm "systemd", pid 1, jiffies 4294668003
  hex dump (first 32 bytes):
    01 00 00 00 23 00 00 00 00 00 00 00 00 00 00 00  ....#...........
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  backtrace (crc 3cc2e52e):
    kmemleak_alloc+0x3c/0x50
    __kmalloc_node_track_caller_noprof+0x370/0x500
    krealloc_noprof+0x238/0x300
    kvrealloc_noprof+0x44/0x100
    do_check_common+0x2668/0x2d50
    bpf_check+0x2464/0x2ec0
    bpf_prog_load+0x5c8/0xba8
    __sys_bpf+0x9c0/0x20a0
    __arm64_sys_bpf+0x24/0x60
    invoke_syscall.constprop.0+0x44/0x100
    el0_svc_common.constprop.0+0x3c/0xe0
    do_el0_svc+0x20/0x30
    el0_svc+0x30/0xe0
    el0t_64_sync_handler+0x98/0xe0
    el0t_64_sync+0x170/0x178

-- 
Jens Axboe



             reply	other threads:[~2025-08-01 16:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-01 16:31 Jens Axboe [this message]
2025-08-01 22:41 ` Alexei Starovoitov
2025-08-01 23:26   ` Eduard Zingerman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=97100307-8297-45b2-8f0b-d3b7ef109805@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®