Git Log

Commit Date  
[3d8666] by subrata_modak subrata_modak

I've clean my signalfd test case up with autoconf. After applying the patch, do at ltp/
make (or cd testcases/kernel/syscalls/signalfd; make)
Benefits are:
- signalfd01.c doesn't depends on kernel version (it used KERNEL_VERSION macro.)
- Makefile becomes simple.
- #ifdef/#endif of signalfd01.c becomes readable.
- signalfd.m4 can use other program than ltp.
I revisied my patch.
- signalfd.m4 is renamed to ltp-signalfd.m4.
- configure is run by make if config.h is older than
- autoconf is run by make if configure is older than
- autoheader is run by make if is older than
- dist-clean, a new make target, removes autom4te.cache, config.log and config.status.
- maintainer-clean, a new make target, removes configure and
Signed-off-by: Masatake YAMATO <>.

2008-11-11 08:31:27 Tree
[688256] by subrata_modak subrata_modak

Call cleanup() at the right places to prevent fallocate tests leaving files in the temporary directory. Signed-off-by: Jiri Palecek <>.

2008-11-11 06:46:21 Tree
[814e03] by subrata_modak subrata_modak

Prevent leaving files in the temporary directory by calling tst_rmdir, or cleanup, where appropriate. Signed-off-by: Jiri Palecek <>.

2008-11-11 06:44:51 Tree
[322189] by subrata_modak subrata_modak

Do not call tst_brkm from the cleanup function in some tests: It is bad for the cleanup function to abort by calling tst_brkm, because in that case, further cleanup will not be performed. This patch fixes it in some chmod*, chown*, fchmod* and fchown* tests by substituting tst_resm for tst_brkm. Signed-off-by: Jiri Palecek <>.

2008-11-11 06:43:40 Tree
[d3ee1f] by subrata_modak subrata_modak

Don't break chown tests on non-catastrophic failures. Signed-off-by: Jiri Palecek <>.

2008-11-11 06:39:11 Tree
[11fbfd] by subrata_modak subrata_modak

This patch fixes the error, that code exhausting the file descriptor table in execve04 test actually doesn't exhaust the fd table at all. Signed-off-by: Jiri Palecek <>.

2008-11-11 06:18:11 Tree
[635f2a] by subrata_modak subrata_modak

Fix success detection in execve04 test:
The execve04 test works like this: It sets up the environment, calls execve() and expects failure. However, this has two bad consequences if the call actually succeeds
1. The failure (ie. success of the call) is unnoticed,
2. The test leaves loads of files in the temporary directory.
all of them being caused by the fact that the test no longer runs after a succesful exec(). This patch fixes the situation by calling exec in a child only. The failure (or success) is gathered from the child's exit value. Signed-off-by: Jiri Palecek <>.

2008-11-11 06:17:04 Tree
[24fc21] by subrata_modak subrata_modak

when building Debian ltp package on alpha, the package failed to build, because alpha lacks some of the syscalls (the xxx_16 ones). See:
I have created some patches, which fix this behaviour (ie. the build doesn't fail then). They work like this:
1. Syscalls which are potentially missing on some architectures are listed in the stub-list,
2. If a syscall(x) is called and x is 0 (a value of undefined stub syscalls), the test is aborted by tst_brk(). This is accomplished by a macro wrapper over the syscall() function (this almost eliminates the need of changing the tests in question, and allows the compiler to eliminate parts of tests of nonexistent syscalls as dead code). The attached patches implement this. Some remarks:
- the syscalls added to the stub list are the ones which appear in the kernel sources as __IGNORE_name-of-syscall,
- the macro is for gcc only. The test using this mechanism (ie. #including linux_syscall_numbers.h and calling syscall()) must define static function void cleanup(void) to be called when the syscall is missing (the patch also handles this for tests that lack it).
Signed-off-by: Jiri Palecek <>.

2008-11-11 05:57:38 Tree
[e312d9] by subrata_modak subrata_modak

Hello, these are some little fixes I've created for ltp. They are typos, fixes for compiler warning, bashisms in the makefiles etc. Signed-off-by: Jiri Palecek <>.

2008-11-11 05:15:52 Tree
[424f27] by subrata_modak subrata_modak

This patch fixes a compilation warning:
timerfd01.c: In function `main':
timerfd01.c:128: warning: unused variable `tfd2'
Signed-off-by: CAI Qian <>.

2008-11-11 04:55:32 Tree
[65be6c] by subrata_modak subrata_modak

on SLES10 SP2 __NR_get_robust_list is not defined and cause following compiler warning:
make[4]: Entering directory `/usr/src/packages/BUILD/ltp-full-20081031/testcases/kernel/syscalls/get_robust_list'
cc -fmessage-length=0 -D_FORTIFY_SOURCE=2 -O2 -g -Wall -fmessage-length=0 -D_FORTIFY_SOURCE=2 -O2 -g -I../../include -g -Wall -I../../../../include -Wall get_robust_list01.c
-L../../../../lib -lltp -o get_robust_list01
get_robust_list01.c: In function 'main':
get_robust_list01.c:252: warning: control reaches end of non-void function
make[4]: Leaving directory `/usr/src/packages/BUILD/ltp-full-20081031/testcases/kernel/syscalls/get_robust_list'
And cause "unexpected" return value:
x86_64:~/:[1]# /usr/lib64/ltp/testcases/bin/get_robust_list01 get_robust_list: system call not available
x86_64:~/:[43]# echo $?
x86_64:~/:[0]# /usr/lib64/ltp/testcases/bin/get_robust_list01 | wc -c
Attached patch avoids "random"/43 return value. Signed-off-by: Daniel Gollub <>.

2008-11-07 10:15:22 Tree
[fdbe86] by subrata_modak subrata_modak

Subrata and Daniel,
moving from ia64 to x86_64 arch I have got this at linking time:
cc -o aio-stress aio-stress.o -Wall -O -g -DAIO -L /usr/lib -laio -lpthread
/usr/bin/ld: skipping incompatible /usr/lib/ when searching for -lpthread
/usr/bin/ld: skipping incompatible /usr/lib/libpthread.a when searching for -lpthread
/usr/bin/ld: skipping incompatible /usr/lib/ when searching for -lc
/usr/bin/ld: skipping incompatible /usr/lib/libc.a when searching for -lc
so , if you could have a look to the suggested following patch. Signed-Off-By: Jacky Malcles <>.

2008-11-07 09:50:30 Tree
[46501c] by subrata_modak subrata_modak

(previous mail got accidentally line-wrapped, sorry.). Attachted patch changes the location of thest test-binaries of aio-stress and aiodio runtest-files. Instead of the relative-build location just the binary get called,which is in the PATH of testcases/bin/ anyway when called by "pan". This patch should have no impact on testing inside ltp-build-tree. The idea of this patch is to allow easier packaging of LTP. (No runtest-file modification required when installting into the system environment) Signed-off-by: Daniel Gollub <>.

2008-11-07 09:38:40 Tree
[09162c] by subrata_modak subrata_modak

This patch fixes an issue with the sort command in netns testcases. Because of this all network namespace testcases were failing. Signed-off-by: Sudhir Kumar <>.

2008-11-07 09:25:31 Tree
[a8b1ae] by subrata_modak subrata_modak

Added Kernel .config options for building LTP SECURITY TESTS. Signed-Off-By: Subrata Modak <>. Reviewd-By: Stephen Smalley <>.

2008-11-07 09:19:07 Tree
[66e085] by subrata_modak subrata_modak

Submitting the testcase, which would try to kill the parent namespace pid from the container init. Also this tests a scenario of killing non existent pid from the container. Signed-off-by: Veerendra C <>. Acked-by: Sukadev Bhattiprolu <>.

2008-11-07 09:06:01 Tree
[a9e522] by subrata_modak subrata_modak

The following Patch adds the option to run filecaps tests from and also provisions for installation of required libraries not present in the system. Also systematic execution of all tests run through is added. Signed-Of-By: Subrata Modak <>.

2008-11-07 08:54:25 Tree
[d9600d] by subrata_modak subrata_modak

Following the footsteps of Masatake Yamato, i have decided to enable building, installing & running of some _16 & _64 bit syscalls tests in LTP. I have taken this trivial ones, and, would leave other porting to you. Signed-Off-By: Subrata Modak <>.

2008-11-07 08:45:27 Tree
[ce18da] by subrata_modak subrata_modak

This will remain diabled till we find a solution to the Infinite loop problem. Subrata Modak <>.

2008-11-04 11:30:13 Tree
[fe5ccf] by subrata_modak subrata_modak

Added test case for checking cpuidle sysfs files. Signed-Off-By: Nageswara R Sastry <>.

2008-11-04 08:34:34 Tree
[0678e8] by subrata_modak subrata_modak

The attached Patch defines more about the keywords:
i) TPASS - Indicates that the test case had the expected result and passed.
ii) TFAIL - Indicates that the test case had an unexpected result and failed.
iii) TBROK - Indicates that the remaining test cases are broken and will not execute correctly, because some precondition not met, such as a resource not being available.
iv) TCONF - Indicates that the test case was not written to run on the current harware or software configuration such as machine type, or, kernel version.
v) TRETR - Indicates that the test cases has been retired and should not be executed any longer.
vi) TWARN - Indicates that the test case experienced an unexpected or undesirable event that should not affect the test itself such as being unable to cleanup resources after the test finished.
vii) TINFO - Specifies useful information about the status of the test that does not affect the result and does not indicate a problem.

in the HTML file generated after test run. I believe it will be very useful for deciphering results better: Signed-Off-By: Subrata Modak <>.

2008-11-04 06:17:21 Tree
[d1ece5] by subrata_modak subrata_modak

Enable Kernel with the Option during build to test filecaps support. Subrata.

2008-11-03 10:09:30 Tree
[751f98] by vapier vapier

remove bogus line

2008-11-03 09:04:43 Tree
[5002f7] by vapier vapier

check input files and abort if broken line is found

2008-11-03 09:00:07 Tree
[a3b820] by subrata_modak subrata_modak

Alan Cox [] wrote:
The test changes the window size using the slave-fd and expects that it won't affect the window-size on master-fd. With this change, we return the slave's window size and test fails. I've no idea why anyone would have thought the existing behaviour was correct. The pty/tty pair code tries to share the size and other information at all times and the old test was I think verifying a bug existed.
Sukadev <> wrote:
We are referring to the last window size check in test2() of testcases/kernel/pty/ptem01.c. This check will cause the test to fail when some of the planned ttydev changes are merged. Would you happen to know if the check is really required or if it should be dropped ?
Subrata Modak <> wrote:
I would want the test to remain there, but introduce some checkings before running the test. As test2() is valid under present circumstances, we should retain it as people will keep using LTP on lower kernels. Having said that, i would like to come with a solution where test2() of testcases/kernel/pty/ptem01.c is not run after the planned ttydev changes are merged. Something compile/run time checking to either not to build that part of code and run it. Can we do something like that by checking some glibc/kernel exported definitions ?
Sukadev <> wrote:
Just to be clear, the entire test2() is not broken. Only the last part (see patch below) Other parts of test2() should be fine even with new changes. Other than the kernel version when the changes are merged, I am not sure there is a way. Besides, it is not clear which assertion that part of test2() is testing and if it is even needed for older kernels. Here is the part of test2() I am referring to: Signed-Off-By: Sukadev <>.

2008-11-03 07:22:44 Tree
Older >

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks