linux-kernel - Re: [RFC PATCH v1 0/9] Tests for sync infrastructure

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]

Message-ID: <56F92454.4060102@collabora.co.uk>
Date:	Mon, 28 Mar 2016 09:32:20 -0300
From:	Emilio López <emilio.lopez@...labora.co.uk>
To:	Shuah Khan <shuahkh@....samsung.com>
Cc:	devel@...verdev.osuosl.org,
	Gustavo Padovan <gustavo.padovan@...labora.co.uk>,
	Riley Andrews <riandrews@...roid.com>,
	Daniel Vetter <daniel.vetter@...ll.ch>,
	John Harrison <John.C.Harrison@...el.com>,
	linux-kernel@...r.kernel.org, dri-devel@...ts.freedesktop.org,
	Greg Hackmann <ghackmann@...gle.com>,
	Rob Clark <robdclark@...il.com>,
	linux-kselftest@...r.kernel.org,
	Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
	Daniel Stone <daniels@...labora.com>,
	Arve Hjønnevåg <arve@...roid.com>
Subject: Re: [RFC PATCH v1 0/9] Tests for sync infrastructure

Hi,

I somehow missed these emails back in the day, sorry for the delay in 
replying.

El 09/03/16 a las 13:13, Shuah Khan escribió:
> On 03/09/2016 08:28 AM, Emilio López wrote:
>> Hello everyone,
>>
>> This is a series of tests to exercise the sync kernel infrastructure. It is
>> meant to be a test suite for the work Gustavo has been doing to destage it,
>> see [0] for his latest series to date.
>>
>> These tests were originally part of a battery of tests shipping with
>> Android's libsync that were rewritten to use the new userspace interfaces.
>>
>> As usual, all comments are welcome.
>>
>> Cheers!
>> Emilio
>>
>> [0] https://lists.freedesktop.org/archives/dri-devel/2016-March/102204.html
>
> Good to see this suite added to Kselftest. Thanks for
> being thorough and including .gitignore.
>
> Are there any destructive and/or longer time tests
> in this suite. If so could you please make them
> optional to run. Please see selftests/timers as an
> example for excluding.

As far as I know they shouldn't destroy anything. The full sync suite 
runs in under 5 seconds on my virtualized setup; we can make the stress 
tests optional if that's too long a time, what do you think?.

Cheers,
Emilio