linux-kernel - kmemleak reports

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-next>] [day] [month] [year] [list]

Message-ID: <4A5D148A.5090405@gmail.com>
Date:	Tue, 14 Jul 2009 20:28:10 -0300
From:	Kevin Winchester <kjwinchester@...il.com>
To:	Catalin Marinas <catalin.marinas@....com>
CC:	Arjan van de Ven <arjan@...radead.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: kmemleak reports

Hi Catalin,

I have noticed a few kmemleak reports being sent to LKML in the last few days, and I could chime in with mine, if you wish:

    kmemleak: 97 new suspected memory leaks (see /sys/kernel/debug/kmemleak)

The entries are for X, ntpdate, scsi_scan_2, softirq, swapper, in case there's anything surprising in there.

However, I was thinking that you might soon start getting too many reports to process.  I wonder if there might be some way that you could have a similar facility to kerneloops that would automatically register leak reports to a website where they could be organized and ranked by number of occurrences.  Are the individual leaks reported in such at way that would allow them to be grouped like that?

If a kerneloops-style setup is not desirable/feasible, would you be able to send me a walkthrough for how you go about tracking down one of these leaks?  Then I might be able to help out by investigating a few of my own.

Thanks,

-- 
Kevin Winchester

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