linux-kernel - Re: [PATCH] ftracetest: Do not use usleep

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:	Mon, 30 Mar 2015 14:47:41 -0600
From:	Shuah Khan <shuahkh@....samsung.com>
To:	Steven Rostedt <rostedt@...dmis.org>
CC:	Namhyung Kim <namhyung@...nel.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Michael Ellerman <mpe@...erman.id.au>,
	Dave Jones <davej@...emonkey.org.uk>,
	Luis Henriques <luis.henriques@...onical.com>
Subject: Re: [PATCH] ftracetest: Do not use usleep

On 03/25/2015 06:32 PM, Namhyung Kim wrote:
> The usleep is only provided on distros from Redhat so running ftracetest
> on other distro resulted in failures due to the missing usleep.
> 
> The reason of using [u]sleep in the test was to generate (scheduler)
> events. But as we use 'cat trace | grep | wc -l' to read the events,
> the command themselves already generate some events before reading the
> trace file so no need to call [u]sleep explicitly.
> 
> Reported-by: Michael Ellerman <mpe@...erman.id.au>
> Reported-by: Dave Jones <davej@...emonkey.org.uk>
> Reported-by: Luis Henriques <luis.henriques@...onical.com>
> Tested-by: Michael Ellerman <mpe@...erman.id.au>
> Signed-off-by: Namhyung Kim <namhyung@...nel.org>
> ---

Hi Steve,

I will pull this in for 4.1. Assume that is ok. Just confirming.

thanks,
-- Shuah


-- 
Shuah Khan
Sr. Linux Kernel Developer
Open Source Innovation Group
Samsung Research America (Silicon Valley)
shuahkh@....samsung.com | (970) 217-8978
--
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/