linux-ext4 - Re: [PATCH linux-kselftest/test v2] ext4: add kunit test for decoding extended timestamps

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:   Thu, 17 Oct 2019 17:12:36 -0600
From:   Shuah Khan <skhan@...uxfoundation.org>
To:     Iurii Zaikin <yzaikin@...gle.com>
Cc:     "Theodore Y. Ts'o" <tytso@....edu>,
        Brendan Higgins <brendanhiggins@...gle.com>,
        "open list:KERNEL SELFTEST FRAMEWORK" 
        <linux-kselftest@...r.kernel.org>, linux-ext4@...r.kernel.org,
        adilger.kernel@...ger.ca,
        KUnit Development <kunit-dev@...glegroups.com>,
        "skh >> Shuah Khan" <skhan@...uxfoundation.org>
Subject: Re: [PATCH linux-kselftest/test v2] ext4: add kunit test for decoding
 extended timestamps

On 10/17/19 5:07 PM, Iurii Zaikin wrote:
>> Having the ability to take test data doesn't make it non-deterministic
>> though. It just means that if user wants to test with a different set
>> of data, there is no need to recompile the test. This could be helpful
>> to test cases the test write didn't think about.
>>
> Again, unit tests are not meant to be babysat. They are intended to become
> a part of the codebase and be run against every proposed change to ensure
> the change doesn't break anything.
> The whole process is supposed to be fully automated.
> Imagine a KUnit test run for all tests that gets kicked off as soon as a patch
> shows up in Patchwork and the maintainers getting the test run results.
> If you can think of a test that the change author didn't for a new corner case,
> then you as the maintainer ask the change author to add such test.
> Or if some corner case comes up as a result of a bug then the new case is
> submitted with the fix.
> This is how unit testing is deployed in the larger software world. In the most
> enlightened places a change will not be accepted unless it's accompanied by
> the unit tests that offer good coverage for the possible inputs and code paths.
> A change that breaks existing tests is either incorrect and has to be fixed or
> the existing tests need to be updated for the behavior change.
> 

Okay. I am asking for an option to override the test data. You didn't
address that part.

You can do all of this and allow users to supply another set of data.
It doesn't gave to be one or the other.

thanks,
-- Shuah