linux-kernel - Re: [tip:perf/core] perf script/python: Print array argument as string

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]

Date:	Thu, 26 Jun 2014 21:22:58 +0200
From:	Jiri Olsa <jolsa@...hat.com>
To:	Sebastian Andrzej Siewior <bigeasy@...utronix.de>
Cc:	mingo@...nel.org, hpa@...or.com, linux-kernel@...r.kernel.org,
	tzanussi@...il.com, jolsa@...nel.org, namhyung@...nel.org,
	tglx@...utronix.de, linux-tip-commits@...r.kernel.org
Subject: Re: [tip:perf/core] perf script/python: Print array argument as
 string

On Thu, Jun 26, 2014 at 05:37:27PM +0200, Sebastian Andrzej Siewior wrote:
> On 06/12/2014 02:01 PM, tip-bot for Namhyung Kim wrote:
> 
> > Commit-ID:  e646fe730a324098a718f1c9b2f349efb99d5457
> > Gitweb:     http://git.kernel.org/tip/e646fe730a324098a718f1c9b2f349efb99d5457
> > Author:     Namhyung Kim <namhyung@...nel.org>
> > AuthorDate: Thu, 29 May 2014 13:44:55 +0900
> > Committer:  Jiri Olsa <jolsa@...nel.org>
> > CommitDate: Mon, 9 Jun 2014 12:21:03 +0200
> > 
> > perf script/python: Print array argument as string
> > 
> > With the Sebastian's change of handling num array argument (of raw
> > syscall enter), the script still failed to work like this:
> 
> This patch got merged. It fixes something that was introduced by
>   "perf script: move the number processing into its own function" [0]
>   "perf script: handle the num array type in python properly" [1]
> 
> which was not yet merged.

yea, we are fast.. fixing bugs even before making them ;-)

I'll check/queue those 2

thanks,
jirka
--
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/