[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20220422074243.GU2731@worktop.programming.kicks-ass.net>
Date: Fri, 22 Apr 2022 09:42:43 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: ashamedbit <muralianiruddhan@...il.com>
Cc: Andy Lutomirski <luto@...nel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
Dave Hansen <dave.hansen@...ux.intel.com>, x86@...nel.org,
"H. Peter Anvin" <hpa@...or.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Subject: x86/vdso/vdso2c: Memory Leak fix, Fix leak of
variable name in vdso2c.c
On Fri, Apr 22, 2022 at 03:09:22AM -0400, ashamedbit wrote:
> The file vdso2c.c contains a memory leak of variable 'name'.
> This leak was detected by ASAN(AddressSanitizer) on local builds.
> A tool called AddressWatcher automatically attempts to fix memory
> leaks suggested by ASAN. The fix has been inserted to stop the
> memory leak in the file vdso2c.c.
I think you need to fix your tool, this is 3 lines before the program
terminates. Please explain how that is a leak?
Powered by blists - more mailing lists