1) Log Message:
These tests were contributed by the timerfd() syscall developer Davide Libenzi <firstname.lastname@example.org>.
2) Log Message:
CPU and MEMORY HOTPLUG test cases picked up from http://devresources.linux-foundation.org/dev/hotplug/
3) Log Message:
This patch fix a concurrency issue in mremap04. The tmp directory the IPC key was build with was destroyed before we destroy the IPC ressource attached to the key. In case of concurency, the same inode id can be reused for another process tmp dir, leading to the generation of the same key. Renaud Lottiaux <Renaud.Lottiaux@kerlabs.com>.
4) Log Message:
I spent some time looking at the sched_latency test trying to see why it took so long to start the thread. The java version of the test takes a comparable amount of time to start the thread as it does for each period. The rt-test version was taking an order of magnitude longer. After digging through the java documentation, I found that the RealtimeThread does not actually start executing until the RealtimeThread.waitForNextPeriod() fulfills the time specified in the PeriodicParameters parameter included in its constructor. So all the tests are scheduled to run about 1 second after the threads are created. This gives the system plenty of time to create the thread (a non-realtime code path), set the scheduling parameters and then sleep until the specified run time. The start latency as measured by the test goes something like this:
start_time = nanoTime() + 1000000000;
rt = new realtimeThread(sched_param, new \ PeriodicParameters(start_time, ...), ..., run);
/* by the rtsj specification, this method will not run until start_time */
now = nanoTime();
start_latency = now - start_time;
The rt-tests version went something like this:
start_time = rt_gettime();
create_fifo_thread(periodic_thread, (void*)0, PRIO);
now = rt_gettime();
start_latency = now - start;
As you can see, the start_latency is a very different measurement in these two cases. In the first, it is basically the initial starting latency as measured by the remainder of the loops. In the second, the execution path of creating the pthread is also counted in the latency. While this might be an important number for us to keep low in our testing, this is not what the java test is measuring. This patch puts the rt-test version in line with the java version. I also think this is reasonable since the rt-wiki says that we should _NEVER_ create threads on the real-time stage. Signed-off-by: Vernon Mauery <email@example.com>.
5) Log Message:
The following patches fix execve05 for error reporting when execve() succeeds, and exit synchronization in loaded systems. The last two patches are minor cleanups. execve05 checks that execve() fails if a process has opened the file with write access. However, in case the test fails and execve() succeeds, the default binary (test3) has return code 0, which is interpreted as test success. We get output like that:
with return code 0 (success)
execve05 1 FAIL : Failures reported above
with return code matching FAIL.
This patch simply changes the success return code from 0 to 3, so that execve() success, and thus test failure, can be properly reported. Signed-off-by: Louis Rilling <Louis.Rilling@kerlabs.com>.
6) Log Message:
The following patches fix execve05 for error reporting when execve() succeeds, and exit synchronization in loaded systems. The last two patches are minor cleanups. In execve05, the first child must keep a file open at least until the second child tries to execve() this file. However the test achieves this with a sleep of 10s, which may fail on loaded systems. This patch replaces this (arbitrary) sleep with a pipe-based synchronization, where the parent notifies the first child once the second child has terminated. Signed-off-by: Louis Rilling <Louis.Rilling@kerlabs.com>.
7) Log Message:
The following patches fix execve05 for error reporting when execve() succeeds, and exit synchronization in loaded systems. The last two patches are minor cleanups. In a child, calling waitpid() to wait for the death of sibling child is simply non-sense. Moreover in execve05, the second child does not need such synchronization. Remove it. Signed-off-by: Louis Rilling <Louis.Rilling@kerlabs.com>.
8) Log Message:
The following patches fix execve05 for error reporting when execve() succeeds, and exit synchronization in loaded systems. The last two patches are minor cleanups. cleanup() is reserved for the main test process. In children, call exit() instead. Signed-off-by: Louis Rilling <Louis.Rilling@kerlabs.com>.
9) Log Message:
This patch fix an issue in the sync_pipe implementation. The problem is the following : after the creation of a pipe we do not close any file descriptor until the end of a test. Let's imagine the following execution :
- Process A calls sync_pipe_create
- Process A do a fork (creation of process B)
- Process A calls sync_pipe_wait
---> Process A blocks on sync_pipe_wait
- Process B starts
- Process B exits because of an early error.
In this case, process A never exits. Since it has not closed its write descriptor to the pipe, the pipe is not considered as broken, thus process A is not notified its son is dead. Thus it will wait forever. Renaud Lottiaux <Renaud.Lottiaux@kerlabs.com>.
10) Log Message:
This patch fixes a compilation warning due to the function "sync_pipe_close" which was not exported. Renaud Lottiaux <Renaud.Lottiaux@kerlabs.com>.
11) Log Message:
After the patch from Roy moveing the libtestsuite code from /testcases/kernel/syscalls/lib to /lib, the code in the old directory has not been removed. Moreover, include PATH in some makefile was still pointing to this old directory. This patch remove libtestsuite code from the old directory and remove deprecated references to this old dir in some Makefiles. Renaud Lottiaux <Renaud.Lottiaux@kerlabs.com>.
12) Log Message:
time-schedule01 failed, because it sent SIGTERM to itself before program exited, so the return value is not 0. This patch makes the main process ignore SIGTERM. Li Zefan <firstname.lastname@example.org>.
13) Log Message:
This patch fix the make file of fs_bin test case so that it can be cross-built. Roy Lee <email@example.com>.
14) Log Message:
Add syscall numbers for timerfd syscalls under i386 and x86_64. Roy Lee <firstname.lastname@example.org>.
15) Log Message:
Currently, timerfd01 test case blocks building process for architectures that haven’t prepared for it. This patch modify it to be more generic for all architectures. Roy Leee <email@example.com>.
16) Log Message:
It looks like the only thing that didn't apply was the function declaration. It builds (with a warning) and runs just fine. But here is a patch to fix the warning. Signed-off-by: Vernon Mauery <firstname.lastname@example.org>.
17) Log Message:
utimensat() syscall was introduced from linux-2.6.22 onwards. Michael wrote the initial testcases, and, the same is being contributed to LTP under GPLv2. I worked out a patch for this. Though this is not using LTP specific libraries at the moment. But the tests run well and tests 99 separate variations. Michael has written it through itś length and breadth. I generated the code coverage (9.2%) over 2.6.25-gcov kernel, which however was not built with <make allmodconfig> option. Please see it attached along with a draft man page of utimensat(), created by Michael. Let us know how do you feel about this test. We can then go ahead and add this to LTP. Signed-off-by Michael Kerrisk <email@example.com>. Signed-off-by: Subrata Modak <firstname.lastname@example.org>.
18) Log Message:
On ia64, __clone2() is used instead of clone(). Signed-off-by: Li Zefan <email@example.com>.
19) Log Message:
I execute fork12 test and OMM killer begin send SIGKILL to its children and fork return success always. fork12 hang up in this case, so I create the patch (see attach), which check whether someone child killed and if it occur, return number of forked processes. Andrew Vagin <firstname.lastname@example.org>.
20) Log Message:
This patch fixes the writetest.c to return proper status on Failure/Success. At present the return code of the writest.c is 'zero' for both Success and Failure. As per norms non-zero value should be returned for error , so fixing this testcase. Signed off : Veerendra C <email@example.com>.
21) Log Message:
mallocstress stresses the VMM and C library by spawning N threads which malloc blocks of increasing size until malloc returns NULL. It occur because test doesn't wait for all thread started. already started threads begin allocate memory, so pthread_create can return ENOMEM. my patch added this synchronizing. I use semaphore, because it can wait-for-zero unlike pthread_mutex. sorry, forgot set permission in semget, new patch attached. Andrew Vagin <firstname.lastname@example.org>.
22) Log Message:
Reverting back the changes done to fcntl-lock tests in May 2008 release, as this would have canceled the operation Revision *1.1 *done on the /Mon Sep 11 20:40:52 2006 UTC/ by /mreed10 /which added "A patch that added new functionality into the NFSvf lock tests.
-adds the capability to stress a server with multiple clients"
So it is possible to get back to what 's in ltp-full-20080430 and add my fix: You can fix it by replacing in the locktests.c file
Signed-off-by: Le Rouzic <email@example.com>.
23) Log Message:
In the manpage for tst_res(3) in the April snapshot it says...
tst_brk - Print result message and break remaining test cases
tst_brkm - Print result message, including file contents, and break remaining test cases
... at the top of the page. The prototypes and the logic is backwards for the summaries. A patched manpage is provided. Garrett Cooper <firstname.lastname@example.org>.
24) Log Message:
Force the catch_sighup to be volatile in order to overcome an issue due to the compiler optimization. In fact, compiling the test with -Os the catch_sighup variable is not set to 1 into the signal handler. At runtime, the test remain in a loop. No problem compiling without Os or O2.
Signed-off-by: Giuseppe Cavallaro <email@example.com>,
Signed-off-by: Carmelo Amoroso <firstname.lastname@example.org>.
25) Log Message:
Fix a bug in the sigiotask test and enable the test_fdreceive policy to build against the latest refpolicy headers. Signed-off-by: Stephen Smalley <email@example.com>.
26) Log Message:
Included the statement:
These tests are OSDL/LF and imported into LTP under GPLv2.
27) Log Message:
This patch ensures that async_handler and async_handler_jk runs by default. Also the profile/default is updated to reflect the same. Signed-Off-By: Chirag <firstname.lastname@example.org>.
28) Log Message:
Looks like the else is missing since in both the cases where flag is set to one or not we get the test broken print. Signed-off-by: Max Stirling <email@example.com>.
29) Log Message:
we have some truble with mapping api functions (such as tst_exit) in bash (./tools/apicmds/ltpapicmd.c). Now this problem may be fixed if added "exit" after tst_exit, but it's temporary. We should redesign this system and describe it in documentation. Andrew Vaggin <firstname.lastname@example.org>.
30) Log Message:
signal_test_01 failed on ia64, the following message outputed:
ERROR [line: 146] sigaltstack failed: Cannot allocate memory
: Cannot allocate memory
signal_test_01: IPC Signals TestSuite program
And, i found the defined macro STACKSIZE is short on ia64. This patch fix it. Signed-off-by: Shi Weihua <email@example.com>.
31) Log Message:
signal_test_05 failed on ia64 and x86_64, the following message outputed:
ERROR [line: 145] child process exited abnormally
Some signals which are ignored in ignore_signals() are not ignored in child(). e.g., 32, 33. (SIGRTMIN is 34). So we should reuse ignore_signals()'s signal ignoring code in child(). Signed-off-by: Shi Weihua <firstname.lastname@example.org>.
32) Log Message:
Updating to include info about all other LTP man pages. Subrata Modak <email@example.com>
33) Log Message:
I've ported a testcase for gettid() from crackerjack to ltp. I've added a directory ltp/testcases/kernel/syscalls/gettid. Signed-off-by: Masatake YAMATO <firstname.lastname@example.org>
34) Log Message:
I found wrong format string usage in ltp/testcases/kernel/syscalls/exit/exit02.c: returned value from strerror is not used. Signed-off-by: Masatake YAMATO <email@example.com>.
35) Log Message:
This patch fix a concurrency issue in semctl06. The IPC keys used for this test could conflict with keys from another task. Signed-off-by: Matthieu Fertré <firstname.lastname@example.org>.
36) Log Message:
The attached patch was necessary in order to get LTP to build for our embedded system at work. Without this patch testcases that use the my_getpwnam() library function suffer from redeclaration errors. Signed-off-by: Matt Fleming <email@example.com>.
37) Log Message:
Addition of enhanced test plan by Cai Qian <firstname.lastname@example.org>.
38) Log Message:
Fixed the way how to run the "tc" command on the remote machine. Otherwise, we always get the following message on the local side: The remote host does not have netem functionality. Signed-off-by: Giuseppe Cavallaro@st.com.
39) Log Message:
Running the UDP network stress tests on my SH4 target I have had to modify the following scripts: killall_udp_traffic and udp4-multi-diffip01. It deletes the address before setting it to avoid the following error: RTNETLINK answers: File exists; it implies that the test fails. Signed-off-by: Giuseppe Cavallaro <email@example.com>.
40) Log Message:
This modifies the command sent to the remote host just to kill the ns-udpclient script. Indeed, it seems that the previous string always returns 1. Moreover, it adds a new check to verify if the return value is not empty. It could happen, for example, if the RSH returns sometime the following error: poll: protocol failure in circuit setup. Signed-off-by: Giuseppe Cavallaro <firstname.lastname@example.org>.
41) Log Message:
Attached a new patch just to add the same fixes I provided you for icpm and tcp network stress as well. On SH4 STB with STLinux distribution we are able to run all the network stress tests without any failures. Due to configuration issues we do not run the multi-diffnic tests (because they require plural Network cards for host). It modifies the command sent to the remote host to kill tcp/icmp clients. It also deletes the address before setting it to avoid the following error: "RTNETLINK answers: File exists". This implies that the test fails. Signed-off-by: Giuseppe Cavallaro <email@example.com>.
42) Log Message:
Addition of Initial set of Process Event Connectors by Li Zefan. Process event connector is a netlink connector that reports process events to userspace, and currently we have 5 kinds of process events, i.e. fork, exit, exec, uid, gid. There are total 5 test cases to test its functionality. But the test is not run by default, because I don't find a way to decide whether the underlying kernel supports this feather or not. Signed-off-by: Li Zefan <firstname.lastname@example.org>.
43) Log Message:
Here it is. Based on my last patch.
- building failure on 2.6.16 should be fixed
- fix "make install" if kernel version < 2.6.15
- abort tests if kernel version < 2.6.15
Signed-off-by: Li Zefan <email@example.com>.
44) Log Message:
This was ported from the Crackerjack Project by Masatake YAMATO <firstname.lastname@example.org>.
45) Log Message:
I'd like to use the mechanism you introduced in io_* testcases. So I've made 'io_cancel' string in the script and Makefile a variable to avoid mistake. I made the patch from testcases/kernel/syscalls/io_cancel/Makefile, not from ltp/testcases/kernel/syscalls/io_cancel/Makefile. Is this acceptable. CVS reports like testcases/kernel/syscalls/io_cancel/Makefile. Signed-off-by: Masatake YAMATO <email@example.com>.
46) Log Message:
hackbench tests the Linux scheduler. Initial test was written by Rusty Russell <firstname.lastname@example.org>. Later modified by Pierre Peiffer <email@example.com>, Ingo Molnar <firstname.lastname@example.org>, Arjan van de Ven <email@example.com>, "Zhang, Yanmin" <firstname.lastname@example.org>, Nathan Lynch <email@example.com> and others. Included in LTP by Subrata Modak<firstname.lastname@example.org>, after Signed-off-by: Rusty Russell <email@example.com>.
47) Log Message:
I am proposing with the joined patch to allow the suite to be able the run the previous rpc tests (called now basic_tests). It needs to resolve some issues in the new "tirpc part" before allowing the suite to launch it again. Le Rouzic <firstname.lastname@example.org>.
48) Log Message:
Few Changes to ttype value.
49) Log Message:
Changes to fix Build, Install and run on non-supported architectures.
50) Log Message:
Fixing the run on supported kernels.