Received: by 2002:ac0:a679:0:0:0:0:0 with SMTP id p54csp652668imp; Thu, 21 Feb 2019 08:31:11 -0800 (PST) X-Google-Smtp-Source: AHgI3IaGHgHYW2xPkjG8KoWzAtcN6kCAfrlV1bVfXaCM6bDbFjDDsBCP74eRguZCL+V+r9D/GueP X-Received: by 2002:a65:6658:: with SMTP id z24mr39288680pgv.189.1550766671808; Thu, 21 Feb 2019 08:31:11 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1550766671; cv=none; d=google.com; s=arc-20160816; b=H4PuwSgtvhzaXU5z46caAhL/uHsErm+uztS+Mm5r/4/JWbMU1sa6M8/WewKIiHmKEo 2zoowb3ejs7/RRLrQ8aioeZZjb51/kphD1TNH0bIOYUAA79WW+XbuaPJDRIvs+TAwZ/u xIAH8a+8IKUQzCoiErVfnqv3m+cYAPqaQKxbY4EdRMRTCls2GUARtpP+znKFWaqiN4pW zgmVvrHQdwkS46GXNgDOxRCw4Kk/9sQh1Cmdr728ki1pefxyMhK45yetSOeaqyWjEDRJ u+N8ZPoRO67ZWUaWlyEl7gRfWXj2wbLa0Bp7vmGuP8zvtZX74P6AsoXBnABvESFtKAvi Qdmw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=3a5zYvNv9hKE1mAZz2nAsZFGJQYldBzFlvjW+RQTeMI=; b=aEoFEy2qQ25EdCzcsZ3wTETwGjUfGHnpWRsB6LaEZ4J9jCmCCAEV2byUV+8wu7P34K +bIM+cI41JqhuKkag+uX/jZU2AsrfSH7HFCaY0FM0BcovAPE3gBmxMTxgfnUC8HijRXa KVJwFPi49J1rDUmqforLh+kaKa9GeKZTCa/iuQ8ZChXbcW/qrvGheotLchrGPl+Os9R4 hNzeZqsMj2uHn4YHdD7x3khzKna+RgzmikUDUotUSMbK94phMqrfj5k3stJ0qilwjXMn hx0ysXFCNye5hIEyfS7ahcDZYbrorKcziQkeMwCe3sZmgNcLhOV02Lp632T9F3EA21Kv 2VYA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id x1si1770078plo.58.2019.02.21.08.30.55; Thu, 21 Feb 2019 08:31:11 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727485AbfBUQ3C (ORCPT + 99 others); Thu, 21 Feb 2019 11:29:02 -0500 Received: from mx1.redhat.com ([209.132.183.28]:35060 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726074AbfBUQ3B (ORCPT ); Thu, 21 Feb 2019 11:29:01 -0500 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id A6A8D30A56BB; Thu, 21 Feb 2019 16:29:01 +0000 (UTC) Received: from krava (ovpn-204-108.brq.redhat.com [10.40.204.108]) by smtp.corp.redhat.com (Postfix) with SMTP id 69D6E1001DD3; Thu, 21 Feb 2019 16:28:59 +0000 (UTC) Date: Thu, 21 Feb 2019 17:28:58 +0100 From: Jiri Olsa To: Jonas Rabenstein Cc: linux-perf-users@vger.kernel.org, Peter Zijlstra , Ingo Molnar , Arnaldo Carvalho de Melo , Alexander Shishkin , Namhyung Kim , linux-kernel@vger.kernel.org Subject: Re: [PATCH] perf hist: fix memory leak if histogram entry is reused Message-ID: <20190221162858.GA3940@krava> References: <20190221122306.1511-1-jonas.rabenstein@studium.uni-erlangen.de> <20190221123909.GG10990@krava> <20190221135320.io7egcwajehfrdd5@studium.uni-erlangen.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190221135320.io7egcwajehfrdd5@studium.uni-erlangen.de> User-Agent: Mutt/1.10.1 (2018-07-13) X-Scanned-By: MIMEDefang 2.84 on 10.5.11.22 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.47]); Thu, 21 Feb 2019 16:29:01 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Feb 21, 2019 at 02:53:20PM +0100, Jonas Rabenstein wrote: > On Thu, Feb 21, 2019 at 01:39:09PM +0100, Jiri Olsa wrote: > > On Thu, Feb 21, 2019 at 01:23:06PM +0100, Jonas Rabenstein wrote: > > > In __hists__add_entry the srcline of the addr_location is duplicated > > > for the hist_entry. If hists__findnew_entry returns an already existing > > > hist_entry the srcline has to be freed again as no further reference to > > > that duplicated srcline would exists anymore. > > > > > > Signed-off-by: Jonas Rabenstein > > > --- > > > tools/perf/util/hist.c | 3 +++ > > > 1 file changed, 3 insertions(+) > > > > > > diff --git a/tools/perf/util/hist.c b/tools/perf/util/hist.c > > > index 8aad8330e392..25b8dbdbbe87 100644 > > > --- a/tools/perf/util/hist.c > > > +++ b/tools/perf/util/hist.c > > > @@ -623,6 +623,9 @@ __hists__add_entry(struct hists *hists, > > > .ops = ops, > > > }, *he = hists__findnew_entry(hists, &entry, al, sample_self); > > > > > > + if (he && he->srcline != entry.srcline) > > > + free(entry.srcline); > > > + > > > if (!hists->has_callchains && he && he->callchain_size != 0) > > > hists->has_callchains = true; > > > return he; > > > > nice, do we have similar issue in here? > > > > jirka > > > > > > --- > > diff --git a/tools/perf/util/hist.c b/tools/perf/util/hist.c > > index 216388003dea..e65e6822c848 100644 > > --- a/tools/perf/util/hist.c > > +++ b/tools/perf/util/hist.c > > @@ -966,7 +966,7 @@ iter_add_next_cumulative_entry(struct hist_entry_iter *iter, > > .map = al->map, > > .sym = al->sym, > > }, > > - .srcline = al->srcline ? strdup(al->srcline) : NULL, > > + .srcline = al->srcline, > While this shouldn't leak the memory, we may end up with an al->srcline > to get free afterwards while still having a reference on it within the > hist_entry... Also I could not find where/how the hist_entry is freed up > so we may get an double free if both of al and he clean the srcline. > Of course, with your solution we could spare the useless strdup/free if > we find an hist_entry (which should be the typical case for hotspots..). > Taking a deeper look thus should be beneficial - but I do not have the > time for that right now because I'm still working on the inline-symbol > integration which is more important for me... ok, I'll check it jirka