Aren
/
NetBSD
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
NetBSD/tests/lib/libc/sys/Makefile

71 lines
1.4 KiB
Makefile
Raw Normal View History

Add a test for PR/45618: Motoyuki OHMORI: kqueue EVFILT_TIMER with smaller timeout value makes kernel busy or panic
2011-11-17 05:14:12 +04:00
# $NetBSD: Makefile,v 1.20 2011/11/17 01:14:12 christos Exp $
test for sigqueue
2011-01-10 07:57:56 +03:00
MKMAN= no
.include <bsd.own.mk>
Add a simple test case to check executable mapping rights for mprotect(2). - provide an exec_prot_support() routine so $ARCH can indicate whether it supports execution protection or not, and skip test accordingly. - have a trivial 'return_one' shellcode to copy anywhere in a page, and call it. The decision to keep the assembly solution is mine, reasons are twofold: - all pure-C implementations cannot be controlled easily: bounds detection (beginning/end) of return_one is unpredictable, or requires the use of overkill solutions like libelf. Using dlsym(3) was a good proposal, however I can't use it to know the end address of the payload. It makes copying of the shellcode a bit more difficult: using a constant may be too small (code has not been entirely copied, and can lead to errors that can be erroneously detected as "test passed"), or too big (depending on where it is mapped in memory, copying past the end of the function may trigger SIGSEGV). - I have to ensure that the resulting assembly is the most compact possible, especially as it will be reused to test other parts of memory (stack, data, rodata, etc.). Only i386 and amd64 are implemented so far. Others will come in due time. FWIW, writing the exec_prot_support() callback and the return_one payload should be enough. Writing callback requires good knowledge of the platform, depending on chip revision, CPU, board, MMU... the protection level may vary. Current files are put under lib/libc/arch/* and lib/libc/common/. Feel free to move them around the tests/ tree. Keep in mind that the common/ and arch/ code will be used outside of libc, so please do not hide them too deep in the tree. I checked a few architectures via build.sh cross-compile, and will keep an eye on buildbot for potential build breakage. Feel free to contact me in case you see any, of course.
2011-07-19 03:16:08 +04:00
.include "../arch/Makefile.exec_prot"
test for sigqueue
2011-01-10 07:57:56 +03:00
TESTSDIR= ${TESTSBASE}/lib/libc/sys
Add the syscall tests back. Couple of files and tests were also renamed for consistency. All of these now mimic the libc structure.
2011-07-07 10:57:53 +04:00
TESTS_C+= t_access
TESTS_C+= t_chroot
Move the clock_gettime(2) timer test to the right place.
2011-10-15 10:42:16 +04:00
TESTS_C+= t_clock_gettime
Continuing the (re)organization of the lib/libc atf regression tests
2011-01-13 05:40:43 +03:00
TESTS_C+= t_clone
Move connect(2), listen(2) and socketpair(2) tests to the right place.
2011-11-05 22:19:01 +04:00
TESTS_C+= t_connect
Add the syscall tests back. Couple of files and tests were also renamed for consistency. All of these now mimic the libc structure.
2011-07-07 10:57:53 +04:00
TESTS_C+= t_dup
TESTS_C+= t_fsync
Remove 't_cerror' (this is tested by numerous individual tests). Rename 't_context' to 't_getcontext' for consistency.
2011-07-07 11:06:21 +04:00
TESTS_C+= t_getcontext
Add the syscall tests back. Couple of files and tests were also renamed for consistency. All of these now mimic the libc structure.
2011-07-07 10:57:53 +04:00
TESTS_C+= t_getgroups
TESTS_C+= t_getitimer
TESTS_C+= t_getlogin
TESTS_C+= t_getpid
TESTS_C+= t_getrusage
TESTS_C+= t_getsid
TESTS_C+= t_gettimeofday
TESTS_C+= t_issetugid
Add a test for PR/45618: Motoyuki OHMORI: kqueue EVFILT_TIMER with smaller timeout value makes kernel busy or panic
2011-11-17 05:14:12 +04:00
TESTS_C+= t_kevent
Add the syscall tests back. Couple of files and tests were also renamed for consistency. All of these now mimic the libc structure.
2011-07-07 10:57:53 +04:00
TESTS_C+= t_kill
TESTS_C+= t_link
Move connect(2), listen(2) and socketpair(2) tests to the right place.
2011-11-05 22:19:01 +04:00
TESTS_C+= t_listen
Add the syscall tests back. Couple of files and tests were also renamed for consistency. All of these now mimic the libc structure.
2011-07-07 10:57:53 +04:00
TESTS_C+= t_mincore
Move the mkdir(2) test to the right place.
2011-10-15 10:26:33 +04:00
TESTS_C+= t_mkdir
Add the syscall tests back. Couple of files and tests were also renamed for consistency. All of these now mimic the libc structure.
2011-07-07 10:57:53 +04:00
TESTS_C+= t_mkfifo
TESTS_C+= t_mknod
TESTS_C+= t_mmap
TESTS_C+= t_mprotect
Add 21 unit tests for the XSI message queues.
2011-11-05 11:45:40 +04:00
TESTS_C+= t_msgctl
TESTS_C+= t_msgget
TESTS_C+= t_msgrcv
TESTS_C+= t_msgsnd
Add the syscall tests back. Couple of files and tests were also renamed for consistency. All of these now mimic the libc structure.
2011-07-07 10:57:53 +04:00
TESTS_C+= t_msync
TESTS_C+= t_nanosleep
Move the pipe(2) test to the right place.
2011-10-15 10:17:02 +04:00
TESTS_C+= t_pipe
Move all pipe2 tests to a separate file.
2011-10-31 19:41:31 +04:00
TESTS_C+= t_pipe2
Move the posix_fadvise(2) test to the right place.
2011-10-15 10:10:26 +04:00
TESTS_C+= t_posix_fadvise
Add the syscall tests back. Couple of files and tests were also renamed for consistency. All of these now mimic the libc structure.
2011-07-07 10:57:53 +04:00
TESTS_C+= t_poll
TESTS_C+= t_revoke
TESTS_C+= t_select
TESTS_C+= t_setrlimit
TESTS_C+= t_setuid
Move the sigaction(2) test to the right place.
2011-10-15 11:00:48 +04:00
TESTS_C+= t_sigaction
Make sure we build all of thests, not just the last one (use += vs =)
2011-01-13 06:09:54 +03:00
TESTS_C+= t_sigqueue
Move connect(2), listen(2) and socketpair(2) tests to the right place.
2011-11-05 22:19:01 +04:00
TESTS_C+= t_socketpair
Add the syscall tests back. Couple of files and tests were also renamed for consistency. All of these now mimic the libc structure.
2011-07-07 10:57:53 +04:00
TESTS_C+= t_stat
TESTS_C+= t_timer_create
TESTS_C+= t_truncate
Move the ucontext(2) test to the right place.
2011-10-15 10:54:52 +04:00
TESTS_C+= t_ucontext
Add the syscall tests back. Couple of files and tests were also renamed for consistency. All of these now mimic the libc structure.
2011-07-07 10:57:53 +04:00
TESTS_C+= t_umask
TESTS_C+= t_unlink
Move the writev(2) test to the right place.
2011-10-15 10:50:52 +04:00
TESTS_C+= t_write
Add the syscall tests back. Couple of files and tests were also renamed for consistency. All of these now mimic the libc structure.
2011-07-07 10:57:53 +04:00
Add a simple test case to check executable mapping rights for mprotect(2). - provide an exec_prot_support() routine so $ARCH can indicate whether it supports execution protection or not, and skip test accordingly. - have a trivial 'return_one' shellcode to copy anywhere in a page, and call it. The decision to keep the assembly solution is mine, reasons are twofold: - all pure-C implementations cannot be controlled easily: bounds detection (beginning/end) of return_one is unpredictable, or requires the use of overkill solutions like libelf. Using dlsym(3) was a good proposal, however I can't use it to know the end address of the payload. It makes copying of the shellcode a bit more difficult: using a constant may be too small (code has not been entirely copied, and can lead to errors that can be erroneously detected as "test passed"), or too big (depending on where it is mapped in memory, copying past the end of the function may trigger SIGSEGV). - I have to ensure that the resulting assembly is the most compact possible, especially as it will be reused to test other parts of memory (stack, data, rodata, etc.). Only i386 and amd64 are implemented so far. Others will come in due time. FWIW, writing the exec_prot_support() callback and the return_one payload should be enough. Writing callback requires good knowledge of the platform, depending on chip revision, CPU, board, MMU... the protection level may vary. Current files are put under lib/libc/arch/* and lib/libc/common/. Feel free to move them around the tests/ tree. Keep in mind that the common/ and arch/ code will be used outside of libc, so please do not hide them too deep in the tree. I checked a few architectures via build.sh cross-compile, and will keep an eye on buildbot for potential build breakage. Feel free to contact me in case you see any, of course.
2011-07-19 03:16:08 +04:00
SRCS.t_mprotect= t_mprotect.c ${SRCS_EXEC_PROT}
Add the syscall tests back. Couple of files and tests were also renamed for consistency. All of these now mimic the libc structure.
2011-07-07 10:57:53 +04:00
LDADD.t_getpid+= -lpthread
Move the posix_fadvise(2) test to the right place.
2011-10-15 10:10:26 +04:00
LDADD.t_posix_fadvise+= -lrumpvfs -lrump -lrumpuser -lpthread
Add the syscall tests back. Couple of files and tests were also renamed for consistency. All of these now mimic the libc structure.
2011-07-07 10:57:53 +04:00
WARNS= 4
test for sigqueue
2011-01-10 07:57:56 +03:00
.include <bsd.test.mk>