linux-kernel - [PATCH 0/7] trace-cmd: Small fixes and cleanups on libparsevent

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-next>] [day] [month] [year] [list]

Date:	Mon,  9 Apr 2012 11:54:27 +0900
From:	Namhyung Kim <namhyung.kim@....com>
To:	Steven Rostedt <rostedt@...dmis.org>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Ingo Molnar <mingo@...nel.org>
Cc:	Arnaldo Carvalho de Melo <acme@...radead.org>,
	Borislav Petkov <bp@...en8.de>,
	David Ahern <dsahern@...il.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: [PATCH 0/7] trace-cmd: Small fixes and cleanups on libparsevent

Hi, all

This is a couple of small changes that I found during the flight back to
Korea :). While I'm not finished with reading the whole code, I send what
I have now in the hope that it'd help Frederic's unification work somewhat.
More might come later as I read the remaining parts.

The patch 01 is a workaround to build trace-cmd without installing swig
since I don't have an internet access at that time, so it's independent
to others and can go separately.

Thanks.


Namhyung Kim (7):
  trace-cmd: Add NO_PYTHON option for Makefile
  parse-events: Fix printk_cmp()
  parse-events: Introduce extend_token()
  parse-events: Handle strdup failure cases
  parse-events: Fix a possible memory leak
  parse-events: Handle realloc() failure path
  parse-events: Fix a possibly wrong memory dereference

 Makefile       |    2 +
 parse-events.c |  168 +++++++++++++++++++++++++++++++++++++++----------------
 2 files changed, 121 insertions(+), 49 deletions(-)

-- 
1.7.7.6

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