Received-SPF: pass (google.com: domain of linux-kernel+bounces-65509-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) client-ip=2604:1380:45d1:ec00::1;
Date: Wed, 14 Feb 2024 11:22:25 -0500
From: Steven Rostedt <rostedt@goodmis.org>
To: Kalle Valo <kvalo@kernel.org>
Cc: regressions@lists.linux.dev, linux-kernel@vger.kernel.org,
 linux-trace-kernel@vger.kernel.org, Jeff Johnson
 <quic_jjohnson@quicinc.com>
Subject: Re: [regression] tracing: kmemleak warning in
 allocate_cmdlines_buffer()
Message-ID: <20240214112225.088484da@gandalf.local.home>
In-Reply-To: <87mss3njvj.fsf@kernel.org>
References: <87r0hfnr9r.fsf@kernel.org>
	<20240214094617.1e6ec684@gandalf.local.home>
	<87mss3njvj.fsf@kernel.org>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Wed, 14 Feb 2024 17:30:40 +0200
Kalle Valo <kvalo@kernel.org> wrote:

> Although the patch didn't apply for me as in my tree the functions are
> in kernel/trace/trace.c. I don't know what happened so as a quick hack I
> just manually added the three lines to my version of trace.c. Let me
> know if there's a git tree or branch you would like me to test, I can do
> that easily.

I sent out a v2 that should apply and I added your Tested-by tag. But you
may want to verify that it does indeed still work, as I decided to swap the
order of adding kmemleak_alloc() with the memset(), so it's not exactly the
same.

Thanks,

-- Steve