Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751438AbaJQW2S (ORCPT ); Fri, 17 Oct 2014 18:28:18 -0400 Received: from mx1.redhat.com ([209.132.183.28]:42550 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751158AbaJQW2R (ORCPT ); Fri, 17 Oct 2014 18:28:17 -0400 Date: Fri, 17 Oct 2014 19:27:59 -0300 From: Arnaldo Carvalho de Melo To: Jiri Olsa Cc: linux-kernel@vger.kernel.org, Andi Kleen , Corey Ashford , David Ahern , Frederic Weisbecker , Ingo Molnar , Namhyung Kim , Paul Mackerras , Peter Zijlstra Subject: Re: [PATCHv2 0/7] perf tools: Fix branch report segfaults Message-ID: <20141017222759.GA28763@redhat.com> References: <1413468427-31049-1-git-send-email-jolsa@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1413468427-31049-1-git-send-email-jolsa@kernel.org> X-Url: http://acmel.wordpress.com User-Agent: Mutt/1.5.20 (2009-12-10) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Em Thu, Oct 16, 2014 at 04:07:00PM +0200, Jiri Olsa escreveu: > hi, > adding some branch_info checks to prevent segfaults > on data without branch info. > > v2: using cmp_null as suggested by Namhyung Didn't notice this one, will try and put on next pull req, - Arnaldo > jirka > > available at: > git://git.kernel.org/pub/scm/linux/kernel/git/jolsa/perf.git > perf/abort_fix_2 > > Cc: Andi Kleen > Cc: Arnaldo Carvalho de Melo > Cc: Corey Ashford > Cc: David Ahern > Cc: Frederic Weisbecker > Cc: Ingo Molnar > Cc: Namhyung Kim > Cc: Paul Mackerras > Cc: Peter Zijlstra > Signed-off-by: Jiri Olsa > --- > tools/perf/util/sort.c | 102 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++--------------------- > 1 file changed, 76 insertions(+), 26 deletions(-) -- 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/