linux-kernel - Re: [PATCH v6 05/10] nvmet: implement namespace identify descriptor list

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>] [day] [month] [year] [list]

Date:   Mon, 12 Jun 2017 18:19:24 +0200
From:   Christoph Hellwig <hch@....de>
To:     Chaitanya Kulkarni <Chaitanya.Kulkarni@....com>
Cc:     Johannes Thumshirn <jthumshirn@...e.de>,
        Sagi Grimberg <sagi@...mberg.me>,
        Keith Busch <keith.busch@...el.com>,
        Hannes Reinecke <hare@...e.de>,
        Max Gurtovoy <maxg@...lanox.com>,
        Linux NVMe Mailinglist <linux-nvme@...ts.infradead.org>,
        Linux Kernel Mailinglist <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v6 05/10] nvmet: implement namespace identify
        descriptor list

On Mon, Jun 12, 2017 at 03:33:11AM +0000, Chaitanya Kulkarni wrote:
> Right now I'm keeping the framework under "${KDIR}/tools/testing/selftests/", please let me know if that is not a desirable directory.

Heh, Johannes and I just had a discussion on the test framework
locations last weekend over a beer.

Both of us agree that a separate repository would be much preferable,
mostly due to two reasons:

 - it allows people that backport changes (e.g. distros) to always
   run the latests test suite without having to backport it as well,
   and have one test suite config for all branches
 - ease of running it from a VM or initramfs instead of having to
   download the whole kernel tree or copying things out

Last but not least it also seems a little easier to get started that
way.