From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753012AbdA3JN6 (ORCPT ); Mon, 30 Jan 2017 04:13:58 -0500 Received: from mx1.redhat.com ([209.132.183.28]:55988 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752101AbdA3JMo (ORCPT ); Mon, 30 Jan 2017 04:12:44 -0500 Date: Mon, 30 Jan 2017 10:01:59 +0100 From: Jiri Olsa To: Taeung Song Cc: Arnaldo Carvalho de Melo , linux-kernel@vger.kernel.org, Jiri Olsa , Namhyung Kim , Ingo Molnar , Peter Zijlstra , Wang Nan Subject: Re: [PATCH 1/2] perf tools: Use zfree() instead of free() in parse-events.c Message-ID: <20170130090159.GC22029@krava> References: <1485753819-12857-1-git-send-email-treeze.taeung@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1485753819-12857-1-git-send-email-treeze.taeung@gmail.com> User-Agent: Mutt/1.7.1 (2016-10-04) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.28]); Mon, 30 Jan 2017 09:02:03 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jan 30, 2017 at 02:23:38PM +0900, Taeung Song wrote: > Currently there are several parts not checking NULL > after allocating with zalloc() or asigning NULL value > to a pointer variable after doing free(). > > So I fill in code checking NULL and > use zfree() instead of free(). can't see directly reasons for zfree usage, but it looks reasonable.. do you have any crash reports due to missing zfree? thanks, jirka