From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andi Kleen <andi@firstfloor.org>
Subject: Re: libnuma valgrind errors
Date: Fri, 2 Jul 2010 20:31:43 +0200
Message-ID: <20100702183143.GG12221@basil.fritz.box>
References: <b2d6d086d4b4ae8786b6aede58a3da89@swcp.com>
Mime-Version: 1.0
Return-path: <linux-numa-owner@vger.kernel.org>
Content-Disposition: inline
In-Reply-To: <b2d6d086d4b4ae8786b6aede58a3da89@swcp.com>
Sender: linux-numa-owner@vger.kernel.org
List-ID: <linux-numa.vger.kernel.org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: Trammell Hudson <hudson@osresearch.net>
Cc: linux-numa@vger.kernel.org

On Fri, Jul 02, 2010 at 11:55:09AM -0600, Trammell Hudson wrote:
> When running a trivial program linked with -lnuma under valgrind I get
> errors that numa_bitmask_alloc() has been called and not freed the memory. 
> This is on Ubuntu 9.04, with libnuma 2.0.2 on x86-64.

This is a false positive -- the values are essentially globals that never
go away and it's not a bug. If you don't want to see you would need to use 
a suppression file.

-Andi