Menu
▾
▴
[Ltp-cvs] ltp ChangeLog,1.122,1.123
|
From: Subrata <sub...@us...> - 2009-04-29 13:57:02
|
Update of /cvsroot/ltp/ltp In directory ddv4jf1.ch3.sourceforge.com:/tmp/cvs-serv17956/ltp Modified Files: ChangeLog Log Message: Changes for APRIL 2009. Signed-Off-By: Subrata Modak <su...@li...>. Index: ChangeLog =================================================================== RCS file: /cvsroot/ltp/ltp/ChangeLog,v retrieving revision 1.122 retrieving revision 1.123 diff -C2 -d -r1.122 -r1.123 *** ChangeLog 31 Mar 2009 05:58:26 -0000 1.122 --- ChangeLog 29 Apr 2009 13:56:49 -0000 1.123 *************** *** 1,2 **** --- 1,552 ---- + LTP-20090430 + + 1) Log Message: + This patch adds Integrity Measurement Architecture(IMA) testing support: + Changes: + - updated README + - add test for existence of openssl-devel (m4/ltp-crypto.m4) + - add support for finding an audit message in different log files + Signed-off-by: Mimi Zohar <zo...@us...>. + + Modified Files: + ltp/config.mk.in + ltp/configure.ac + ltp/testcases/kernel/security/Makefile + Added Files: + ltp/m4/ltp-crypto.m4 + ltp/runtest/ima + ltp/testcases/kernel/security/integrity/Makefile + ltp/testcases/kernel/security/integrity/ima/Makefile + ltp/testcases/kernel/security/integrity/ima/README + ltp/testcases/kernel/security/integrity/ima/policy/Makefile + ltp/testcases/kernel/security/integrity/ima/policy/measure.policy + ltp/testcases/kernel/security/integrity/ima/policy/measure.policy-invalid + ltp/testcases/kernel/security/integrity/ima/src/Makefile + ltp/testcases/kernel/security/integrity/ima/src/ima_boot_aggregate.c + ltp/testcases/kernel/security/integrity/ima/src/ima_measure.c + ltp/testcases/kernel/security/integrity/ima/src/ima_mmap.c + ltp/testcases/kernel/security/integrity/ima/tests/Makefile + ltp/testcases/kernel/security/integrity/ima/tests/ima_measurements.sh + ltp/testcases/kernel/security/integrity/ima/tests/ima_policy.sh + ltp/testcases/kernel/security/integrity/ima/tests/ima_setup.sh + ltp/testcases/kernel/security/integrity/ima/tests/ima_tpm.sh + ltp/testcases/kernel/security/integrity/ima/tests/ima_violations.sh + + 2) Log Message: + Addition of per_cpu_atomic_operations_vs_interrupt_disabling_module test to LTP. Signed-Off-By: Mathieu Desnoyers <mat...@po...>. + + Added Files: + ltp/testcases/kernel/device-drivers/misc_modules/per_cpu_atomic_operations_vs_interrupt_disabling_module/Makefile + ltp/testcases/kernel/device-drivers/misc_modules/per_cpu_atomic_operations_vs_interrupt_disabling_module/test-cmpxchg-nolock.c + + 3) Log Message: + Module to test Per CPU Allocator. Signed-Off-By: Tejun Heo <tj...@ke...>. + + Added Files: + ltp/testcases/kernel/device-drivers/misc_modules/per_cpu_allocator_module/Makefile + ltp/testcases/kernel/device-drivers/misc_modules/per_cpu_allocator_module/test_per_cpu_allocator_module.c + + 4) Log Message: + Patch for fixing the testcase's segment fault. Signed-Off-By: Fan He <fh...@no...>. + + Modified File(s): + ltp/testcases/open_posix_testsuite/conformance/interfaces/timer_gettime/speculative/6-1.c + ltp/testcases/open_posix_testsuite/conformance/interfaces/timer_settime/speculative/12-1.c + + 5) Log Message: + Extended the summary info to the case of LTP cross-built i.e. running on different arch with respect to the host. Moreover, a more detailed summary about LTP test results has been added. Signed-off-by: Francesco Rundo <fra...@st...>. + + Modified File(s): + ltp/tools/genhtml.pl + + 6) Log Message: + Add Simple Test for PERFORMANCE COUNTER in Linux. Signed-Off-By: Ingo Molnar <mi...@el...>. Ported-To-And-Tested-On-LTP-By: Subrata Modak <su...@li...>. + + Modified Files: + ltp/runalltests.sh + Added Files: + ltp/runtest/perfcounters + ltp/testcases/kernel/performance_counters/Makefile + ltp/testcases/kernel/performance_counters/performance_counter01.c + + 7) Log Message: + Add Test for Software and Hardware PERFORMANCE COUNTERS verification in Linux. Signed-Off-By: Paul Mackerras <pa...@sa...>. Ported-To-And-Tested-On-LTP-By: Subrata Modak <su...@li...>. + + Modified Files: + ltp/runtest/perfcounters + Added Files: + ltp/testcases/kernel/performance_counters/performance_counter02.c + + 8) Log Message: + Add Test for Checking mmap() corruption. Signed-Off-By: Ying Han <yi...@go...>. Ported-To-And-Tested-On-LTP-By: Subrata Modak <su...@li...>. + + Modified Files: + ltp/runtest/stress.part1 + Added Files: + ltp/testcases/kernel/mem/mmapstress/mmap-corruption01.c + + 9) Log Message: + Growfiles: Fix Test Failures. See: http://marc.info/?t=123866461100001&r=1&w=2&n=2, for more info. Signed-Off-By: CAI Qian <ca...@cc...>. + + Modified File(s): + ltp/lib/Makefile + ltp/testcases/kernel/fs/doio/growfiles.c + + 10) Log Message: + While running the latest LTP testsuite (CVS checkout), some tests failed due to small errors in the testscripts. I've attached two diffs for both testcases/kernel/syscalls/utimensat/utimensat_tests.sh and testcases/kernel/syscalls/ioctl/test_ioctl. Signed-Off-By: Christian Kujau <li...@ne...>. + + Modified File(s): + ltp/testcases/kernel/syscalls/ioctl/test_ioctl + ltp/testcases/kernel/syscalls/utimensat/utimensat_tests.sh + + 11) Log Message: + Patch to integrate sched_smt cpu consolidation testcase to LTP. Signed-off-by: poornima nayak <mp...@li...>. + + Modified File(s): + ltp/testcases/kernel/power_management/pm_include.sh + ltp/testcases/kernel/power_management/runpwtests.sh + + 12) Log Message: + This is v4l-test 0.11 patch for LTP. Changes: + - Test cases added for VIDIOC_G_OUTPUT, VIDIOC_S_OUTPUT, VIDIOC_G_FMT, VIDIOC_G_SLICED_VBI_CAP, VIDIOC_QUERYMENU; + - Cleaned up ret and errno variable names; + - Separated the NULL parameter test cases to a separated testsuite and reworked most of the NULL parameter test cases; + - Added camera enabling through /sys/devices/platform/eeepc/camera; + - Added results page to documentation; + - Follow kernel API changes in video_dummy.ko + Signed-off-by: Márton Németh <nm...@fr...>. + + Modified Files: + ltp/testcases/kernel/device-drivers/v4l/kernel_space/video_dummy.c + ltp/testcases/kernel/device-drivers/v4l/user_space/Makefile + ltp/testcases/kernel/device-drivers/v4l/user_space/README + ltp/testcases/kernel/device-drivers/v4l/user_space/dev_video.c + ltp/testcases/kernel/device-drivers/v4l/user_space/test_VIDIOC_AUDIO.c + ltp/testcases/kernel/device-drivers/v4l/user_space/test_VIDIOC_AUDOUT.c + ltp/testcases/kernel/device-drivers/v4l/user_space/test_VIDIOC_CROP.c + ltp/testcases/kernel/device-drivers/v4l/user_space/test_VIDIOC_CROPCAP.c + ltp/testcases/kernel/device-drivers/v4l/user_space/test_VIDIOC_CTRL.c + ltp/testcases/kernel/device-drivers/v4l/user_space/test_VIDIOC_ENUMAUDIO.c + ltp/testcases/kernel/device-drivers/v4l/user_space/test_VIDIOC_ENUMAUDOUT.c + ltp/testcases/kernel/device-drivers/v4l/user_space/test_VIDIOC_ENUMINPUT.c + ltp/testcases/kernel/device-drivers/v4l/user_space/test_VIDIOC_ENUMOUTPUT.c + ltp/testcases/kernel/device-drivers/v4l/user_space/test_VIDIOC_ENUMSTD.c + ltp/testcases/kernel/device-drivers/v4l/user_space/test_VIDIOC_ENUM_FMT.c + ltp/testcases/kernel/device-drivers/v4l/user_space/test_VIDIOC_FREQUENCY.c + ltp/testcases/kernel/device-drivers/v4l/user_space/test_VIDIOC_FREQUENCY.h + ltp/testcases/kernel/device-drivers/v4l/user_space/test_VIDIOC_INPUT.c + ltp/testcases/kernel/device-drivers/v4l/user_space/test_VIDIOC_INPUT.h + ltp/testcases/kernel/device-drivers/v4l/user_space/test_VIDIOC_LOG_STATUS.c + ltp/testcases/kernel/device-drivers/v4l/user_space/test_VIDIOC_MODULATOR.c + ltp/testcases/kernel/device-drivers/v4l/user_space/test_VIDIOC_PARM.c + ltp/testcases/kernel/device-drivers/v4l/user_space/test_VIDIOC_PRIORITY.c + ltp/testcases/kernel/device-drivers/v4l/user_space/test_VIDIOC_QUERYCAP.c + ltp/testcases/kernel/device-drivers/v4l/user_space/test_VIDIOC_QUERYCTRL.c + ltp/testcases/kernel/device-drivers/v4l/user_space/test_VIDIOC_QUERYSTD.c + ltp/testcases/kernel/device-drivers/v4l/user_space/test_VIDIOC_STD.c + ltp/testcases/kernel/device-drivers/v4l/user_space/test_VIDIOC_TUNER.c + ltp/testcases/kernel/device-drivers/v4l/user_space/test_invalid_ioctl.c + ltp/testcases/kernel/device-drivers/v4l/user_space/v4l2_test.c + ltp/testcases/kernel/device-drivers/v4l/user_space/doc/index.html + Added Files: + ltp/testcases/kernel/device-drivers/v4l/user_space/test_VIDIOC_FMT.c + ltp/testcases/kernel/device-drivers/v4l/user_space/test_VIDIOC_FMT.h + ltp/testcases/kernel/device-drivers/v4l/user_space/test_VIDIOC_G_SLICED_VBI_CAP.c + ltp/testcases/kernel/device-drivers/v4l/user_space/test_VIDIOC_G_SLICED_VBI_CAP.h + ltp/testcases/kernel/device-drivers/v4l/user_space/test_VIDIOC_OUTPUT.c + ltp/testcases/kernel/device-drivers/v4l/user_space/test_VIDIOC_OUTPUT.h + ltp/testcases/kernel/device-drivers/v4l/user_space/test_VIDIOC_QUERYMENU.c + ltp/testcases/kernel/device-drivers/v4l/user_space/test_VIDIOC_QUERYMENU.h + ltp/testcases/kernel/device-drivers/v4l/user_space/doc/results.html + + 13) Log Message: + Patch for fixing the openposix_getoverrun_speculative_6_1 testcase's segment fault. Signed-Off-By: Fan He <fh...@no...>. + + Modified File(s): + ltp/testcases/open_posix_testsuite/conformance/interfaces/timer_getoverrun/speculative/6-1.c + + 14) Log Message: + Patch for fixing the openposix_timer_delete_speculative_5_1 testcase's segment fault. Signed-Off-By: Fan He <fh...@no...>. + + Modified File(s): + ltp/testcases/open_posix_testsuite/conformance/interfaces/timer_delete/speculative/5-1.c + + 15) Log Message: + I am not sure what kinds of IO and wait methods are available on uClinux, but by looking at the code in tlibio.h, the following method seems not supported there. So whenever LIO_IO_SYNCP was chosen as the random IO method, it will skip the above code and failback to "No I/O method chosen". Can you try the following patch to see if it fixes the problem? It drops LIO_IO_SYNCP as an avaliable method for uClinux, and also narrows down the wait methods since it does not support async IO there. I'd hope someone knew better than me about uClinux to review this patch. Signed-off-by: CAI Qian <ca...@cc...>. + + Modified File(s): + ltp/include/tlibio.h + + 16) Log Message: + Fix clone07 bug. Signed-Off-By: Guo Hongruan <guo...@gu...>. + + Modified File(s): + ltp/testcases/kernel/syscalls/clone/clone07.c + + 17) Log Message: + Addition of splice02 test for splice() syscall. Original-Author: Jens Axboe <ax...@ke...>, Ported-To-LTP:By: Manas K Nayak <mak...@in...>. + + Modified Files: + ltp/runtest/syscalls + Added Files: + ltp/testcases/kernel/syscalls/splice/splice02.c + + 18) Log Message: + Addition of clock_nanosleep2_01 test for clock_nanosleep2() syscall. Original-Author: M. Koehrer <mat...@ar...>, Ported-To-LTP-By: Manas K Nayak <mak...@in...>, + + Modified Files: + ltp/runtest/syscalls + Added Files: + ltp/testcases/kernel/syscalls/clock_nanosleep2/Makefile + ltp/testcases/kernel/syscalls/clock_nanosleep2/clock_nanosleep2_01.c + + 19) Log Message: + Addition of cacheflush01 test for cacheflush() syscall. Original-Author: Maxin John <max...@gm...>, Ported-To-LTP-By: Manas K Nayak <mak...@in...>, + + Modified Files: + ltp/runtest/syscalls + Added Files: + ltp/testcases/kernel/syscalls/cacheflush/Makefile + ltp/testcases/kernel/syscalls/cacheflush/cacheflush01.c + + 20) Log Message: + Fix mount02 and mount03. Signed-Off-By: Guo Hongruan <guo...@gu...>. + + Modified File(s): + ltp/testcases/kernel/syscalls/mount/mount02.c + ltp/testcases/kernel/syscalls/mount/mount03.c + + 21) Log Message: + How many loops should setuid04 run test case using "setuid04 -i 2"? It should be 2 but in fact, it is 3, This patch solves this problem. Hoppe it is useful. Thanks a lot!. Signed-Off-By: Guo Hongruan <guo...@gu...>. + + Modified File(s): + ltp/testcases/kernel/syscalls/setuid/setuid04.c + + 22) Log Message: + Rohit verma <roh...@gm...> wrote: There is a change in compilation mechanism in LTP from Feb 09 distribution.The previous Make mechanism did not provide any optimization while compiling the fork05 test program and the test used to Pass . However the newer Makefile uses optimization level 2 while compiling, if this file is executed the test case fails. CAI Qian <ca...@cc...> replied: This is definitely a case. I can reproduce it on Fedora 10, so I have created a bug of it, and copied the author Ulrich Drepper, https://bugzilla.redhat.com/show_bug.cgi?id=495296. Ulrich Drepper has pointed out in the above bug report that this failure was due to incorrect test code. The test code isn't correct. The compiler cannot look inside the asm statements in main() and see that they are really necessary. Based on the information given the compiler can drop some of them. Change all asms in main from asm(...) to asm volatile(...), and the code works fine. With the following patch, it works fine with and without compilation optimization. Signed-off-by: CAI Qian <ca...@cc...>. + + Modified Files: + ltp/testcases/kernel/syscalls/fork/fork05.c + + 23) Log Message: + Fix from CAI Qian <ca...@cc...>. + + Modified Files: + ltp/testcases/network/lib6/runcc.c + + 24) Log Message: + It turns out that -s option does not has any effect for binutils ar, which makes related test cases invalid in ar01 test. Nick Clifton replied in the bug report, https://bugzilla.redhat.com/show_bug.cgi?id=490797. It does make a difference on some versions of the ar program, notably those on some Unix and Solaris systems. These versions of ar do not automatically added a symbol index when the archive is created. But the binutils ar automatically adds a symbol index when an archive is created. So the -s option is supported mainly for backwards compatibility with these other versions of ar. Signed-off-by: CAI Qian <ca...@cc...>. + + Modified Files: + ltp/testcases/commands/ade/ar/ar01 + + 25) Log Message: + The library file in powermanagement testcase is modified to support sched_mc=2 testing. Wrote a another function to generate load in the system through make -j x. Signed-off-by: poornima nayak <mp...@li...>. + + Modified Files: + ltp/testcases/kernel/power_management/lib/sched_mc.py + + 26) Log Message: + CPU consolidation testcase is modified such that workload is not passed as input to the testcase. Based on sched_mc input corresponding workload is triggered. Signed-off-by: poornima nayak <mp...@li...>. + + Modified Files: + ltp/testcases/kernel/power_management/cpu_consolidation.py + + 27) Log Message: + Master script of Powermanagement testcase is modified to invoke cpu_consolidation testcase without workload. Restructured cpu_consolidation testcase within a loop. Signed-off-by: poornima nayak <mp...@li...>. + + Modified Files: + ltp/testcases/kernel/power_management/runpwtests.sh + + 28) Log Message: + This testcase test sched_smt_power_saving interface with valid and inavlid values. Signed-off-by: poornima nayak <mp...@li...>. + + Added Files: + ltp/testcases/kernel/power_management/test_sched_smt.sh + + 29) Log Message: + Modifed test_sched_mc interface testing testcase to use reusable function. Signed-off-by: poornima nayak <mp...@li...>. + + Modified Files: + ltp/testcases/kernel/power_management/test_sched_mc.sh + + 30) Log Message: + The test_dma_thread_diotest contains an unnecessary bashism. This patch fixes that. Signed-off-by: Jiri Palecek <jpa...@we...>. + + Modified File(s): + ltp/testcases/kernel/io/direct_io/test_dma_thread_diotest7.sh + + 31) Log Message: + Make fs/quota_remount_test01 more POSIX-shell friendly. Signed-off-by: Jiri Palecek <jpa...@we...>. + + Modified File(s): + ltp/testcases/kernel/fs/quota_remount/quota_remount_test01.sh + + 32) Log Message: + First, there was bug in test - it used seconds part of struct timespec structure, because total_sec was 5 from previous loop, and 1..4 millions of nanoseconds in addition to these 5 seconds did nothing in test result, checking sleep time for correctness also used total_sec. Also pselect takes struct timespec as its argument, not struct timeval, now code in test uses struct timeval as argument of pselect and suppose second field of this structure is microseconds instead of nanoseconds. Let's fix this part of test - I suggest to set nanoseconds to 1e8 ... 4e8 with step 1e8 and check sleep time differs from expected value no more than 10% of it. Signed-Off-By: Dmitry Guryanov <dgu...@pa...>. + + Modified File(s): + ltp/testcases/kernel/syscalls/pselect/pselect01.c + + 33) Log Message: + This is the patch of the v4l-test 0.12 for LTP. Changes: Test cases added for VIDIOC_S_FMT; NULL parameter test suite split to read only, write only and write/read ioctl suite; More verbose debug output in VIDIOC_S_FREQUENCY and in some other test cases; More strict check added for strings in different test cases. Signed-off-by: Márton Németh <nm...@fr...>. + + Modified File(s): + ltp/testcases/kernel/device-drivers/v4l/user_space/README + ltp/testcases/kernel/device-drivers/v4l/user_space/test_VIDIOC_AUDIO.c + ltp/testcases/kernel/device-drivers/v4l/user_space/test_VIDIOC_AUDOUT.c + ltp/testcases/kernel/device-drivers/v4l/user_space/test_VIDIOC_ENUMAUDIO.c + ltp/testcases/kernel/device-drivers/v4l/user_space/test_VIDIOC_ENUMAUDOUT.c + ltp/testcases/kernel/device-drivers/v4l/user_space/test_VIDIOC_ENUMINPUT.c + ltp/testcases/kernel/device-drivers/v4l/user_space/test_VIDIOC_ENUMOUTPUT.c + ltp/testcases/kernel/device-drivers/v4l/user_space/test_VIDIOC_ENUMSTD.c + ltp/testcases/kernel/device-drivers/v4l/user_space/test_VIDIOC_ENUM_FMT.c + ltp/testcases/kernel/device-drivers/v4l/user_space/test_VIDIOC_FMT.c + ltp/testcases/kernel/device-drivers/v4l/user_space/test_VIDIOC_FMT.h + ltp/testcases/kernel/device-drivers/v4l/user_space/test_VIDIOC_FREQUENCY.c + ltp/testcases/kernel/device-drivers/v4l/user_space/test_VIDIOC_MODULATOR.c + ltp/testcases/kernel/device-drivers/v4l/user_space/test_VIDIOC_QUERYCAP.c + ltp/testcases/kernel/device-drivers/v4l/user_space/test_VIDIOC_QUERYCTRL.c + ltp/testcases/kernel/device-drivers/v4l/user_space/test_VIDIOC_QUERYMENU.c + ltp/testcases/kernel/device-drivers/v4l/user_space/test_VIDIOC_STD.c + ltp/testcases/kernel/device-drivers/v4l/user_space/test_VIDIOC_TUNER.c + ltp/testcases/kernel/device-drivers/v4l/user_space/v4l2_test.c + ltp/testcases/kernel/device-drivers/v4l/user_space/doc/index.html + ltp/testcases/kernel/device-drivers/v4l/user_space/doc/results.html + + 34) Log Message: + Jiri Palecek <jpa...@we...> wrote: While running the selinux tests, I was contemplating the way the $SELINUXTMPDIR is created. It seems to me that creating it in each test individually would allow running the tests in parallel, make some hacks needed to prevent interference of the tests unnecessary, allow the tests to be run directly from ltpmenu et al., and wouldn't add much more code. What do you think about this? Signed-off-by: Jiri Palecek <jpa...@we...>. + "Serge E. Hallyn" <se...@us...> replied: + If the motivation is to support multiple concurrent ltp runs, wouldn't it be better to have selinux-testsuite/tests/runtest.sh set/export SELINUXTMPDIR to a per-run tempdir? Even as simple as /tmp/selinux-$pid. Well, and testscripts/test_selinux.sh I guess. Hmm, no, bc at that level you can't easily support multiple policy module loads anyway. Never mind. + Jiri Palecek <jpa...@we...> replied back: No, the motivation was mostly to allow running these tests directly from PAN, without any supporting scripts. The ability to run the tests concurrently is just a pleasant bonus. I chose this way, because I find the needed changes pretty small. + "Serge E. Hallyn" <se...@us...> finally replied: Yeah - seems like a good idea. If the directories sometimes don't get deleted, then you might help out the admin by giving the directories easy to spot names so they can manually clean up... i.e. use mktemp -d /tmp/ltpselinuxXXXX or maybe even better mkdir -p /tmp/ltpselinux; mktemp -d -p /tmp/ltpselinux. + + Modified File(s): + ltp/testcases/kernel/security/selinux-testsuite/tests/bounds/selinux_bounds.sh + ltp/testcases/kernel/security/selinux-testsuite/tests/capable_file/selinux_capable_file.sh + ltp/testcases/kernel/security/selinux-testsuite/tests/capable_sys/selinux_capable_sys.sh + ltp/testcases/kernel/security/selinux-testsuite/tests/entrypoint/selinux_entrypoint.sh + ltp/testcases/kernel/security/selinux-testsuite/tests/execute_no_trans/selinux_execute_no_trans.sh + ltp/testcases/kernel/security/selinux-testsuite/tests/fdreceive/selinux_fdreceive.sh + ltp/testcases/kernel/security/selinux-testsuite/tests/file/selinux_file.sh + ltp/testcases/kernel/security/selinux-testsuite/tests/inherit/selinux_inherit.sh + ltp/testcases/kernel/security/selinux-testsuite/tests/ioctl/selinux_ioctl.sh + ltp/testcases/kernel/security/selinux-testsuite/tests/link/selinux_link.sh + ltp/testcases/kernel/security/selinux-testsuite/tests/mkdir/selinux_mkdir.sh + ltp/testcases/kernel/security/selinux-testsuite/tests/open/selinux_open.sh + ltp/testcases/kernel/security/selinux-testsuite/tests/readlink/selinux_readlink.sh + ltp/testcases/kernel/security/selinux-testsuite/tests/relabel/selinux_relabel.sh + ltp/testcases/kernel/security/selinux-testsuite/tests/rename/selinux_rename.sh + ltp/testcases/kernel/security/selinux-testsuite/tests/rxdir/selinux_rxdir.sh + ltp/testcases/kernel/security/selinux-testsuite/tests/setattr/selinux_setattr.sh + ltp/testcases/kernel/security/selinux-testsuite/tests/stat/selinux_stat.sh + + 35) Log Message: + I have been trying to run the selinux tests on Debian and discovered a small flaw. The test was using a return value variable which wasn't set by the test. I've coma across another strange (at least to me) fact - when you execute a program without path, it is searched for in $PATH. However, if the program is in one directory if $PATH and selinux rejects to run the file, the following directories in $PATH are search, and the call can succeed. Is this behavior planned? I know it can't tamper the security of selinux, but it can lead to surprising results. Also, I've found some uses of macros not present in Debian's refpolicy. Should I send a patch for them? Signed-off-by: Jiri Palecek <jpa...@we...>. + + Modified File(s): + ltp/testcases/kernel/security/selinux-testsuite/tests/entrypoint/selinux_entrypoint.sh + + 36) Log Message: + Add cgroup regression tests to LTP: Those testcases can reproduce bugs we found in cgroups, and is useful to track future regressions. Note: this test may crash the system with older kernels, so it is disabled for kernels older than 2.6.29. Another note: getdelays.c is linux-2.6/Documentation/accounting/getdelays.c. How to run this test: # runltp -f controllers + Result: + cgroup_regression_test 1 PASS : no kernel bug was found + cgroup_regression_test 2 PASS : notify_on_release is inherited + cgroup_regression_test 3 PASS : no kernel bug was found + cgroup_regression_test 4 PASS : no lockdep BUG was found + cgroup_regression_test 5 PASS : no kernel bug was found + cgroup_regression_test 6 PASS : no kernel bug was found + cgroup_regression_test 7 PASS : no kernel bug was found + cgroup_regression_test 8 PASS : no kernel bug was found + cgroup_regression_test 9 PASS : no kernel warning was found + cgroup_regression_test 10 PASS : no kernel warning was found + Signed-off-by: Li Zefan <li...@cn...>. + + Modified Files: + ltp/runtest/controllers + ltp/testcases/kernel/controllers/Makefile + ltp/testcases/kernel/controllers/README + Added Files: + ltp/testcases/kernel/controllers/cgroup/Makefile + ltp/testcases/kernel/controllers/cgroup/README + ltp/testcases/kernel/controllers/cgroup/cgroup_regression_test.sh + ltp/testcases/kernel/controllers/cgroup/fork_processes.c + ltp/testcases/kernel/controllers/cgroup/getdelays.c + ltp/testcases/kernel/controllers/cgroup/test_10_1.sh + ltp/testcases/kernel/controllers/cgroup/test_10_2.sh + ltp/testcases/kernel/controllers/cgroup/test_3_1.sh + ltp/testcases/kernel/controllers/cgroup/test_3_2.sh + ltp/testcases/kernel/controllers/cgroup/test_6_1.sh + ltp/testcases/kernel/controllers/cgroup/test_6_2.c + ltp/testcases/kernel/controllers/cgroup/test_9_1.sh + ltp/testcases/kernel/controllers/cgroup/test_9_2.sh + + 37) Log Message: + Test suite for cpuset: This is the test suite for the basis operation test and part functionality test of cpuset. It contains adding/removing cpus/mems test, setting flags test, exclusive function test, hierarchy relation test, inherit relation test and cpuset VS syscall test. More testcases will be added in future. Signed-off-by: Miao Xie <mi...@cn...>. + + Modified Files: + ltp/testcases/kernel/controllers/Makefile + ltp/testcases/kernel/controllers/README + ltp/testcases/kernel/controllers/test_controllers.sh + ltp/testcases/kernel/controllers/testplan.txt + Added Files: + ltp/testcases/kernel/controllers/cpuset/Makefile + ltp/testcases/kernel/controllers/cpuset/README + ltp/testcases/kernel/controllers/cpuset/run_cpuset_test.sh + ltp/testcases/kernel/controllers/cpuset/cpuset_base_ops_test/Makefile + ltp/testcases/kernel/controllers/cpuset/cpuset_base_ops_test/cpuset_base_ops_testset.sh + ltp/testcases/kernel/controllers/cpuset/cpuset_exclusive_test/Makefile + ltp/testcases/kernel/controllers/cpuset/cpuset_exclusive_test/cpuset_exclusive_test.sh + ltp/testcases/kernel/controllers/cpuset/cpuset_hierarchy_test/Makefile + ltp/testcases/kernel/controllers/cpuset/cpuset_hierarchy_test/cpuset_hierarchy_test.sh + ltp/testcases/kernel/controllers/cpuset/cpuset_inherit_test/Makefile + ltp/testcases/kernel/controllers/cpuset/cpuset_inherit_test/cpuset_inherit_testset.sh + ltp/testcases/kernel/controllers/cpuset/cpuset_lib/Makefile + ltp/testcases/kernel/controllers/cpuset/cpuset_lib/cpuset_funcs.sh + ltp/testcases/kernel/controllers/cpuset/cpuset_syscall_test/Makefile + ltp/testcases/kernel/controllers/cpuset/cpuset_syscall_test/cpuset_syscall_test.c + ltp/testcases/kernel/controllers/cpuset/cpuset_syscall_test/cpuset_syscall_testset.sh + + 38) Log Message: + While running the su01 test on Debian, I encountered a different error message on changing the password and giving a wrong old password. I guess the error message is actually OK, so I suggest to add it to the possible successful outcomes. Signed-off-by: Jiri Palecek <jpa...@we...>. + + Modified Files: + ltp/testcases/commands/su/su01_s1 + + 39) Log Message: + Fix running of the selinux tests: while running the ltp selinux tests on Debian, I found some problems: 1) the testdomain attribute cannot have setcurrent permission to itself. This is because in Debian refpolicy, only domains with attribute set_curr_context can have setcurrent permission on own processes (otherwise, it's forbidden by neverallow). And AFAIK, it's impossible to specify that domains having attribute testdomain also have attribute set_curr_context. Moreover, I found only two tests (dyntrans and dyntrace) that actually need it so far, so I'm not convinced it has to be granted globally. 2) the testscripts (eg. selinux_file.sh) have the test_file_t context, but they are to be run as sysadm_t. Sysadm_t therefore needs execute_no_trans permission on the test files. Please correct me if I'm wrong. - allow sysadm_t execute_no_trans on test_file_t to allow him to run the test shell scripts - get rid of setexec permission for testdomain, it conflicts with refpolicy and AFAIK is unneeded. Signed-off-by: Jiri Palecek <jpa...@we...>. + + Modified Files: + ltp/testcases/kernel/security/selinux-testsuite/refpolicy/test_global.te + + 40) Log Message: + + README: update kernel config for cgroup testing: lockdep is needed in one of the testcases in cgroup regression test. Signed-off-by: Li Zefan <li...@cn...>. + + Modified Files: + ltp/README + + 41) Log Message: + Fix fsync02 usage on filesystems which have undefined amount of free space: "Fields that are undefined for a particular file system are set to 0". Note that if it's ramfs or tmpfs with -o nr_blocks=0, there is no such thing as "amount of free space", reserved for root or not. - Al Viro. Signed-off-by: Michal Simek <mo...@mo...>. + + Modified Files: + ltp/testcases/kernel/syscalls/fsync/fsync02.c + + 42) Log Message: + Delete the change_owner binary, as it is an insecure suid root binary; rewrite tests that use it: This patch is based on Jiri's change_owner patch. I removed references in runtest/syscalls and fix some coding style violations. Signed-off-by: Michal Simek <mo...@mo...>. + + Modified Files: + ltp/runtest/syscalls + ltp/testcases/kernel/syscalls/chmod/Makefile + ltp/testcases/kernel/syscalls/chmod/chmod05.c + ltp/testcases/kernel/syscalls/chmod/chmod06.c + ltp/testcases/kernel/syscalls/chown/Makefile + ltp/testcases/kernel/syscalls/chown/chown03.c + ltp/testcases/kernel/syscalls/chown/chown04.c + ltp/testcases/kernel/syscalls/fchmod/Makefile + ltp/testcases/kernel/syscalls/fchmod/fchmod05.c + ltp/testcases/kernel/syscalls/fchmod/fchmod06.c + ltp/testcases/kernel/syscalls/fchown/Makefile + ltp/testcases/kernel/syscalls/fchown/fchown03.c + ltp/testcases/kernel/syscalls/fchown/fchown04.c + + 43) Log Message: + The attached patch fixes this bug. This is the bug of the kernel. The following patch has fixed the bug. + commit af76aba00fdcfb21535c9f9872245d14097a4561 + Author: Rusty Russell <ru...@ru...> + Date: Mon Mar 30 22:05:11 2009 -0600 + cpumask: fix seq_bitmap_*() functions. + 1) seq_bitmap_list() should take a const. + 2) All the seq_bitmap should use cpumask_bits(). + Signed-off-by: Rusty Russell <ru...@ru...> + But after applying this patch, Case 5 and 6 still failed. It is because the max size of CPUSET in the glibc is 1024, but the max size of your kernel is 4096, when we invoke the sched_getaffinity, the kernel will check whether the size of mask passed into the function is >= the size of the mask in the kernel. If not, the function returns -1. So it is not the bug of the tesecase. This patch contains two lib files written by Paul Jackson who is ex-maintainer of cpuset. These two lib files are used for both this bug fix and the testcases that will be added in future. Signed-Off-By: Miao Xie <mi...@cn...>. + + Modified Files: + ltp/testcases/kernel/controllers/cpuset/cpuset_lib/cpuset_funcs.sh + ltp/testcases/kernel/controllers/cpuset/cpuset_syscall_test/Makefile + ltp/testcases/kernel/controllers/cpuset/cpuset_syscall_test/cpuset_syscall_test.c + ltp/testcases/kernel/controllers/cpuset/cpuset_syscall_test/cpuset_syscall_testset.sh + Added Files: + ltp/testcases/kernel/controllers/cpuset/cpuset_lib/bitmask.h + ltp/testcases/kernel/controllers/cpuset/cpuset_lib/common.h + ltp/testcases/kernel/controllers/cpuset/cpuset_lib/cpuset.h + ltp/testcases/kernel/controllers/cpuset/cpuset_lib/libbitmask.c + ltp/testcases/kernel/controllers/cpuset/cpuset_lib/libcpuset.c + + 44) Log Message: + Add capability bounding set testcases, to verify the following: + 1. prctl(CAP_BSET_READ, 0..NCAPS) returns 1 + 2. prctl(CAP_BSET_READ, -1|NCAPS+1) return -1 + 3. prctl(CAP_BSET_DROP, -1|NCAPS+1) returns -1 + 4. prctl(CAP_BSET_DROP, 0..NCAPS) returns 1 + 4b. prctl(CAP_BSET_READ, N) returns 0 after each unset, 1 for those not yet removed + 5. fI=empty; N \notin pP; prctl(CAPBSET_DROP, N); setting pI=N fails + 6. pI=N; fI=fE=N; prctl(CAPBSET_DROP, N); exec(f) - N \in pE + (or make f setuid-root) + 7. pI=0; fI=fE=N; prctl(CAPBSET_DROP, N); exec(f) - N \notin pE + (or make f setuid-root) + A set of securebits and keepcaps tests have yet to be written (as per an email I sent a few months ago). Signed-off-by: Serge Hallyn <se...@us...>. + + Modified Files: + ltp/runltp + ltp/testcases/kernel/security/Makefile + Added Files: + ltp/runtest/cap_bounds + ltp/testcases/kernel/security/cap_bound/Makefile + ltp/testcases/kernel/security/cap_bound/cap_bounds_r.c + ltp/testcases/kernel/security/cap_bound/cap_bounds_rw.c + ltp/testcases/kernel/security/cap_bound/cap_bset_inh_bounds.c + ltp/testcases/kernel/security/cap_bound/check_for_libcap.sh + ltp/testcases/kernel/security/cap_bound/check_pe.c + ltp/testcases/kernel/security/cap_bound/dummy.c + ltp/testcases/kernel/security/cap_bound/exec_with_inh.c + ltp/testcases/kernel/security/cap_bound/exec_without_inh.c + ltp/testcases/kernel/security/cap_bound/run_capbounds.sh + + 45) Log Message: + Exit in testsf_s6 when host lookup fails to prevent segfaults later. Jiri Palecek <jpa...@we...>. + + Modified Files: + ltp/testcases/network/ipv6/sendfile6/testsf_s6.c + + 46) Log Message: + Fix collateral damage caused by recent coding style cleanups. Signed-off-by: Jiri Palecek <jpa...@we...>. + + Modified Files: + ltp/testcases/kernel/syscalls/syslog/syslog01 + ltp/testcases/kernel/syscalls/syslog/syslog02 + ltp/testcases/kernel/syscalls/syslog/syslog03 + ltp/testcases/kernel/syscalls/syslog/syslog04 + ltp/testcases/kernel/syscalls/syslog/syslog05 + ltp/testcases/kernel/syscalls/syslog/syslog06 + ltp/testcases/kernel/syscalls/syslog/syslog07 + ltp/testcases/kernel/syscalls/syslog/syslog08 + ltp/testcases/kernel/syscalls/syslog/syslog09 + ltp/testcases/kernel/syscalls/syslog/syslog10 + + 47) Log Message: + This patch is a rewrite of symlinkat and linkat tests aimed to: + - simplify the code + - cease using the current directory for testfiles + Hope this applies, since I'm sending this from a weekly (er.. monthly) version of Opera. Signed-off-by: Jiri Palecek <jpa...@we...>. + + Modified Files: + ltp/testcases/kernel/syscalls/linkat/linkat01.c + ltp/testcases/kernel/syscalls/symlinkat/symlinkat01.c + + 48) Log Message: + fallocate tests call syscall() incorrectly for 32-bit powerpc. Signed-off-by: Dave Kleikamp <sh...@li...>. + + Modified Files: + ltp/testcases/kernel/syscalls/fallocate/fallocate01.c + ltp/testcases/kernel/syscalls/fallocate/fallocate02.c + ltp/testcases/kernel/syscalls/fallocate/fallocate03.c + + 49) Log Message: + IMA update openssl-devel existence test: Verify the existence of openssl/sha.h not libcrypto, which is included in multiple packages, to determine if openssl-devel is installed. Signed-off-by: Mimi Zohar <zo...@us...>. Acked-by: Serge Hallyn <se...@us...>. + + Modified File(s): + ltp/m4/ltp-crypto.m4 + LTP-20090331 |