linux-kernel - Re: Leaks in trace reported by kmemleak

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <c4e36d110910190215j129e61ey5e20634a4bc19292@mail.gmail.com>
Date:	Mon, 19 Oct 2009 11:15:54 +0200
From:	Zdenek Kabelac <zdenek.kabelac@...il.com>
To:	Catalin Marinas <catalin.marinas@....com>
Cc:	Li Zefan <lizf@...fujitsu.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Steven Rostedt <rostedt@...dmis.org>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Ingo Molnar <mingo@...e.hu>
Subject: Re: Leaks in trace reported by kmemleak

2009/10/16 Catalin Marinas <catalin.marinas@....com>:
> On Fri, 2009-10-16 at 17:07 +0200, Zdenek Kabelac wrote:
>> So I've tested this modified version and it gives much better result
>> with respect to amount of leaked objects
>
> BTW, I created this tree with kmemleak patches to be pushed upstream:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/cmarinas/kmemleak.git
>
> It would be easier to test.

Yes this branch worked well - and there were no leaks  from i915 or
kvm modules for trace.

What is however interesting is the false positive leak for
dma_debug_init(). Which is sometimes listed and sometimes not - the
memory is allocated just once in the code during boot, so it's strange
that pointers to that area are sometimes out of kmemleak scan.

Zdenek
--
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/