From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757590AbcAOMy7 (ORCPT ); Fri, 15 Jan 2016 07:54:59 -0500 Received: from bombadil.infradead.org ([198.137.202.9]:45889 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752526AbcAOMy6 (ORCPT ); Fri, 15 Jan 2016 07:54:58 -0500 Date: Fri, 15 Jan 2016 13:54:53 +0100 From: Peter Zijlstra To: Alexander Shishkin Cc: Ingo Molnar , linux-kernel@vger.kernel.org, vince@deater.net, eranian@google.com, Arnaldo Carvalho de Melo Subject: Re: [PATCH] perf: Cleanup user's child events Message-ID: <20160115125453.GK6357@twins.programming.kicks-ass.net> References: <1452856935-364-1-git-send-email-alexander.shishkin@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1452856935-364-1-git-send-email-alexander.shishkin@linux.intel.com> User-Agent: Mutt/1.5.21 (2012-12-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jan 15, 2016 at 01:22:15PM +0200, Alexander Shishkin wrote: > Events are leaking in the following scenario: user creates an event for > task A, task A forks into B (producing a child event), user closes the > original event. Both original user's event and its child will remain for > as long as task B is around. In other words, we don't clean up children > when we try to release the parent. The orphan stuff should clear those up, no?