Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757445Ab1CNW1n (ORCPT ); Mon, 14 Mar 2011 18:27:43 -0400 Received: from leopard.mail.utk.edu ([160.36.0.85]:38675 "EHLO leopard.mail.utk.edu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757404Ab1CNW1m (ORCPT ); Mon, 14 Mar 2011 18:27:42 -0400 Date: Mon, 14 Mar 2011 18:27:19 -0400 (EDT) From: Vince Weaver To: linux-kernel@vger.kernel.org cc: Peter Zijlstra , Paul Mackerras , Ingo Molnar , Arnaldo Carvalho de Melo Subject: Re: perf: kernel memory leak when inherit enabled In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 739 Lines: 20 On Fri, 11 Mar 2011, Vince Weaver wrote: > > While trying to use perf events with inherit enabled to profile some > multi-threaded BLAS routines (using PAPI) I ended up out-of-memorying my > machine. It turns out you can quickly leak gigabytes of kernel memory > that isn't freed when the process exits. I've bisected this. There's a whole day I'll never see again. binutils 2.21 and gcc-4.5 for the lose :( Anyway this memory leak with inherit was introduced in 4fd38e4595e Vince -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/