linux-kernel - Re: [PATCH] kmemleak: do not leak object after tree insertion error (v3)

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 for Android: free password hash cracker in your pocket

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

Date:	Thu, 19 Apr 2012 10:19:17 +0100
From:	Catalin Marinas <catalin.marinas@....com>
To:	Sergey Senozhatsky <sergey.senozhatsky@...il.com>
Cc:	"linux-mm@...ck.org" <linux-mm@...ck.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] kmemleak: do not leak object after tree insertion
 error (v3)

On Wed, Apr 18, 2012 at 04:44:48PM +0100, Sergey Senozhatsky wrote:
>  [PATCH] kmemleak: do not leak object after tree insertion error
> 
>  In case when tree insertion fails due to already existing object
>  error, pointer to allocated object gets lost because of overwrite
>  with lookup_object() return. Free allocated object before object
>  lookup. 
> 
>  Signed-off-by: Sergey Senozhatsky <sergey.senozhatsky@...il.com>

Thanks. I applied it to my kmemleak branch and I'll send it to Linus at
some point (during the next merging window).

-- 
Catalin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/