linux-kernel - Re: [PATCH 22/28] tools lib traceevent: Remove malloc_or

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 for Android: free password hash cracker in your pocket

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

Date:	Wed, 4 Dec 2013 08:51:50 -0500
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Arnaldo Carvalho de Melo <acme@...stprotocols.net>
Cc:	Jiri Olsa <jolsa@...hat.com>, linux-kernel@...r.kernel.org,
	Corey Ashford <cjashfor@...ux.vnet.ibm.com>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Ingo Molnar <mingo@...e.hu>,
	Namhyung Kim <namhyung@...nel.org>,
	Paul Mackerras <paulus@...ba.org>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	David Ahern <dsahern@...il.com>
Subject: Re: [PATCH 22/28] tools lib traceevent: Remove malloc_or_die from
 event-plugin.c

On Wed, 4 Dec 2013 10:29:32 -0300
Arnaldo Carvalho de Melo <acme@...stprotocols.net> wrote:


> Yeah, I also have some reservations about adding more globals (the
> trace_event stuff just to associate a plugins list with pevent, probably
> pevent should have that list, haven't looked 100% at the code), but in
> general probably this patchset is OK, I think we should take it in and
> then address those other problems in a followup patchset, d'accord?

Yep, agreed. If we can associate it to the pevent descriptor then that
would be best.

Yes, take this in now, and we can address the other issues in a
followup. But these issues need to be addressed before we make the
libtraecevent library public.

-- 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/