linux-kernel - Where to put test code?

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

Date:	Wed, 19 Sep 2012 16:52:43 -0500
From:	Daniel Santos <danielfsantos@....net>
To:	LKML <linux-kernel@...r.kernel.org>
Subject: Where to put test code?

I'm putting the finishing touches on the generic red-black tree test
code, but I'm uncertain about where to place it exactly.

I haven't finished the test module just yet, but the idea is that the
tests can be run in userspace as well as kernelspace to make it easier
to test on multiple compilers.  It has some common sources files (used
by in both places) and then specific code for both user- and
kernel-space that I currently have as follows:

tools/testing/selftests/grbtree/       - common.{c,h}
tools/testing/selftests/grbtree/user   - user-space main.c, Makefile, etc.
tools/testing/selftests/grbtree/module - kernel-space grbtest.c,
Makefile, etc.

Would this be correct or should the common & module code go some place
else and then just have the user-space code under
tools/testing/selftests/grbtest?

Thanks
Daniel

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/