Re: [LTP] [RFC] [KDUMP] [PROPOSED WORK] kdump on Xen hypervisor and guests, more tests for utilities, like makedumpfile, mkdumprd, kexec etc
Hi Cai, Thanks very much for explaining everything. Regards-- Subrata On Tue, 2008-08-12 at 16:48 +0800, Cai Qian wrote: > Hi Subrata, > > From: Subrata Modak <[EMAIL PROTECTED]> > Subject: Re: [LTP] [RFC] [KDUMP] [PROPOSED WORK] kdump on Xen hypervisor and > guests, more tests for utilities, like makedumpfile, mkdumprd, kexec etc > Date: Tue, 12 Aug 2008 11:43:02 +0530 > > > On Tue, 2008-08-12 at 10:16 +0800, Cai Qian wrote: > > > Hi Subrata, > > > > > > From: Subrata Modak <[EMAIL PROTECTED]> > > > Subject: Re: [LTP] [RFC] [KDUMP] [PROPOSED WORK] kdump on Xen hypervisor > > > and guests, more tests for utilities, like makedumpfile, mkdumprd, kexec > > > etc > > > Date: Mon, 11 Aug 2008 19:02:47 +0530 > > > > > > > Cai, > > > > > > > > Any headway in this front ? > > > > > > > > > > I have all test cases finished, but I am working on implementing a > > > suitable harness to run those tests. > > > > Thanks Cai. Happy to know that you are done with all the test cases, and > > only the integration part is pending. I am little bit confused when you > > say that you are working on implementing a suitable harness to run those > > tests. Does that mean that the way the present LTP-Kdump tests are run > > is not suitable to accommodate the enhancements/additions that you are > > doing to the LTP-Kdump ? > > > > What I have already done is to create several basic building blocks for > testing of Kdump. For example, setup-bare-metal, config-ext3, > crash-sysrq-c, crash-lkdtm, analyse-crash etc. You probably could guess > what they are doing from their names. Then, we could combine those > building blocks to create test cases, which should give us more freedom > and flexibility to test things. I am going to include some pre-defined > test cases into LTP as well. I might propose new tests as LTP-kdump-ng. > > > I do not mind in having a nice harness within LTP for executing the > > LTP-Kdump tests, but i would hope that the new harness should also > > include the existing LTP-Kdump tests, so that you use the same (new > > harness) to tests everything in LTP-Kdump. Let me know what you think > > for the same. > > > > The problem that I am trying to figure it out is that we need a suitable > harness to schedule those tests and report results. For example, there > is a test case is like the following, > > setup-bare-metal > config-ext3:uuid > crash-sysrq-c > analyse-crash > > The first and the third steps requires to reboot the machine, so we need > a harness could resume execution of tests after reboot. I am thinking of > using cron job as in existing LTP-kdump tests, or a tests injector > running as a daemon, or something else. > > New tests should incorporate all existing tests and coverage of Kdump in > LTP. > > CaiQian > > > Regards-- > > Subrata > > > > > > > > CaiQian > > > > > > > Regards-- > > > > Subrata > > > > > > > > On Thu, 2008-07-24 at 05:11 +0530, Subrata Modak wrote: > > > > > Hi Cai, > > > > > > > > > > Some patches in Bits and Pieces regarding this nearby ? > > > > > > > > > > Regards-- > > > > > Subrata > > > > > > > > > > > > > > > > > Yes. Initally, I put this item to a relative low priority, partly > > > > > > because kdump config options and init scripts are tend to be > > > > > > distro-specific, so it won't be easy to write portable tests for > > > > > > different distros. In addition, lots of config options are not easy > > > > > > to > > > > > > be tested automately, like raw disk target, vfat disk target, and > > > > > > network target etc, as testers have to setup those name manually. > > > > > > But, > > > > > > you are right, those are high priority tests for kexec/kdump in > > > > > > distro > > > > > > release, we tested most of those options manually for RHEL anyway > > > > > > and we > > > > > > had some automated tests of it, which I'll try to submit to LTP as > > > > > > many > > > > > > as possible. For those manual tests, I'll also try to find some > > > > > > ways to > > > > > > automate them. For example, for different dump targets, it is > > > > &
Re: [LTP] [RFC] [KDUMP] [PROPOSED WORK] kdump on Xen hypervisor and guests, more tests for utilities, like makedumpfile, mkdumprd, kexec etc
On Tue, 2008-08-12 at 10:16 +0800, Cai Qian wrote: > Hi Subrata, > > From: Subrata Modak <[EMAIL PROTECTED]> > Subject: Re: [LTP] [RFC] [KDUMP] [PROPOSED WORK] kdump on Xen hypervisor and > guests, more tests for utilities, like makedumpfile, mkdumprd, kexec etc > Date: Mon, 11 Aug 2008 19:02:47 +0530 > > > Cai, > > > > Any headway in this front ? > > > > I have all test cases finished, but I am working on implementing a > suitable harness to run those tests. Thanks Cai. Happy to know that you are done with all the test cases, and only the integration part is pending. I am little bit confused when you say that you are working on implementing a suitable harness to run those tests. Does that mean that the way the present LTP-Kdump tests are run is not suitable to accommodate the enhancements/additions that you are doing to the LTP-Kdump ? I do not mind in having a nice harness within LTP for executing the LTP-Kdump tests, but i would hope that the new harness should also include the existing LTP-Kdump tests, so that you use the same (new harness) to tests everything in LTP-Kdump. Let me know what you think for the same. Regards-- Subrata > > CaiQian > > > Regards-- > > Subrata > > > > On Thu, 2008-07-24 at 05:11 +0530, Subrata Modak wrote: > > > Hi Cai, > > > > > > Some patches in Bits and Pieces regarding this nearby ? > > > > > > Regards-- > > > Subrata > > > > > > > > > > > Yes. Initally, I put this item to a relative low priority, partly > > > > because kdump config options and init scripts are tend to be > > > > distro-specific, so it won't be easy to write portable tests for > > > > different distros. In addition, lots of config options are not easy to > > > > be tested automately, like raw disk target, vfat disk target, and > > > > network target etc, as testers have to setup those name manually. But, > > > > you are right, those are high priority tests for kexec/kdump in distro > > > > release, we tested most of those options manually for RHEL anyway and we > > > > had some automated tests of it, which I'll try to submit to LTP as many > > > > as possible. For those manual tests, I'll also try to find some ways to > > > > automate them. For example, for different dump targets, it is possible > > > > to verify the generated initrd file as expected. > > > > > > > > > > > > > > > == increase coverages for new kexec/kdump development efforts == > > > > > > - new reserved region syntax in Kernel. > > > > > > > > > > Another important thing we need to focus on is driver testing. Drivers > > > > > can fail to initialize in second kernel and kdump will fail. Can we do > > > > > something so that we can do following. > > > > > > > > > > > > > That isn't something I have not thought of. For RHEL release testing, we > > > > will have a workflow to run those tests on any storage/network drivers, > > > > and it will report back testing results and driver matrix. However, this > > > > workflow is very distro-specific, and depends on the test farm it is > > > > using, so it does not make any sense to put it here. > > > > > > > > > - Collect the machine statistics on which kdump was tested and send > > > > > the reports to a common place. Especially capture the > > > > > storage/network > > > > > driver data which can be probably be available through LTP site. > > > > > > > > > > > > > That sounds like a good idea to me. > > > > > > > > > - Also capture how much memory was reserved on what architecture and > > > > > whether it worked or not. This will help us verify for sure that how > > > > > much memory to reserve for second kernel on various architectures. > > > > > > > > > > > > > This is something could be done. I'll have a look at it. > > > > > > > > Thanks, > > > > CaiQian > > > > > > > > > Thanks > > > > > Vivek > > > > > > > > > - > > > This SF.Net email is sponsored by the Moblin Your Move Developer's > > > challenge > > > Build the coolest Linux based applications with Moblin SDK & win great > > > prizes > > > Grand prize is a trip for two to an Open Source event anywhere in the > > > world > > > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > > > ___ > > > Ltp-list mailing list > > > [EMAIL PROTECTED] > > > https://lists.sourceforge.net/lists/listinfo/ltp-list > > ___ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec
Re: [LTP] [RFC] [KDUMP] [PROPOSED WORK] kdump on Xen hypervisor and guests, more tests for utilities, like makedumpfile, mkdumprd, kexec etc
Cai, Any headway in this front ? Regards-- Subrata On Thu, 2008-07-24 at 05:11 +0530, Subrata Modak wrote: > Hi Cai, > > Some patches in Bits and Pieces regarding this nearby ? > > Regards-- > Subrata > > > > > Yes. Initally, I put this item to a relative low priority, partly > > because kdump config options and init scripts are tend to be > > distro-specific, so it won't be easy to write portable tests for > > different distros. In addition, lots of config options are not easy to > > be tested automately, like raw disk target, vfat disk target, and > > network target etc, as testers have to setup those name manually. But, > > you are right, those are high priority tests for kexec/kdump in distro > > release, we tested most of those options manually for RHEL anyway and we > > had some automated tests of it, which I'll try to submit to LTP as many > > as possible. For those manual tests, I'll also try to find some ways to > > automate them. For example, for different dump targets, it is possible > > to verify the generated initrd file as expected. > > > > > > > > > == increase coverages for new kexec/kdump development efforts == > > > > - new reserved region syntax in Kernel. > > > > > > Another important thing we need to focus on is driver testing. Drivers > > > can fail to initialize in second kernel and kdump will fail. Can we do > > > something so that we can do following. > > > > > > > That isn't something I have not thought of. For RHEL release testing, we > > will have a workflow to run those tests on any storage/network drivers, > > and it will report back testing results and driver matrix. However, this > > workflow is very distro-specific, and depends on the test farm it is > > using, so it does not make any sense to put it here. > > > > > - Collect the machine statistics on which kdump was tested and send > > > the reports to a common place. Especially capture the storage/network > > > driver data which can be probably be available through LTP site. > > > > > > > That sounds like a good idea to me. > > > > > - Also capture how much memory was reserved on what architecture and > > > whether it worked or not. This will help us verify for sure that how > > > much memory to reserve for second kernel on various architectures. > > > > > > > This is something could be done. I'll have a look at it. > > > > Thanks, > > CaiQian > > > > > Thanks > > > Vivek > > > - > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > ___ > Ltp-list mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/ltp-list ___ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec
Re: [RFC] [KDUMP] [PROPOSED WORK] kdump on Xen hypervisor and guests, more tests for utilities, like makedumpfile, mkdumprd, kexec etc
Hi Cai, Some patches in Bits and Pieces regarding this nearby ? Regards-- Subrata > > Yes. Initally, I put this item to a relative low priority, partly > because kdump config options and init scripts are tend to be > distro-specific, so it won't be easy to write portable tests for > different distros. In addition, lots of config options are not easy to > be tested automately, like raw disk target, vfat disk target, and > network target etc, as testers have to setup those name manually. But, > you are right, those are high priority tests for kexec/kdump in distro > release, we tested most of those options manually for RHEL anyway and we > had some automated tests of it, which I'll try to submit to LTP as many > as possible. For those manual tests, I'll also try to find some ways to > automate them. For example, for different dump targets, it is possible > to verify the generated initrd file as expected. > > > > > > == increase coverages for new kexec/kdump development efforts == > > > - new reserved region syntax in Kernel. > > > > Another important thing we need to focus on is driver testing. Drivers > > can fail to initialize in second kernel and kdump will fail. Can we do > > something so that we can do following. > > > > That isn't something I have not thought of. For RHEL release testing, we > will have a workflow to run those tests on any storage/network drivers, > and it will report back testing results and driver matrix. However, this > workflow is very distro-specific, and depends on the test farm it is > using, so it does not make any sense to put it here. > > > - Collect the machine statistics on which kdump was tested and send > > the reports to a common place. Especially capture the storage/network > > driver data which can be probably be available through LTP site. > > > > That sounds like a good idea to me. > > > - Also capture how much memory was reserved on what architecture and > > whether it worked or not. This will help us verify for sure that how > > much memory to reserve for second kernel on various architectures. > > > > This is something could be done. I'll have a look at it. > > Thanks, > CaiQian > > > Thanks > > Vivek ___ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec
[RFC] [KDUMP] [PROPOSED WORK] kdump on Xen hypervisor and guests, more tests for utilities, like makedumpfile, mkdumprd, kexec etc
Hi, Cai has proposed to work on the above LTP-KDUMP test cases enrichment/enhancements. Please let us know about your views on the same. We encourage people to review his proposal and the corresponding upcoming test cases. I am going to put this soon on the LTP-KDUMP plan document. http://ltp.cvs.sourceforge.net/ltp/ltp/testcases/kdump/doc/TEST_PLAN.txt, Regards-- Subrata .. Here is my first draft plan of Kexec/Kdump tests enhancement sorted by priorities. I would like to add them as many as possible. == filtered vmcore utilities == - in different compressed levels, verify the vmcore with the correct layout. - verify it in flat file or ELF formats from a network host. == analyse vmcore utilities == - GDB - crash with better error detecting. - crash to analyse Hypervisor and Dom0 Kernel. == test scripts == - timestamp information for crash was triggered, vmcore was generated, and vmcore was verified. - aim to 100% automation, and reduce manual setup. - tidy up scripts. == crash scenarios == - SDINT switch for ia64 if possible. - Hypervisor crash for Virtualization. - crashes on full- and para-virt guests. == fix bugs in existing tests == - printk LKDTM module can hang the second Kernel. == kdump configurations and init script == - capture vmcore after init runs. - rpm pre- and post-scripts - kdump_pre and kdump_post directives == increase coverages for new kexec/kdump development efforts == - new reserved region syntax in Kernel. CaiQian ___ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec
[ANNOUNCE] The Linux Test Project has been Released for NOVEMBER 2007
ubmitted by Khem Raj <[EMAIL PROTECTED]> File(s) Affected: ltp/testcases/kernel/mem/shmt/shmt09.c 15) Log Message: New posix_fadvise and fadvise64 Testcases contributed by Masatake YAMATO <[EMAIL PROTECTED]> File(s) Affected: ltp/runtest/syscalls New File(s) Addes: ltp/testcases/kernel/syscalls/fadvise/Makefile ltp/testcases/kernel/syscalls/fadvise/posix_fadvise01.c ltp/testcases/kernel/syscalls/fadvise/posix_fadvise02.c ltp/testcases/kernel/syscalls/fadvise/posix_fadvise03.c ltp/testcases/kernel/syscalls/fadvise/posix_fadvise04.c 16) Log Message: Existing code in LTP Kdump has been enhanced to test dump on network and different partitions. The attached patch supports following features -Dump on EXT3 partition, partition referenced by partition name, Label and UUID -Dump on raw partition -Dump on Network dump server -Test dump filtering feature of Kdump -Test Link Delay feature of Kdump -Result analysis has been implemented for local dumping and network dumping. -Result analysis has been implemented for filtering as well as link delay. But the analysis part can be enahnced further -'setup' file has been modified * To accept inputs from user or file * To automate configuration of bootloader file to reserve memory for crashkernel * To test basic or exchausted list of LKDTM test * To accept user inputs for dumping on different partitions and for network dumping -'master' file has been modified *To invoke result analysis code of dumping in different destinations *to remove cronjob when execution is done, this is a bug fix -'test' file has been modifed *To set kdump.conf file based on user input and trigger crash -'Makefile' has been modified not to run 'setup' -Added new files *kdump_propogate ->To add ssh public keys to network dump server *verify_dump ->To verify dump in different partitions and network dumping *lkdtm.orig is replaced with lkdtm.base for basic testcases of lkdtm, lkdtm.exha for exhausted list of lkdtm testcases. Submitted by: Poornima Nayak <[EMAIL PROTECTED]> File(s) Affected: ltp/testcases/kdump/Makefile ltp/testcases/kdump/README ltp/testcases/kdump/TEST_PLAN.txt ltp/testcases/kdump/master ltp/testcases/kdump/setup ltp/testcases/kdump/test File(s) Added: ltp/testcases/kdump/kdump_propagate ltp/testcases/kdump/verify_dump ltp/testcases/kdump/testlists/lkdtm.base ltp/testcases/kdump/testlists/lkdtm.exha File(s) Removed: ltp/testcases/kdump/testlists/lkdtm.orig 17) Log Message: Fix endless loop hit messages for kdump test case, by Cai Qian <[EMAIL PROTECTED]> File(s) Affected: ltp/testcases/kdump/rhtools/lkdtm_mod/lkdtm.c 18) Log Message: Fix for vmcore generation and vmcore verification are at different hours, by Cai Qian <[EMAIL PROTECTED]> File(s) Affected: ltp/testcases/kdump/master 19) Log Message: Changes that allows adp to run top on batch mode instead of interactively, submitted by Rafael Folco <[EMAIL PROTECTED]> File(s) Affected: ltp/testscripts/adp.sh 20) Log Message: Changes to prevent fcntl14 test case to crash on uclinux on blackfin board, submitted by Vivi <[EMAIL PROTECTED]> File(s) Affected: ltp/testcases/kernel/syscalls/fcntl/fcntl14.c 21) Log Message: New HTML format for LTP Output File(s) Affected: ltp/runltp File(s) Added: ltp/tools/genhtml.pl ltp/tools/html_report_header.txt 22) Log Message: Add IA64 support to kdump test case, submitted by Cai Qian <[EMAIL PROTECTED]> File(s) Affected: ltp/testcases/kdump/setup 23) Log Message: Patch to fix summary script of LTP kdump (can't retrieve LOG correctly), submitted by Lin Feng Shen ([EMAIL PROTECTED]) File(s) Affected: ltp/testcases/kdump/summary 24) Log Message: Fix for master script of LTP kdump (Which tries to copy /proc/config.gz though it's not available), submitted by Cijurajan Kollanoor ([EMAIL PROTECTED]) File(s) Affected: ltp/testcases/kdump/master 25) Log Message: Report TCONF for swapon/off test when run on tmpfs or nfs, submitted by Kumar Gala <[EMAIL PROTECTED]> File(s) Affected: testcases/kernel/syscalls/swapoff/swapoff01.c testcases/kernel/syscalls/swapoff/swapoff02.c testcases/kernel/syscalls/swapon/swapon01.c testcases/kernel/syscalls/swapon/swapon02.c testcases/kernel/syscalls/swapon/swapon03.c 26) Log Message: This does testing for the missing functionalities of MADV_REMOVE, MADV_DONTFORK & MADV_DOFORK, submitted by Pavan, [EMAIL PROTECTED] File(s) Added: ltp/testcases/kernel/syscalls/madvise/madvise03.c 27) Log Message: Added an Option to mail-back LTP reports, by Subrata Modak <[EMAIL PROTECTED]> File(s) Affected: ltp/runltp 28) Log Message: Added sendfile64 support and new testcase sendfile04.c in this regard, by Masatake YAMATO <[EMAIL PROTECTED]> File(s) Affected: runtest/syscalls testcases/kernel/syscalls/sendfile/Makefile testcases/kernel/syscalls/sendfile/sendfile02.c test
[ANNOUNCE] The Linux Test Project has been Released for SEPTEMBER 2007
Dear All, The Linux Test Project test suite has been released for the month of SEPTEMBER 2007. The latest version of the test-suite contains 3000+ tests for the Linux OS and can be found at http://ltp.sourceforge.net/. Latest happenings in LTP can also be found at: http://ltp.sourceforge.net/wiki/, http://ltp.sourceforge.net/wikiArchives.php, and, IRC: irc.freenode.org #ltp. Our web site also contains other information such as: - A Linux test tools matrix - Technical papers - How To's on Linux testing - Code coverage analysis tool. Release Highlights: * Enabling Kernel Version Comparisns for Lots of Testcase(s), * Removal of Connectathon Testcases for want of GPLV2 license, * Patching of NUMA Testcases for better Statistics Collection, * Fixes for KDUMP scripts errors, * Mandatory generation of failed testcases file, * Fix of LTP output format as pointed out by Andrew Morton, * Update of OPENHPI testsuite to 2.10.0, Note(s) from the Maintainer: LTP output will see new formats in the coming days. This will make interpreting output more easily and conceptually. Hope that Real Time Linux Testcases will see the light of the day by this month end. We would encourage the community to post results to [EMAIL PROTECTED], patches, new tests, bugs or comments/questions to [EMAIL PROTECTED], http://sourceforge.net/tracker/?func=add&group_id=3382&atid=103382 (for New Bug(s)), http://sourceforge.net/tracker/?func=add&group_id=3382&atid=303382 (for New Patch(s)), http://sourceforge.net/tracker/?func=add&group_id=3382&atid=353382 (for New Feature Request(s)) Please also see the ChangeLog Attached (SEPTEMBER 2007): Happy testing, Regards-- Subrata, 1) Log Message: "[EMAIL PROTECTED]" wanted to fix some anomalies in "acct01" testcase File(s) Affected: ltp/testcases/kernel/syscalls/acct/acct01.c 2) Log Message: "[EMAIL PROTECTED]" made modifications to check whether the Kernel is UTSNAMESPACE or SYSVIPC_NAMSPACE enabled File(s) Affected: ltp/testcases/kernel/containers/container_test.sh ltp/testcases/kernel/containers/sysvipc/Makefile File(s) Added: ltp/testcases/kernel/containers/sysvipc/check_ipcns_enabled.c 3) Log Message: "[EMAIL PROTECTED]" fixed exit code for inotify01 and inotify02 when running with kernel < 2.6.13 File(s) Affected: ltp/testcases/kernel/syscalls/inotify/inotify01.c ltp/testcases/kernel/syscalls/inotify/inotify02.c 4) Log Message: Fixing "ioperm02" testcase for kernel comparisns File(s) Affected: ltp/testcases/kernel/syscalls/ioperm/ioperm02.c 5) Log Message: "[EMAIL PROTECTED]" induced time for Statistics collection in RHEL File(s) Affected: ltp/testcases/kernel/numa/numa01.sh 6) Log Message: Removing these Testcases as they do not satisfy GPLv2 License Agreement File(s) Deleted: ltp/testcases/network/nfs/cthon04 Makefile README READWIN.txt Testitems domount.c getopt.c runtests server tests.h tests.init unixdos.h ltp/testcases/network/nfs/cthon04/basic Makefile runtests runtests.mvs subr.c test1.c test2.c test3.c test4.c test4a.c test5.c test5a.c test5b.c test6.c test7.c test7a.c test7b.c test8.c test9.c ltp/testcases/network/nfs/cthon04/basic/console build.bat test1.mak test2.mak test3.mak test4a.mak test4.mak test5a.mak test5b.mak test5.mak test6.mak test7a.mak test7b.mak test7.mak test8.mak test9.mak ltp/testcases/network/nfs/cthon04/basic/dos build.bat test1.mak test2.mak test3.mak test4a.mak test4.mak test5a.mak test5b.mak test5.mak test6.mak test7a.mak test7b.mak test7.mak test8.mak test9.mak ltp/testcases/network/nfs/cthon04/basic/scripts basic2.bat basic3.bat basic.bat cthon00.mst cthon01.mst cthon02.mst cthon03.mst cthon04.mst cthon.bat runcthon.prl ltp/testcases/network/nfs/cthon04/general large4.sh large.c Makefile makefile.tst mkdummy nroff.in rmdummy runtests runtests.wrk stat.c ltp/testcases/network/nfs/cthon04/lock Makefile runtests tlock.c ltp/testcases/network/nfs/cthon04/special bigfile2.c bigfile.c dupreq.c excltest.c freesp.c fstat.c holey.c Makefile negseek.c nfsidem.c nstat.c op_chmod.c op_ren.c op_unlk.c READWIN.txt rename.c rewind.c runtests runtests.wrk stat2.c stat.c telldir.c touchn.c truncate.c ltp/testcases/network/nfs/cthon04/special/console build1.bat build.bat dupreq.mak excltest.mak fstat.mak holey.mak negseek.mak nfsidem.mak nstat.mak op_chmod.mak op_ren.mak op_unlk.mak rename.mak rewind.mak stat2.mak stat.mak touchn.mak truncate.mak ltp/testcases/network/nfs/cthon04/special/dos build1.bat build.bat dupreq.mak excltest.mak fstat.mak holey.mak negseek.mak nfsidem.mak nstat.mak op_chmod.mak op_ren.mak op_unlk.mak rename.mak rewind.mak stat2.mak stat.mak touchn.mak truncate.mak ltp/testcases/network/nfs/cthon04/special/scripts run.bat ltp/testcases/network/nfs/cthon04/tools dirdmp.c dirprt.c Makefile pmapbrd.c pmaptst.c README tcp.c tcpd.c udp.c udpd.c 7) Log Message: This guides you to the new location of
[ANNOUNCE] The Linux Test Project has been Released for AUGUST 2007
*Dear All*, The Linux Test Project test suite has been released for the month of AUGUST 2007. The latest version of the test-suite contains 3000+ tests for the Linux OS and can be found at http://ltp.sourceforge.net/. Latest happenings in LTP can also be found at: http://ltp.sourceforge.net/wiki/, and http://ltp.sourceforge.net/wikiArchives.php. Our web site also contains other information such as: - A Linux test tools matrix - Technical papers - How To's on Linux testing - Code coverage analysis tool. *Release Highlights:* ** * Integration of NUMA testcases* * *Releases of RHEL5 LSPP Certification Test suite*** * * Release of LTP-KDUMP Test-Case Plan* * * Release of Containers Testcases Plan* * * Release of GCOV-Kernel & LCOV Packages* ** Merging of OPEN_HPI_TESTSUITE-2.9.3 to LTP* * Addition of a new Test Case 'swapon03' * Many more Bug Fixes and Patches * *Note(s) from the Maintainer:* You will see couple of new test-cases in LTP in coming months and also broken testcases getting fixed slowly. We want to revisit all testcases and hence the time taken is long. From every release onwards you will also find results of LTP-RUNALL on different Architectures (_*ia64, x86_64, i386, PPC64, s390x*_) on varied Kernels & Distros. This will give you more insight into the behaviour of LTP across different platforms. We encourage the community to post results to [EMAIL PROTECTED], and patches, new tests, bugs or comments/questions to [EMAIL PROTECTED], http://sourceforge.net/tracker/?func=add&group_id=3382&atid=103382 (for New Bug(s)), http://sourceforge.net/tracker/?func=add&group_id=3382&atid=303382 (for New Patch(s)), http://sourceforge.net/tracker/?func=add&group_id=3382&atid=353382 (for New Feature Request(s)) Please also see the ChangeLog Attached (AUGUST 2007): Happy testing, Regards-- Subrata Modak, 1) Log Message: "[EMAIL PROTECTED]" fixed write05 that failed with LTP 20070331 on Fedora 7 GA File(s) Affected: ltp/testcases/kernel/syscalls/write/write05.c 2) Log Message: "[EMAIL PROTECTED]" corrected fail message in data_space testcase File(s) Affected: ltp/testcases/kernel/mem/vmtests/data_space.c 3) Log Message: "[EMAIL PROTECTED]" made mmap1 to be terminated by Ctrl-C File(s) Affected: ltp/testcases/kernel/mem/mtest06/mmap1.c 4) Log Message: "[EMAIL PROTECTED]" fixed times03, where it failed to generate report on user time on RHEl5.1 early build(2.6.18-32.el5) File(s) Affected: ltp/testcases/kernel/syscalls/times/times03.c 5) Log Message: gcov-kernel: added eabi-compatibility patch, renamed .diff to .patch by "[EMAIL PROTECTED]" File(s) Added: ltp/utils/analysis/gcov-kernel/linux-2.6.21-gcov-arm-eabi.patch ltp/utils/analysis/gcov-kernel/linux-2.6.22-gcov-arm-eabi.patch File(s) Deleted: ltp/utils/analysis/gcov-kernel/linux-2.6.21-gcov-arm-eabi.diff 6) Log Message: lcov: fixed spec file File(s) Affected: ltp/utils/analysis/lcov/rpm/lcov.spec 7) Log Message: gcov-kernel: removed outdated FAQ entry File(s) Affected: ltp/utils/analysis/gcov-kernel/FAQ 8) Log Message: gcov-kernel: added Makefile File(s) Added: ltp/utils/analysis/gcov-kernel/Makefile 9) Log Message: lcov: Makefile for release 1.6 File(s) Affected: /cvsroot/ltp/utils/analysis/lcov/Makefile 10) Log Message: lcov: Makefile for post-release File(s) Affected: /cvsroot/ltp/utils/analysis/lcov/Makefile 11) Log Message: lcov: add experimental option "--norecursion" File(s) Affected: /cvsroot/ltp/utils/analysis/lcov/bin/geninfo /cvsroot/ltp/utils/analysis/lcov/bin/lcov 12) Log Message: Changes to make testcases/kernel/numa/numa01.sh executable File(s) Affected: ltp/testcases/kernel/numa/Makefile 13) Log Message: "[EMAIL PROTECTED]" changed the Default values for MAXSIZE and csize File(s) Affected: ltp/testcases/kernel/mem/vmtests/stack_space.c 14) Log Message: "[EMAIL PROTECTED]" wanted to handle file descriptors properly File(s) Affected: ltp/testcases/kernel/syscalls/mkdir/mkdir03.c ltp/testcases/kernel/syscalls/mmap/mmap09.c ltp/testcases/kernel/syscalls/open/open07.c ltp/testcases/kernel/syscalls/sendfile/sendfile03.c 15) Log Message: "[EMAIL PROTECTED]" says that this version can handle when the distro has MAX_SWAPFILES as 30 or 32 File(s) Modified: ltp/runtest/ltplite ltp/runtest/stress.part3 ltp/runtest/syscalls ltp/testcases/kernel/syscalls/swapon/swapon02.c File(s) Added: ltp/testcases/kernel/syscalls/swapon/swapon03.c 16) Log Message: Containers Testcases Plan File(s) Added: ltp/testcases/kernel/containers/TEST_PLAN.txt 17) Log Message: LTP-KDUMP Test-Case Plan File(s) Added: ltp/testcases/kdump/TEST_PLAN.txt 18) Log Message: Update to OpenHPI 2.9.3 (www.openhpi.org for more info) File(s) Affected: ltp/testcases/open_hpi_testsuite/ ___ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec
LTP-KDUMP Test Plan
Please find attached the Tentative LTP-KDUMP Test case Plan, depicting the future work that will be done on LTP-KDUMP. Regards-- Subrata Following is the Tentative plan for improving LTP-KDUMP Test-cases: === ||S.NO|| ACTIVITY || TENTATIVE-TIME || === || 1 || Test and integrate kdump's netdump patch to LTP || SEP/OCT-2007|| || 2 || Modify ltp-kdump to automate all usecases of || SEP/OCT-2007|| ||||kdump-network dumping usecases || || || 3 || Enhance error handler for kdump test || OCT/NOV-2007|| ||||automation script || || || 4 || Enhance result analysis module of ltp-kdump || OCT/NOV-2007|| === ___ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec
[ANNOUNCE] The Linux Test Project has been Released for JULY 2007
cases/kernel/io/ltp-aiodio/fsx-linux.c ltp/testcases/network/nfs/fsx-linux/fsx-linux.c 12) Log Message: Randy Dunlap writes: Fix printf format warnings File(s) Affected: ltp/testcases/network/stress/ns-tools/Makefile ltp/testcases/network/stress/ns-tools/ns-igmp_querier.c ltp/testcases/network/stress/ns-tools/ns-mcast_join.c ltp/testcases/network/stress/ns-tools/ns-mcast_receiver.c ltp/testcases/network/stress/ns-tools/ns-tcpserver.c 13) Log Message: getsockopt() takes a socklen_t, not an int, as its optlen File(s) Affected: ltp/testcases/network/stress/ns-tools/ns-tcpclient.c ltp/testcases/network/stress/ns-tools/ns-tcpserver.c ltp/testcases/network/stress/ns-tools/ns-udpserver.c 14) Log Message: cleanup file File(s) Affected: ltp/testcases/kernel/syscalls/gethostid/gethostid01.c 15) Log Message: back out uclinux changes to something that doesnt spit warnings as reported by Randy Dunlap File(s) Affected: ltp/testcases/kernel/syscalls/gethostid/gethostid01.c 16) Log Message: fixup gcc warnings by removing silly pieces of code File(s) Affected: ltp/testcases/kernel/mem/mtest06/mmap1.c ltp/testcases/kernel/mem/mtest06/mmap2.c ltp/testcases/kernel/mem/mtest06/mmap3.c ltp/testcases/kernel/mem/mtest06/shmat1.c 17) Log Message: Randy Dunlap writes: Convert mmap1 to use standard test results output format. Correct several typos. File(s) Affected: ltp/testcases/kernel/mem/mtest06/Makefile ltp/testcases/kernel/mem/mtest06/mmap1.c 18) Log Message: gcov-kernel: adding gcov-kernel patch for 2.6.22 File(s) Addes: ltp/utils/analysis/gcov-kernel/linux-2.6.22-gcov-arm-hack.patch ltp/utils/analysis/gcov-kernel/linux-2.6.22-gcov.patch 19) Log Message: [1754301] Helge Deller writes: mark hppa/parisc as expecting a segv as well File(s) Affected: ltp/testcases/kernel/syscalls/mmap/mmap03.c 20) Log Message: Randy Dunlap writes: convert output to match the standard LTP output File(s) Affected: ltp/testcases/kernel/fs/linktest/linktest.pl 21) Log Message: close stdout to remove noise File(s) Affected: ltp/testcases/kernel/mem/mtest05/dummy.c 22) Log Message: Randy Dunlap writes: Convert mmstress to use the standard results format File(s) Affected: ltp/testcases/kernel/mem/mtest05/Makefile ltp/testcases/kernel/mem/mtest05/mmstress.c 23) Log Message: "[EMAIL PROTECTED]" updated the contact information at ltp-howto doc File(s) Affected: ltp/doc/ltp-howto.lyx ltp/doc/ltp-howto.txt 24) Log Message: "[EMAIL PROTECTED]" wants to update this with kernel/fs/fsstress/fsstress.c File(s) Affected: ltp/testcases/network/nfs/nfs_fsstress/fsstress.c 25) Log Message: "[EMAIL PROTECTED]" added SIGNAL and Address Fault handling capability for all architectures File(s) Affected: ltp/testcases/kernel/mem/mtest06/mmap1.c 26) Log Message: "[EMAIL PROTECTED]" added more options to 'runltp' File(s) Affected: ltp/runltp ltp/doc/man1/pan.1 ltp/pan/pan.c 27) Log Message: Upgrade to Posix Testsuite 1.5.2 File(s) Affected/Added: ltp/testcases/open_posix_testsuite 28) Log Message: Fixing Proper Freeing of Memory Chunks File(s) Affected: ltp/tools/genload/stress.c Happy testing, Regards-- Subrata Modak, ___ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec
[ANNOUNCE] LTP Roadmap Released
Hi All, Sometime back we started retrospection on LTP and the various ways to make it better. It resulted in critical evaluation of LTP within & outside LTP users community. It also reflected the various ways on making it more better and effective. Working in this direction, we have come up with a road map which we feel will be helpful to the community. The following wiki pages will throw some light on the same: * http://ltp.sourceforge.net/wiki/ * http://ltp.sourceforge.net/wikiArchives.php Your comments on the contents and the goals set will be highly appreciated. All comments will be published on the above wiki pages. Regards & Thanks-- Subrata Modak ___ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec
[ANNOUNCE] The Linux Test Project has been Released for June 2007,
IX displays warnings File(s) Affected: open_posix_testsuite/conformance/interfaces/sem_unlink/2-2.c open_posix_testsuite/conformance/interfaces/sigaltstack/9-1.c 8)Log Message: "[EMAIL PROTECTED]" corrected the way by which pthread_exit() handles pointer argument File(s) Affected: ltp/testcases/kernel/io/disktest/threading.h 9)Log Message: "[EMAIL PROTECTED]" fixed the problem reported at bug [1732287] mtest06/mmap1.c missing run_once check in do loop File(s) Affected: ltp/runtest/ltplite ltp/runtest/mm ltp/runtest/stress.part1 ltp/testcases/kernel/mem/mtest06/mmap1.c 10)Log Message: gcov-kernel: add patches to support arm eabi-compliant gcc File(s) Affected: /ltp/utils/analysis/gcov-kernel/linux-2.6.18-gcov-arm-eabi.patch /ltp/utils/analysis/gcov-kernel/linux-2.6.19-gcov-arm-eabi.patch /ltp/utils/analysis/gcov-kernel/linux-2.6.20-gcov-arm-eabi.patch /ltp/utils/analysis/gcov-kernel/linux-2.6.21-gcov-arm-eabi.diff 11)Log Message: "[EMAIL PROTECTED]" added this test case to check for "fault in pages readable" functionality File(s) Affected: ltp/runtest/stress.part3 ltp/runtest/syscalls ltp/runtest/ltplite File(s) Added:ltp/testcases/kernel/syscalls/writev/writev06.c 12)Log Message: "[EMAIL PROTECTED]" added sysvipc (conatainers) namespace testcases File(s) Added:ltp/testcases/kernel/containers/sysvipc/Makefile ltp/testcases/kernel/containers/sysvipc/runipcnstest.sh ltp/testcases/kernel/containers/sysvipc/runtests_noltp.sh ltp/testcases/kernel/containers/sysvipc/shmnstest.c File(s) Affected: ltp/README ltp/testcases/kernel/containers/Makefile ltp/testcases/kernel/containers/README ltp/testcases/kernel/containers/container_test.sh 13)Log Message: Randy Dunlap writes: Convert kernel/sched/pthreads/*.c to use the standard message output functions instead of printf(). File(s) Affected: ltp/testcases/kernel/sched/pthreads/pth_str01.c ltp/testcases/kernel/sched/pthreads/pth_str02.c ltp/testcases/kernel/sched/pthreads/pth_str03.c 14)Log Message: "[EMAIL PROTECTED]" did "mmstress" cleanups to make output unbuffered so that it is not produced repetitively and erroneously File(s) Affected: ltp/testcases/kernel/mem/mtest05/mmstress.c 15)Log Message: "[EMAIL PROTECTED]" wants to solve segfault problem with "mount03" on SLES10 File(s) Affected: ltp/testcases/kernel/syscalls/mount/Makefile ltp/testcases/kernel/syscalls/mount/mount03.c 16)Log Message: as Ricardo Salveti de Araujo points out, dont set CC so it can easily be overridden File(s) Affected: ltp/testcases/kernel/containers/utsname/Makefile 17)Log Message: "Andreas Dilger" updated "fsx-linux" testcase to include new feature(s) including distributed filesystem coherency Log Message:Copyright Statements once added cannot be deleted, however, many Copyright Statements can co-exist File(s) Affected: ltp/testcases/kernel/fs/fsx-linux/fsx-linux.c 18)Log Message: Fix from "[EMAIL PROTECTED]" to use standard test results output File(s) Affected: ltp/testcases/kernel/mem/mem/mem01.c ltp/testcases/kernel/mem/mtest01/Makefile ltp/testcases/kernel/mem/mtest01/mtest01.c ltp/testcases/misc/math/float/main.c 19)Log Mesage: "[EMAIL PROTECTED]" fixes conatiner testing with 'unshare' support for lower kernel versions File(s) Affected: ltp/testcases/kernel/containers/Makefile ltp/testcases/kernel/containers/container_test.sh 20)Log Message: Fix for Bug no "1736357",tar file is not multiplatform, pointed out by "Neil Brewitt" File(s) Added:ltp/testcases/network/nfsv4/locks/deploy_info File(s) Deleted: ltp/testcases/network/nfsv4/locks/DEPLOY 21)Log Message: "[EMAIL PROTECTED]" fixes conatiner testing with 'unshare' support for lower kernel versions File(s) Added:ltp/testcases/kernel/containers/check_for_unshare.c 22)Log Message: Update to OpenHPI 2.9.2 File(s) Addedd/Modified/Deleted: ltp/testcases/open_hpi_testsuite/ Happy testing, Regards & Thanks-- Subrata Modak, ___ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec
