mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Subject: [for-linus][PATCH] ring-buffer: Fix subbuf_ids memory leak in rb_allocate_cpu_buffer() error path
Date: Fri, 31 Jul 2026 20:36:11 -0400	[thread overview]
Message-ID: <20260731203611.680cbc68@robin> (raw)


tracing fix for 7.2:

- Fix memory leak of subbuf_ids in rb_allocate_cpu_buffer()

  Remote buffers allocate a subbuf_ids array. If the allocator function
  fails after it is allocated, it does not free it, resulting in a
  memory leak.

  git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git
trace/fixes

Head SHA1: 260b20d9b78bf002f89088fb62d60e8dee98f6f8


Masami Hiramatsu (Google) (1):
      ring-buffer: Fix subbuf_ids memory leak in rb_allocate_cpu_buffer() error path

----
 kernel/trace/ring_buffer.c | 1 +
 1 file changed, 1 insertion(+)
---------------------------
commit 260b20d9b78bf002f89088fb62d60e8dee98f6f8
Author: Masami Hiramatsu (Google) <mhiramat@kernel.org>
Date:   Fri Jul 31 23:16:46 2026 +0900

    ring-buffer: Fix subbuf_ids memory leak in rb_allocate_cpu_buffer() error path
    
    In rb_allocate_cpu_buffer(), cpu_buffer->subbuf_ids is allocated using
    kcalloc() when buffer->remote is non-NULL. If a subsequent page allocation
    fails (e.g., ring_buffer_desc_page() returns NULL or rb_allocate_pages()
    fails), execution jumps to fail_free_reader.
    
    While __free(kfree) automatically frees the outer cpu_buffer structure
    at scope exit, kfree(cpu_buffer) does not recursively free nested heap
    pointers such as cpu_buffer->subbuf_ids, resulting in a memory leak.
    
    Fix this by explicitly freeing cpu_buffer->subbuf_ids in the
    fail_free_reader error unwinding path when cpu_buffer->remote is set.
    
    Link: https://patch.msgid.link/178550740672.380917.6067449683620196150.stgit@devnote2
    Fixes: 2e67fabd8b77 ("ring-buffer: Introduce ring-buffer remotes")
    Assisted-by: Antigravity:gemini-3.6-flash
    Signed-off-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
    Reviewed-by: Vincent Donnefort <vdonnefort@google.com>
    Signed-off-by: Steven Rostedt <rostedt@goodmis.org>

diff --git a/kernel/trace/ring_buffer.c b/kernel/trace/ring_buffer.c
index 78d3875a47a5..8e2485bb3aa8 100644
--- a/kernel/trace/ring_buffer.c
+++ b/kernel/trace/ring_buffer.c
@@ -2599,6 +2599,7 @@ rb_allocate_cpu_buffer(struct trace_buffer *buffer, long nr_pages, int cpu)
 	return_ptr(cpu_buffer);
 
  fail_free_reader:
+	kfree(cpu_buffer->subbuf_ids);
 	free_buffer_page(cpu_buffer->reader_page);
 
 	return NULL;

                 reply	other threads:[~2026-08-01  0:36 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20260731203611.680cbc68@robin \
    --to=rostedt@goodmis.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@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®