linux-kernel - Re: [PATCH] perf tools: Fix an error on perf-bench document

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: <CAMO-S2g+cuv85XBfTQJTjwp4GcwT2WivLHD9X_gca67TFCBGgQ@mail.gmail.com>
Date:	Mon, 2 Jul 2012 00:05:59 +0900
From:	Hitoshi Mitake <h.mitake@...il.com>
To:	Namhyung Kim <namhyung@...nel.org>
Cc:	Ingo Molnar <mingo@...nel.org>,
	Arnaldo Carvalho de Melo <acme@...stprotocols.net>,
	Ingo Molnar <mingo@...hat.com>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] perf tools: Fix an error on perf-bench document

On Thu, Jun 28, 2012 at 10:56 AM, Namhyung Kim <namhyung@...nel.org> wrote:
> On Wed, 27 Jun 2012 23:28:22 +0900, Hitoshi Mitake wrote:
>> I wrote the simple fix for eliminatng wrong usage of "clock":
>> https://github.com/mitake/linux/commit/b7836d41deff430c16058ca729120dccfa41e74e
>>
>> This patch assumes the change made by the Namhyung's patch. So I'm
>> planning to send this after the Namhyung's patch is applied to tip
>> tree. Or should the patches be unified before applied?
>
> The patch is now in Arnaldo's tree. So you can see it in tip tree soon
> unless something bad happens.
>
> Anyway, looking at your commit (I think it's better just to send it via
> email with mentioning the dependency), it seems only addresses memset
> part but I think memcpy has the same problem, right?

Thanks for your pointing. I had to fix the problem of memcpy too.
I'll send the new patch later.


-- 
Hitoshi Mitake
h.mitake@...il.com
--
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/