linux-kernel - Re: [PATCH v3 3/3] lib/test_crc: Add test cases for crc calculation

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: <CADfjVrg_oe1d5+3Hr3dv5fVpcA9jYP44B24LJS2_OsUFpnyB5g@mail.gmail.com>
Date:   Wed, 18 Jul 2018 14:30:27 -0400
From:   Noah Massey <noah.massey@...il.com>
To:     andy.shevchenko@...il.com
Cc:     Coly Li <colyli@...e.de>, linux-kernel@...r.kernel.org,
        linux-bcache@...r.kernel.org, linux-block@...r.kernel.org,
        gregkh@...uxfoundation.org, torvalds@...ux-foundation.org,
        tglx@...utronix.de, kstewart@...uxfoundation.org
Subject: Re: [PATCH v3 3/3] lib/test_crc: Add test cases for crc calculation

On Tue, Jul 17, 2018 at 4:59 PM Andy Shevchenko
<andy.shevchenko@...il.com> wrote:
> On Tue, Jul 17, 2018 at 9:51 PM, Noah Massey <noah.massey@...il.com> wrote:
> > On Tue, Jul 17, 2018 at 10:56 AM Coly Li <colyli@...e.de> wrote:
>
> >> +       if (err == 0)
> >> +               pr_info("test_crc: all %d tests passed\n", i);
> >
> > Similar to previous comment: we should not report the number of passed
> > tests, since adding a test would invalidate previous golden output.
> > Also, consider the situation where some tests are conditionally
> > executed depending on kconfig.
>
> We do similar in many test modules and I know at least two that had
> been changed in order to get new test cases.
> Are you proposing to change 'em all?
>

I was proposing that the message should be "test_crc: all tests
passed\n", since that would maintain a static expected output. Upon
further review, parsing minor variations in the messages is simple
enough so if the automated test tools already handle it keeping the
test count in the output is better.

Sorry for the noise,

~ Noah