linux-kernel - Re: [PATCH 2/4] kmemleak: Handle percpu memory allocation

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: <20111004075915.GE15637@dhcp-172-17-108-109.mtv.corp.google.com>
Date:	Tue, 4 Oct 2011 00:59:15 -0700
From:	Tejun Heo <htejun@...il.com>
To:	Catalin Marinas <catalin.marinas@....com>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Huajun Li <huajun.li.lee@...il.com>,
	Christoph Lameter <cl@...ux-foundation.org>
Subject: Re: [PATCH 2/4] kmemleak: Handle percpu memory allocation

Hello,

On Mon, Oct 03, 2011 at 04:21:26PM +0100, Catalin Marinas wrote:
> The updated patch below adds specific kmemleak API for percpu pointers
> so that it only logs one call per allocation rather than the number of
> possible cpus (could be split in two, though the patch is relatively
> simple):

The percpu part looks fine to me but I don't know how kmemleak works
to judge whether the kmemleak part is okay or not.  This just avoids
false positives from slab and would still require bumping up the early
log memory as # of cpus increases, right?

For percpu part,

  Acked-by: Tejun Heo <tj@...nel.org>

How do you want to route this?  If kmemleak patches get routed through
-mm, please feel free to send it to Andrew with Acked-by's added.

Thank you.

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