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] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 18 Mar 2013 22:32:07 +0100
From:	Frederic Weisbecker <fweisbec@...il.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	LKML <linux-kernel@...r.kernel.org>,
	Stanislaw Gruszka <sgruszka@...hat.com>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Steven Rostedt <rostedt@...dmis.org>
Subject: Re: [PATCH 4/4] selftests: Add basic posix timers selftests

2013/3/18 Andrew Morton <akpm@...ux-foundation.org>:
> On Fri, 15 Mar 2013 17:54:02 +0100 Frederic Weisbecker <fweisbec@...il.com> wrote:
>
>> Add some initial basic tests on a few posix timers
>> interface such as setitimer() and timer_settime().
>>
>> These simply check that expiration happens in a reasonable
>> timeframe after expected elapsed clock time (user time,
>> user + system time, real time, ...).
>>
>> This is helpful for finding basic breakages while hacking
>> on this subsystem.
>>
>> ...
>>
>>  tools/testing/selftests/timers/Makefile       |    8 +
>
> I wonder if this should be tools/testing/posix-timers/, to leave room
> in the namespace for other varieties of timer.

In fact I called it timers/ on purpose such that some more timers
related selftests can be added and gathered in the future. But I don't
mind if we keep very single purpose directories like
tools/testing/posix-timers/
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ