linux-kernel - Re: [PATCH 00/22] perf tools: Backport of latest changes on trace-cmd's libparseevent

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 23 May 2012 21:08:10 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Namhyung Kim <namhyung.kim@....com>
Cc:	Arnaldo Carvalho de Melo <acme@...stprotocols.net>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Paul Mackerras <paulus@...ba.org>,
	Ingo Molnar <mingo@...hat.com>,
	Namhyung Kim <namhyung@...il.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Frederic Weisbecker <fweisbec@...il.com>
Subject: Re: [PATCH 00/22] perf tools: Backport of latest changes on
 trace-cmd's libparseevent

On Wed, 2012-05-23 at 11:36 +0900, Namhyung Kim wrote:
> Hi,
> 
> This is a patchset which attempts to sync what we have on trace-cmd
> into libtraceevent. Although some patch introduced new call-sites of
> die() or malloc_or_die(), it'll be removed eventually (or later work)
> and this helps marking the every locations that we need to track.

Thanks Namhyung!

I would recommend that this patch set be queued for 3.6, with the
following being cherry-picked for 3.5:

 patch 5, 10, 12, 13, 14, 15, 19, and 21

Some of the other patches have fixes for failed allocation. As these
bugs have been around in current perf since forever, they can probably
wait another release before being added. It's not like it will cause the
kernel to crash ;-)

-- Steve


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/