linux-kernel - Re: [PATCH] perf tool: save cmdline from user in file header vs what is passed to record

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

Message-ID: <4FF71E0E.8010602@gmail.com>
Date:	Fri, 06 Jul 2012 11:19:10 -0600
From:	David Ahern <dsahern@...il.com>
To:	Arnaldo Carvalho de Melo <acme@...stprotocols.net>
CC:	linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...nel.org>,
	Jiri Olsa <jolsa@...hat.com>,
	Namhyung Kim <namhyung@...il.com>,
	Stephane Eranian <eranian@...gle.com>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Peter Zijlstra <peterz@...radead.org>
Subject: Re: [PATCH] perf tool: save cmdline from user in file header vs what
 is passed to record

On 7/6/12 11:17 AM, Arnaldo Carvalho de Melo wrote:
> Can you please state for what branch, perf/urgent (i.e. current merge
> window) or perf/core (next), this is intended? I usually have been
> making the call, but having feedback from the submitter can help things
> and help meet expectations more frequently.
>
> I'd say this one should be for perf/core, as it is not so critical, what
> do you think?

right, need to add that tag. It's not a regression, just an oversight on 
the original implementation. perf/core is the right branch.

David


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