linux-kernel - Re: [kmemleak report 0/2] kernel 3.1.6, x86

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: <CAHkRjk7MGGJE04dgETmqs_SBb8ju2BOiEmei3aV8MRcpof8-GA@mail.gmail.com>
Date:	Tue, 17 Jan 2012 16:53:10 +0000
From:	Catalin Marinas <catalin.marinas@....com>
To:	Roland Eggner <edvx1@...temanalysen.net>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [kmemleak report 0/2] kernel 3.1.6, x86_64

On 15 January 2012 22:29, Roland Eggner <edvx1@...temanalysen.net> wrote:
> It looks like memory leaks are “eating” 1G+ after only 1 week uptime … that's
> not nice.

Does your system actually lose this memory or they are just be false
positives? We've known since around 3.1 that kmemleak has some issues
with per-cpu memory allocations and reporting false positives. The
patches just went in (to be visible in 3.3-rc1). Alternatively, you
could cherry-pick them from here:

http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=shortlog;h=029aeff5db879afd7760f11214b6fea45f76b58e

(commit f528f0b8e5 "kmemleak: Handle percpu memory allocation" is the
one you would need)

Thanks.

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