netdev - Re: [PATCH net-next 0/1] Introduction of the tc tests

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:   Tue, 20 Jun 2017 11:36:47 -0400 (EDT)
From:   David Miller <davem@...emloft.net>
To:     xiyou.wangcong@...il.com
Cc:     lucasb@...atatu.com, netdev@...r.kernel.org,
        stephen@...workplumber.org, jiri@...nulli.us, mrv@...atatu.com,
        jhs@...atatu.com
Subject: Re: [PATCH net-next 0/1] Introduction of the tc tests

From: Cong Wang <xiyou.wangcong@...il.com>
Date: Mon, 19 Jun 2017 21:13:31 -0700

> I thought tools/testing/selftests/ is mainly for those tests close to
> kernel ABI and API. What is the criteria for these tests? If any test
> can fit in, we somehow would merge the whole LTP...
> 
> I definitely don't object more tests, I am just wondering if we should
> put it to tools/testing/selftests/ or host it somewhere else.

I want it in the kernel so that it gets the level of exposure, care,
review, and use that the kernel does.

If you put it somewhere else it gets at least 10 times less of all
of those attributes.