* Re: [LTP] Reg: Script to extract description of test case from LTPROOT/doc/testcases/*.txt files
[not found] ` <1245346284.5041.31.camel@subratamodak.linux.ibm.com>
@ 2009-06-19 6:30 ` rohit verma
2009-06-23 14:50 ` Subrata Modak
0 siblings, 1 reply; 10+ messages in thread
From: rohit verma @ 2009-06-19 6:30 UTC (permalink / raw)
To: LTP List
[-- Attachment #1: Type: text/plain, Size: 9629 bytes --]
Hi all,
PFA the patch which formats the LTP documentation in 'ltp/doc/testcases' folder.
Note: The formatting is applied to only kernel, misc, network and
commands test-cases.
Formatting used is based on my ideas and comments from Subrata.
Comments on the same are welcome.
Regards,
Rohit
On Thu, Jun 18, 2009 at 11:01 PM, Subrata
Modak<subrata@linux.vnet.ibm.com> wrote:
> Hi,
>
> I think this is good to start with. Send them to LTP mailing list as a
> patch.
>
> Regards--
> Subrata
>
> On Mon, 2009-06-15 at 14:11 +0530, rohit verma wrote:
>> Hi,
>>
>> PFA the formatted documentation for network,kernel,misc and command
>> test-cases. I have verified the document with the original one. Both
>> data match except for the formatting pretty much. However, if u notice
>> any inconsistency, do let me know.
>>
>> Regards,
>> Rohit
>>
>> On Thu, Jun 4, 2009 at 4:12 PM, Subrata Modak<subrata@linux.vnet.ibm.com> wrote:
>> > On Thu, 2009-06-04 at 15:42 +0530, rohit verma wrote:
>> >> Hi,
>> >>
>> >> Yes. I am writing a script that can do the formatting job.
>> >>
>> >> Following is the format that I have used:
>> >>
>> >> <testname=stress_cd>
>> >> <description>
>> >> Creates multiple read threads on the cdrom device.
>> >> <\description>
>> >> <test_location>
>> >> ./testcases/kernel/io/stress_cd/stress_cd.c
>> >> <\test_location>
>> >> <\testname>
>> >>
>> >> Is there any way i can find out the full path of the test-case, other
>> >> than using 'find' command?
>> >>
>> >
>> > Go out of ltp-* directory, and then do find.
>> >
>> > So, you will get:
>> > ./ltp/testcases/kernel/io/stress_cd/stress_cd.c
>> >
>> > Then do find-&-replace of
>> > ./ltp
>> > with
>> > ltp
>> >
>> >> Let me know if the format is fine.
>> >>
>> >
>> > OK.
>> >
>> > Regards--
>> > Subrata
>> >
>> >> Regards,
>> >> Rohit
>> >>
>> >>
>> >> On Thu, Jun 4, 2009 at 2:57 PM, Subrata Modak
>> >> <subrata@linux.vnet.ibm.com> wrote:
>> >> > On Wed, 2009-05-27 at 19:53 +0530, Subrata Modak wrote:
>> >> >> On Wed, 2009-05-27 at 00:18 -0700, rohit verma wrote:
>> >> >> > Hi Subrata,
>> >> >> >
>> >> >> > As the purpose of this document is to brief the description of each
>> >> >> > test case to user. I feel that your format would decrease the
>> >> >> > readability in document .
>> >> >> >
>> >> >> > So should we include following tags "test_location",
>> >> >> > "test_cmdfile_name", "test_cmdfile_entry",
>> >> >> > "Execute_through_commandline", "Execute_through_runltp". or only
>> >> >> > description tag would be sufficient.
>> >> >>
>> >> >> Fine then, but i would insist you to include "testname" &
>> >> >> "test_location" apart from "test_description".
>> >> >
>> >> > Rohit,
>> >> >
>> >> > Are you working on this ?
>> >> >
>> >> > Regards--
>> >> > Subrata
>> >> >
>> >> >>
>> >> >> Regards--
>> >> >> Subrata
>> >> >>
>> >> >> >
>> >> >> > Regards,
>> >> >> > rohit
>> >> >> >
>> >> >> >
>> >> >> > On Tue, May 26, 2009 at 5:22 AM, Subrata Modak
>> >> >> > <subrata@linux.vnet.ibm.com> wrote:
>> >> >> > > On Mon, 2009-05-25 at 21:40 -0700, rohit verma wrote:
>> >> >> > >> Hi Subrata,
>> >> >> > >>
>> >> >> > >> I request you to finalize the format of the documentation ASAP.
>> >> >> > >
>> >> >> > > I would like to see something like:
>> >> >> > >
>> >> >> > > <testname=abort(3)>
>> >> >> > > <test_description="Basic test for abort(3)">
>> >> >> > > <\test_description>
>> >> >> > > <test_location="ltp/testcases/kernel/syscalls/abort/abort01.c">
>> >> >> > > <\test_location>
>> >> >> > > <test_cmdfile_name="ltp/runtest/syscalls">
>> >> >> > > <\test_cmdfile_name>
>> >> >> > > <test_cmdfile_entry="abort01 ulimit -c 1024;abort01">
>> >> >> > > <\test_cmdfile_entry>
>> >> >> > > <Execute_through_commandline="ulimit -c
>> >> >> > > 1024; ./ltp/testcases/bin/abort01">
>> >> >> > > <\Execute_through_commandline>
>> >> >> > > <Execute_through_runltp="./runltp -s abort01">
>> >> >> > > <\Execute_through_runltp>
>> >> >> > > <\testname>
>> >> >> > >
>> >> >> > > The basic idea is to include all important information as we can when we
>> >> >> > > are doing some patching on this. Let me know how others feel, and how we
>> >> >> > > can achieve this.
>> >> >> > >
>> >> >> > > Regards--
>> >> >> > > Subrata
>> >> >> > >
>> >> >> > >>
>> >> >> > >> Ltp-list : Please provide the inputs regarding the text documentation format.
>> >> >> > >>
>> >> >> > >> Regards,
>> >> >> > >> rohit
>> >> >> > >>
>> >> >> > >> On Tue, May 19, 2009 at 3:31 AM, Subrata Modak
>> >> >> > >> <subrata@linux.vnet.ibm.com> wrote:
>> >> >> > >> > Hi Rohit,
>> >> >> > >> >
>> >> >> > >> > On Mon, 2009-05-18 at 19:21 +0800, CAI Qian wrote:
>> >> >> > >> >> From: rohit verma <rohit.170309@gmail.com>
>> >> >> > >> >> Subject: Re: Reg: Script to extract description of test case from LTPROOT/doc/testcases/*.txt files
>> >> >> > >> >> Date: Mon, 18 May 2009 04:55:54 -0700
>> >> >> > >> >>
>> >> >> > >> >> > Dear Subrata/Qian,
>> >> >> > >> >> >
>> >> >> > >> >> > I am trying to develop script which would extracts description information
>> >> >> > >> >> > about user required test case from LTPROOT/doc/testcases/ folder.
>> >> >> > >> >> >
>> >> >> > >> >> > So to make the description text file as standard file, can we represent the
>> >> >> > >> >> > description as mentioned below.
>> >> >> > >> >> >
>> >> >> > >> >> > For example in syscalls category:
>> >> >> > >> >> >
>> >> >> > >> >> > Currently available format of description in LTP as follows.
>> >> >> > >> >> >
>> >> >> > >> >> > abort01
>> >> >> > >> >> > Basic test for abort(3).
>> >> >> > >> >> >
>> >> >> > >> >> > accept01
>> >> >> > >> >> > Verify that accept() returns the proper errno for various failure cases
>> >> >> > >> >> >
>> >> >> > >> >> >
>> >> >> > >> >> > To make it in consistent way, description should be enclosed by executables
>> >> >> > >> >> > as follows.
>> >> >> > >> >> >
>> >> >> > >> >> > <abort01>
>> >> >> > >> >> > Basic test for abort(3).
>> >> >> > >> >> > <\abort01>
>> >> >> > >> >> >
>> >> >> > >> >> > <accept01>
>> >> >> > >> >> > Verify that accept() returns the proper errno for various failure cases
>> >> >> > >> >> > <\accept01>
>> >> >> > >> >> >
>> >> >> > >> >> > Please confirm if this format is O.K or suggest any other format by which we
>> >> >> > >> >> > can easily parse the test cases and extracts the description.
>> >> >> > >> >
>> >> >> > >> > Itś always great to see somebody working on LTP documentation. So, lets
>> >> >> > >> > ask the community also for their opinion as well. Can we also include
>> >> >> > >> > some more tags for more descriptive info ?
>> >> >> > >> >
>> >> >> > >> > Regards--
>> >> >> > >> > Subrata
>> >> >> > >> >
>> >> >> > >> >> >
>> >> >> > >> >>
>> >> >> > >> >> Looks good for me.
>> >> >> > >> >>
>> >> >> > >> >> CAI Qian
>> >> >> > >> >>
>> >> >> > >> >> > If this format is O.K , I would send the patch for those text files
>> >> >> > >> >> >
>> >> >> > >> >> > Regards,
>> >> >> > >> >> > Rohit
>> >> >> > >> >> >
>> >> >> > >> >> >
>> >> >> > >> >> >
>> >> >> > >> >> > On Wed, May 13, 2009 at 7:55 AM, CAI Qian <caiqian@cclom.cn> wrote:
>> >> >> > >> >> >
>> >> >> > >> >> >> From: rohit verma <rohit.170309@gmail.com>
>> >> >> > >> >> >> Subject: Reg: Script to extract description of test case from
>> >> >> > >> >> >> LTPROOT/doc/testcases/*.txt files
>> >> >> > >> >> >> Date: Wed, 13 May 2009 02:16:57 -0700
>> >> >> > >> >> >>
>> >> >> > >> >> >> > Dear Subrata/qian,
>> >> >> > >> >> >> >
>> >> >> > >> >> >> > As if we run LTP testcases, nowhere LTP test suite populates the
>> >> >> > >> >> >> > description of testcases (either in .log, .output, .HTML or .failed
>> >> >> > >> >> >> > test cases files).
>> >> >> > >> >> >> >
>> >> >> > >> >> >> > Description of each test case in category wise is available in
>> >> >> > >> >> >> > LTPROOT/doc/testcases folder.
>> >> >> > >> >> >> >
>> >> >> > >> >> >> > My Question : Is there any ready-made script available to extract the
>> >> >> > >> >> >> > description of user required test case from above specified folder?
>> >> >> > >> >> >> >
>> >> >> > >> >> >> > If script is not available, could you suggest the direction to extract
>> >> >> > >> >> >> > description of test cases.
>> >> >> > >> >> >> >
>> >> >> > >> >> >> >
>> >> >> > >> >> >> > Regards,
>> >> >> > >> >> >> > Rohit.
>> >> >> > >> >> >>
>> >> >> > >> >> >> Not I am aware of. Subrata or someone in the list might have some ideas
>> >> >> > >> >> >> for you.
>> >> >> > >> >> >>
>> >> >> > >> >> >> CAI Qian
>> >> >> > >> >> >>
>> >> >> > >> >
>> >> >> > >> >
>> >> >> > >
>> >> >> > >
>> >> >>
>> >> >>
>> >> >> ------------------------------------------------------------------------------
>> >> >> Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT
>> >> >> is a gathering of tech-side developers & brand creativity professionals. Meet
>> >> >> the minds behind Google Creative Lab, Visual Complexity, Processing, &
>> >> >> iPhoneDevCamp as they present alongside digital heavyweights like Barbarian
>> >> >> Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com
>> >> >> _______________________________________________
>> >> >> Ltp-list mailing list
>> >> >> Ltp-list@lists.sourceforge.net
>> >> >> https://lists.sourceforge.net/lists/listinfo/ltp-list
>> >> >
>> >> >
>> >
>> >
>
>
[-- Attachment #2: ltpdoc_txt.txt --]
[-- Type: text/plain, Size: 301885 bytes --]
Signed-off-by: rohit verma (rohit.170309@gmail.com)
================================================================================
diff -ruN ltp-full-20090531_orig/doc/testcases/commands.txt ltp-full-20090531/doc/testcases/commands.txt
--- ltp-full-20090531_orig/doc/testcases/commands.txt 2003-07-19 03:00:11.000000000 +0530
+++ ltp-full-20090531/doc/testcases/commands.txt 2009-06-19 11:31:27.000000000 +0530
@@ -1,117 +1,170 @@
-ade
----
-ar01
-
- Construct one or more command lines which use options that do not
- take arguments
- For each of these invocations
- Specify the options seperately
- Group the options together
- Compare the behavior of the two cases
- If they behave differently, then fail
- If none of the cases fail, then pass
-
-ld01
-
- To test the basic functionality of the `ld` command.
-
-ldd01
-
- To test the basic functionality of the `ldd` command.
-
-nm01
-
- To test the basic functionality of the `nm` command.
-
-objdump01
-
- Tests the functionality of the `objdump` command.
-
-size01
-
- To test the basic functionality of `size`.
-
-
-
-cpio
-----
-cpio_test.sh
-
- Tests the basic functionality of `cpio` command
-
-
-
-cron
-----
-cron_test.sh
-
- This testcase tests if crontab <filename> installs the cronjob
- and cron schedules the job correctly.
-
-
-
-eject
------
-eject_tests.sh
-
- Tests the basic functionality of `eject` command.
-
-
-
-fileutils
----------
-cp_tests.sh
-
- Test basic functionality of `cp` command
-
-ln_tests.sh
-
- Test basic functionality of `ln` command
-
-mkdir_tests.sh
-
- Test basic functionality of `mkdir` command
-
-mv_test.sh
-
- Test basic functionality of `mv` command
-
-
-
-gzip
-----
-gzip_tests.sh
-
- Test basic functionality of `gzip` and `gunzip` command
-
-
-
-logrotate
----------
-logrotate_tests.sh
-
- Test basic functionality of `logrotate` command.
-
-
-
-mail
-----
-mail_tests.sh
-
- Test basic functionality of `mail` command.
-
-
-
-tar
----
-tar_tests.sh
-
- Test basic functionality of `tar` command.
-
-
-unzip
------
-unzip_tests.sh
-
- Test basic functionality of `unzip` command.
-
+<testname=ar01>
+ <description>
+ Construct one or more command lines which use options that do not
+ take arguments
+ For each of these invocations
+ Specify the options seperately
+ Group the options together
+ Compare the behavior of the two cases
+ If they behave differently, then fail
+ If none of the cases fail, then pass
+
+ <\description>
+ <test_location>
+ ltp/testcases/commands/ade/ar/ar01
+ <\test_location>
+<\testname>
+<testname=ld01>
+ <description>
+ To test the basic functionality of the `ld` command.
+
+ <\description>
+ <test_location>
+ ltp/testcases/commands/ade/ld/ld01
+ <\test_location>
+<\testname>
+<testname=ldd01>
+ <description>
+ To test the basic functionality of the `ldd` command.
+
+ <\description>
+ <test_location>
+ ltp/testcases/commands/ade/ldd/ldd01
+ <\test_location>
+<\testname>
+<testname=nm01>
+ <description>
+ To test the basic functionality of the `nm` command.
+
+ <\description>
+ <test_location>
+ ltp/testcases/commands/ade/nm/nm01
+ <\test_location>
+<\testname>
+<testname=objdump01>
+ <description>
+ Tests the functionality of the `objdump` command.
+
+ <\description>
+ <test_location>
+ ltp/testcases/commands/ade/objdump/objdump01
+ <\test_location>
+<\testname>
+<testname=size01>
+ <description>
+ To test the basic functionality of `size`.
+
+ <\description>
+ <test_location>
+ ltp/testcases/commands/ade/size/size01
+ <\test_location>
+<\testname>
+<testname=cpio_test.sh>
+ <description>
+ Tests the basic functionality of `cpio` command
+
+ <\description>
+ <test_location>
+ ltp/testcases/commands/cpio/cpio_tests.sh
+ <\test_location>
+<\testname>
+<testname=cron_test.sh>
+ <description>
+ This testcase tests if crontab <filename> installs the cronjob
+ and cron schedules the job correctly.
+
+ <\description>
+ <test_location>
+ ltp/testcases/commands/cron/cron_tests.sh
+ <\test_location>
+<\testname>
+<testname=eject_tests.sh>
+ <description>
+ Tests the basic functionality of `eject` command.
+
+ <\description>
+ <test_location>
+ ltp/testcases/commands/eject/eject-tests.sh
+ <\test_location>
+<\testname>
+<testname=cp_tests.sh>
+ <description>
+ Test basic functionality of `cp` command
+
+ <\description>
+ <test_location>
+ ltp/testcases/commands/fileutils/cp/cp_tests.sh
+ <\test_location>
+<\testname>
+<testname=ln_tests.sh>
+ <description>
+ Test basic functionality of `ln` command
+
+ <\description>
+ <test_location>
+ ltp/testcases/commands/fileutils/ln/ln_tests.sh
+ <\test_location>
+<\testname>
+<testname=mkdir_tests.sh>
+ <description>
+ Test basic functionality of `mkdir` command
+
+ <\description>
+ <test_location>
+ ltp/testcases/commands/fileutils/mkdir/mkdir_tests.sh
+ <\test_location>
+<\testname>
+<testname=mv_test.sh>
+ <description>
+ Test basic functionality of `mv` command
+
+ <\description>
+ <test_location>
+ ltp/testcases/commands/fileutils/mv/mv_tests.sh
+ <\test_location>
+<\testname>
+<testname=gzip_tests.sh>
+ <description>
+ Test basic functionality of `gzip` and `gunzip` command
+
+ <\description>
+ <test_location>
+ ltp/testcases/commands/gzip/gzip_tests.sh
+ <\test_location>
+<\testname>
+<testname=logrotate_tests.sh>
+ <description>
+ Test basic functionality of `logrotate` command.
+
+ <\description>
+ <test_location>
+ ltp/testcases/commands/logrotate/logrotate_tests.sh
+ <\test_location>
+<\testname>
+<testname=mail_tests.sh>
+ <description>
+ Test basic functionality of `mail` command.
+
+ <\description>
+ <test_location>
+ ltp/testcases/commands/mail/mail_tests.sh
+ <\test_location>
+<\testname>
+<testname=tar_tests.sh>
+ <description>
+ Test basic functionality of `tar` command.
+
+ <\description>
+ <test_location>
+ ltp/testcases/commands/tar/tar_tests.sh
+ <\test_location>
+<\testname>
+<testname=unzip>
+ <description>
+ Test basic functionality of `unzip` command.
+
+ <\description>
+ <test_location>
+ ltp/testcases/commands/unzip
+ <\test_location>
+<\testname>
diff -ruN ltp-full-20090531_orig/doc/testcases/kernel.txt ltp-full-20090531/doc/testcases/kernel.txt
--- ltp-full-20090531_orig/doc/testcases/kernel.txt 2009-05-27 19:06:34.000000000 +0530
+++ ltp-full-20090531/doc/testcases/kernel.txt 2009-06-19 11:31:28.000000000 +0530
@@ -1,3679 +1,7058 @@
-device-drivers
---------------
-ltpacpi.sh
-
- ACPI (Advanced Control Power & Integration) testscript for 2.5 kernels.
-
-
-fs
---
-doio
-
- growfiles
-
+<testname=ltpacpi.sh>
+ <description>
+ ACPI (Advanced Control Power & Integration) testscript for 2.5 kernels.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/device-drivers/acpi/ltpacpi.sh
+ <\test_location>
+<\testname>
+<testname=growfiles>
+ <description>
This program will grow a list of files.
Each file will grow by grow_incr before the same
- file grows twice. Each file is open and closed before next file is opened.
-
- rwtest
+ file grows twice. Each file is open and closed before next file is opened.
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/fs/doio/growfiles.c
+ <\test_location>
+<\testname>
+<testname=rwtest>
+ <description>
A wrapper for doio and iogen.
- doio - a general purpose io initiator with system call and
- write logging. See doio.h for the structure which defines
- what doio requests should look like.
-
- Currently doio can handle read,write,reada,writea,ssread,
- sswrite, and many varieties of listio requests.
- For disk io, if the O_SSD flag is set doio will allocate
- the appropriate amount of ssd and do the transfer - thus, doio
- can handle all of the primitive types of file io.
-
- iogen - a tool for generating file/sds io for a doio process
-
-fs_di
- A FileSystem Data Integrity test.
-
-fs_inod
-
- Rapidly creates and deletes files through
- multiple processes running in the background.
- The user may specify the number of subdirectories
- to create, the number of files to create (per
- subdirectory), and the number of times to repeat
- the creation/deletion cycle.
-
-fs_maim
-
- Collection of smaller scripts to stress storage management
- utilities.
-
-fs_perms
-
- Regression test for Linux filesystem permissions.
-
-fsstress
-
- A highly configurable stress test utility that calls most of the main
- file system syscalls. Originally developed by SGI for XFS testing.
-
-fsx-linux
-
- Filesystem stress test developed by Apple Computer, Inc.
-
-ftest
-
- A collection of file system tests developed by Sequent/IBM.
-
-inode
-
- Inode-based stress tests.
-
-lftest
- The purpose of this test is to verify the file size limitations of a filesystem.
- It writes one buffer at a time and lseeks from the beginning of the file to the
- end of the last write position. The intent is to test lseek64.
-
-linktest
-
- Regression test for max links per file
-
-openfile
-
- Creates files and opens simultaneously
-
-proc
-
- Recursively reads all files within /proc filesystem.
-
-stream
-
- Collection of tests for testing stream functions.
-
-
-
-io
---
-aio
-
- Collection of asynchronous i/o tests.
-
-
-direct_io
-
- Collection of direct i/o tests.
-
-disktest
-
- Does repeated accesses to a filespec and optionally writes to, reads from,
- and verifies the data. By default, disktest makes assumptions about
- the running environment which allows for a quick start of IO generation.
- However, Disktest has a large number of command line options which can
- be used to adapt the test for a variety of uses including data integrity,
- medium integraty, performance, and simple application simulation.
-
-
-stress_cd
-
- Creates multiple read threads on the cdrom device.
-
-stress_floppy
-
- Tests the reading/writing/formatting on a floppy drive.
-
-
-
-ipc
----
-ipc_stress
-
- A collection of tests designed to stress IPC.
-
-pipeio
-
- This tool can be used to beat on system or named pipes.
- See the help() function below for user information.
-
-semaphore
-
- sem01
-
- Creates a semaphore and two processes. The processes
- each go through a loop where they semdown, delay for a
- random amount of time, and semup, so they will almost
- always be fighting for control of the semaphore.
-
- sem02
+ <\description>
+ <test_location>
+ <\test_location>
+<\testname>
+<testname=doio>
+ <description>
+ a general purpose io initiator with system call and
+ write logging. See doio.h for the structure which defines
+ what doio requests should look like.
+
+ Currently doio can handle read,write,reada,writea,ssread,
+ sswrite, and many varieties of listio requests.
+ For disk io, if the O_SSD flag is set doio will allocate
+ the appropriate amount of ssd and do the transfer
+
+ thus, doio
+ can handle all of the primitive types of file io.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/fs/doio/doio.c
+ <\test_location>
+<\testname>
+<testname=iogen>
+ <description>
+ a tool for generating file/sds io for a doio process
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/fs/doio/iogen.c
+ <\test_location>
+<\testname>
+<testname=fs_di>
+ <description>
+ A FileSystem Data Integrity test.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/fs/fs_di
+ <\test_location>
+<\testname>
+<testname=fs_inod>
+ <description>
+ Rapidly creates and deletes files through
+ multiple processes running in the background.
+ The user may specify the number of subdirectories
+ to create, the number of files to create (per
+ subdirectory), and the number of times to repeat
+ the creation/deletion cycle.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/fs/fs_inod
+ <\test_location>
+<\testname>
+<testname=fs_maim>
+ <description>
+ Collection of smaller scripts to stress storage management
+ utilities.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/fs/fs_maim
+ <\test_location>
+<\testname>
+<testname=fs_perms>
+ <description>
+ Regression test for Linux filesystem permissions.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/fs/fs_perms/fs_perms.c
+ <\test_location>
+<\testname>
+<testname=fsstress>
+ <description>
+ A highly configurable stress test utility that calls most of the main
+ file system syscalls. Originally developed by SGI for XFS testing.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/fs/fsstress/fsstress.c
+ <\test_location>
+<\testname>
+<testname=fsx-linux>
+ <description>
+ Filesystem stress test developed by Apple Computer, Inc.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/fs/fsx-linux/fsx-linux.c
+ <\test_location>
+<\testname>
+<testname=ftest>
+ <description>
+ A collection of file system tests developed by Sequent/IBM.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/fs/ftest
+ <\test_location>
+<\testname>
+<testname=inode>
+ <description>
+ Inode-based stress tests.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/fs/inode
+ <\test_location>
+<\testname>
+<testname=lftest>
+ <description>
+ The purpose of this test is to verify the file size limitations of a filesystem.
+ It writes one buffer at a time and lseeks from the beginning of the file to the
+ end of the last write position. The intent is to test lseek64.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/fs/lftest/lftest.c
+ <\test_location>
+<\testname>
+<testname=linktest>
+ <description>
+ Regression test for max links per file
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/fs/linktest
+ <\test_location>
+<\testname>
+<testname=openfile>
+ <description>
+ Creates files and opens simultaneously
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/fs/openfile/openfile.c
+ <\test_location>
+<\testname>
+<testname=proc>
+ <description>
+ Recursively reads all files within /proc filesystem.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/fs/proc
+ <\test_location>
+<\testname>
+<testname=stream>
+ <description>
+ Collection of tests for testing stream functions.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/fs/stream
+ <\test_location>
+<\testname>
+<testname=aio>
+ <description>
+ Collection of asynchronous i/o tests.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/io/aio
+ <\test_location>
+<\testname>
+<testname=direct_io>
+ <description>
+ Collection of direct i/o tests.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/io/direct_io
+ <\test_location>
+<\testname>
+<testname=disktest>
+ <description>
+ Does repeated accesses to a filespec and optionally writes to, reads from,
+ and verifies the data. By default, disktest makes assumptions about
+ the running environment which allows for a quick start of IO generation.
+ However, Disktest has a large number of command line options which can
+ be used to adapt the test for a variety of uses including data integrity,
+ medium integraty, performance, and simple application simulation.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/io/disktest
+ <\test_location>
+<\testname>
+<testname=stress_cd>
+ <description>
+ Creates multiple read threads on the cdrom device.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/io/stress_cd/stress_cd.c
+ <\test_location>
+<\testname>
+<testname=stress_floppy>
+ <description>
+ Tests the reading/writing/formatting on a floppy drive.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/io/stress_floppy
+ <\test_location>
+<\testname>
+<testname=ipc_stress>
+ <description>
+ A collection of tests designed to stress IPC.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/ipc/ipc_stress
+ <\test_location>
+<\testname>
+<testname=pipeio>
+ <description>
+ This tool can be used to beat on system or named pipes.
+ See the help() function below for user information.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/ipc/pipeio/pipeio.c
+ <\test_location>
+<\testname>
+<testname=sem01>
+ <description>
+ Creates a semaphore and two processes. The processes
+ each go through a loop where they semdown, delay for a
+ random amount of time, and semup, so they will almost
+ always be fighting for control of the semaphore.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/ipc/semaphore/sem01.c
+ <\test_location>
+<\testname>
+<testname=sem02>
+ <description>
The application creates several threads using pthread_create().
One thread performs a semop() with the SEM_UNDO flag set. The
change in sempaphore value performed by that semop should be
"undone" only when the last pthread exits.
-
-
-mem
----
-libmm
-
- Tests the libmm core API.
-
-mem
-
- mem01
-
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/ipc/semaphore/sem02.c
+ <\test_location>
+<\testname>
+<testname=libmm>
+ <description>
+ Tests the libmm core API.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/mem/libmm
+ <\test_location>
+<\testname>
+<testname=mem01>
+ <description>
Test for exercising virtual memory allocation
- and usage. It is intended to provide a limited exposure of the
- system swapper, for now.
-
- mem02
+ and usage. It is intended to provide a limited exposure of the
+ system swapper, for now.
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/mem/mem/mem01.c
+ <\test_location>
+<\testname>
+<testname=mem02>
+ <description>
Checks that memory can be allocated and freed.
-mmapstress
-
- A group of tests for testing mmap().
-
-mtest01
-
- mallocs memory <chunksize> at a time until malloc fails.
-
-mtest05
-
- mmstress
-
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/mem/mem/mem02.c
+ <\test_location>
+<\testname>
+<testname=mmapstress>
+ <description>
+ A group of tests for testing mmap().
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/mem/mmapstress
+ <\test_location>
+<\testname>
+<testname=mtest01>
+ <description>
+ mallocs memory <chunksize> at a time until malloc fails.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/mem/mtest01/mtest01.c
+ <\test_location>
+<\testname>
+<testname=mmstress>
+ <description>
Performs General Stress with Race conditions
-mtest06
-
- mmap1
-
- Test the LINUX memory manager. The program is aimed at
- stressing the memory manager by simultanious map/unmap/read
- by light weight processes, the test is scheduled to run for
- a mininum of 24 hours.
-
- mmap2
-
- Test the LINUX memory manager. The program is aimed at
- stressing the memory manager by repeaded map/write/unmap of a
- of a large gb size file.
-
- mmap3
-
- Test the LINUX memory manager. The program is aimed at
- stressing the memory manager by repeaded map/write/unmap
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/mem/mtest05/mmstress.c
+ <\test_location>
+<\testname>
+<testname=mmap1>
+ <description>
+ Test the LINUX memory manager. The program is aimed at
+ stressing the memory manager by simultanious map/unmap/read
+ by light weight processes, the test is scheduled to run for
+ a mininum of 24 hours.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/mem/mtest06/mmap1.c
+ <\test_location>
+<\testname>
+<testname=mmap2>
+ <description>
+ Test the LINUX memory manager. The program is aimed at
+ stressing the memory manager by repeaded map/write/unmap of a
+ of a large gb size file.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/mem/mtest06/mmap2.c
+ <\test_location>
+<\testname>
+<testname=mmap3>
+ <description>
+ Test the LINUX memory manager. The program is aimed at
+ stressing the memory manager by repeaded map/write/unmap
of file/memory of random size (maximum 1GB) this is done by
- multiple processes.
-
- shmat1
-
- Test the LINUX memory manager. The program is aimed at
- stressing the memory manager by repeaded shmat/write/read/
- shmatd of file/memory of random size (maximum 1000 * 4096)
- done by multiple processes.
-
-mtest07
-
- mallocstress
+ multiple processes.
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/mem/mtest06/mmap3.c
+ <\test_location>
+<\testname>
+<testname=shmat1>
+ <description>
+ Test the LINUX memory manager. The program is aimed at
+ stressing the memory manager by repeaded shmat/write/read/
+ shmatd of file/memory of random size (maximum 1000 * 4096)
+ done by multiple processes.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/mem/mtest06/shmat1.c
+ <\test_location>
+<\testname>
+<testname=mallocstress>
+ <description>
Stresses the VMM and C library by spawning N threads which
malloc blocks of increasing size until malloc returns NULL.
- shm_test
-
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/mem/mtest07/mallocstress.c
+ <\test_location>
+<\testname>
+<testname=shm_test>
+ <description>
Stresses memory management subsystem of Linux. Spawns multiple
pairs of reader & writer threads. One thread will create the
- shared segment of random size and write to this memory, the
+ shared segment of random size and write to this memory, the
other pair will read from this memory.
-page
-
- Tests the behavior of memory paging.
-
-shmt
-
- A collection of shared memory tests.
-
-vmtests
-
- Data and stack space VM tests.
-
-
-
-module
-------
-create_module
-
- Tests the basic functionality of create_module().
-
-delete_module
-
- Tests the basic functionality of delete_module().
-
-query_module
-
- Tests the basic functionality of query_module().
-
-
-
-pty
----
-hangup01
-
- Writes three messages to a slave pty, with a hangup after each.
- Verifies all thre messages are received.
-
-ptem01
-
- - Tests termio/termios ioctls
- - Tests window size setting and getting
- - Tests sending a break
- - Tests multiple opens of slave side
- - Tests several simultaneous opens
-
-pty01
-
- - Tests slave locking
- - Tests slave operations with closed master
- - Tests operations on master with closed slave
- - Tests multiple opens on slave side of pty
- - Tests opening/closing of lots of ptys in parallel.
-
-
-
-sched
------
-clisrv
-
- Read contents of data file. Write each line to socket, then
- read line back from socket and write to standard output.
-
-hyperthreading
-
- ht_enabled
-
- Test for whether HT enabling is the default setting and
- the kernel option works as expected.
-
- ht_affinity
-
- Test for whether a set of system calls is provided to bind
- itself or another process to a subset of currently active
- processors and to get affinity information.
-
- ht_interrupt
- Test for SMP interrupt distribution among all logical CPU
- should not be interfered by HT patch.
-
-process_stress
-
- Stresses the process management kernel code.
-
-pthreads
-
- pth_str01
-
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/mem/mtest07/shm_test.c
+ <\test_location>
+<\testname>
+<testname=page>
+ <description>
+ Tests the behavior of memory paging.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/mem/page
+ <\test_location>
+<\testname>
+<testname=shmt>
+ <description>
+ A collection of shared memory tests.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/mem/shmt
+ <\test_location>
+<\testname>
+<testname=vmtests>
+ <description>
+ Data and stack space VM tests.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/mem/vmtests
+ <\test_location>
+<\testname>
+<testname=create_module>
+ <description>
+ Tests the basic functionality of create_module().
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/module/create_module
+ <\test_location>
+<\testname>
+<testname=delete_module>
+ <description>
+ Tests the basic functionality of delete_module().
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/module/delete_module
+ <\test_location>
+<\testname>
+<testname=query_module>
+ <description>
+ Tests the basic functionality of query_module().
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/module/query_module
+ <\test_location>
+<\testname>
+<testname=hangup01>
+ <description>
+ Writes three messages to a slave pty, with a hangup after each.
+ Verifies all thre messages are received.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/pty/hangup01.c
+ <\test_location>
+<\testname>
+<testname=ptem01>
+ <description>
+ - Tests termio/termios ioctls
+ - Tests window size setting and getting
+ - Tests sending a break
+ - Tests multiple opens of slave side
+ - Tests several simultaneous opens
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/pty/ptem01.c
+ <\test_location>
+<\testname>
+<testname=pty01>
+ <description>
+ - Tests slave locking
+ - Tests slave operations with closed master
+ - Tests operations on master with closed slave
+ - Tests multiple opens on slave side of pty
+ - Tests opening/closing of lots of ptys in parallel.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/pty/pty01.c
+ <\test_location>
+<\testname>
+<testname=clisrv>
+ <description>
+ Read contents of data file. Write each line to socket, then
+ read line back from socket and write to standard output.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/sched/clisrv
+ <\test_location>
+<\testname>
+<testname=ht_enabled>
+ <description>
+ Test for whether HT enabling is the default setting and
+ the kernel option works as expected.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/sched/hyperthreading/ht_enabled
+ <\test_location>
+<\testname>
+<testname=ht_affinity>
+ <description>
+ Test for whether a set of system calls is provided to bind
+ itself or another process to a subset of currently active
+ processors and to get affinity information.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/sched/hyperthreading/ht_affinity
+ <\test_location>
+<\testname>
+<testname=ht_interrupt>
+ <description>
+ Test for SMP interrupt distribution among all logical CPU
+ should not be interfered by HT patch.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/sched/hyperthreading/ht_interrupt
+ <\test_location>
+<\testname>
+<testname=process_stress>
+ <description>
+ Stresses the process management kernel code.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/sched/process_stress
+ <\test_location>
+<\testname>
+<testname=pth_str01>
+ <description>
Creates a tree of threads
- pth_str02
-
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/sched/pthreads/pth_str01.c
+ <\test_location>
+<\testname>
+<testname=pth_str02>
+ <description>
Creates n threads
- pth_str03
-
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/sched/pthreads/pth_str02.c
+ <\test_location>
+<\testname>
+<testname=pth_str03>
+ <description>
Creates a tree of threads does calculations, and
- returns result to parent
-
-sched_stress
-
- Stress the scheduler code of the kernel.
-
-tool
-
- time-schedule
+ returns result to parent
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/sched/pthreads/pth_str03.c
+ <\test_location>
+<\testname>
+<testname=sched_stress>
+ <description>
+ Stress the scheduler code of the kernel.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/sched/sched_stress
+ <\test_location>
+<\testname>
+<testname=time-schedule>
+ <description>
Tool to test how long a context switch takes.
- trace_sched
-
- This utility spawns N tasks, each task sets its priority by
- making a system call to the scheduler. The thread function
- reads the priority that tbe schedular sets for this task and
- also reads from /proc the processor this task last executed on
- the information that is gathered by the thread function may
- be in real-time. Its only an approximation.
-
-
-
-syscalls
---------
- abort01
-
- Basic test for abort(3).
-
-
- accept01
-
- Verify that accept() returns the proper errno for various failure cases
-
-
- access01
-
- Basic test for access(2) using F_OK, R_OK, W_OK, and X_OK arguments.
-
- access02
-
- Verify that access() succeeds to check the read/write/execute permissions
- on a file if the mode argument passed was R_OK/W_OK/X_OK.
-
- Also verify that, access() succeeds to test the accessibility of the file
- referred to by symbolic link if the pathname points to a symbolic link.
-
- access03
-
- EFAULT error testing for access(2).
-
- access04
-
- Verify that,
- 1. access() fails with -1 return value and sets errno to EACCES
- if the permission bits of the file mode do not permit the
- requested (Read/Write/Execute) access.
- 2. access() fails with -1 return value and sets errno to EINVAL
- if the specified access mode argument is invalid.
- 3. access() fails with -1 return value and sets errno to EFAULT
- if the pathname points outside allocate address space for the
- process.
- 4. access() fails with -1 return value and sets errno to ENOENT
- if the specified file doesn't exist (or pathname is NULL).
- 5. access() fails with -1 return value and sets errno to ENAMETOOLONG
- if the pathname size is > PATH_MAX characters.
-
- access05
-
- Verify that access() succeeds to check the existance of a file if
- search access is permitted on the pathname of the specified file.
-
-
- acct01
-
- Issues calls to acct() and tests the returned values against expected
- results
-
- acct02
-
- Issues calls to acct() and tests the returned values against expected
- results
-
-
- adjtimex01
-
- Basic test for adjtimex().
-
- adjtimex02
-
- Tests for error conditions.
-
-
- alarm01
-
- Basic test for alarm(2).
-
- alarm02
-
- Boundary Value Test for alarm(2).
-
- alarm03
-
- Alarm(2) cleared by a fork.
-
- alarm04
-
- Check that when an alarm request is made, the signal SIGALRM is received
- even after the process has done an exec().
-
- alarm05
-
- Check the functionality of the Alarm system call when the time input
- parameter is non zero.
-
- alarm06
-
- Check the functionality of the Alarm system call when the time input
- parameter is zero.
-
- alarm07
-
- Check the functionality of the alarm() when the time input
- parameter is non-zero and the process does a fork.
-
-
- asyncio02
-
- Write/close flushes data to the file.
-
-
- bind01
-
- Verify that bind() returns the proper errno for various failure cases
-
-
- brk01
-
- Test the basic functionality of brk().
-
-
- capget01
-
- Test the basic functionality of capget().
-
- capget02
-
- Test the error conditions of capget().
-
-
- capset01
-
- Test the basic functionality of capset().
-
- capset02
-
- Test the error conditions of capset().
-
-
- chdir01
-
- Check proper operation of chdir(): tests whether the
- system call can it change the current, working directory, and find a
- file there? Will it fail on a non-directory entry ?
-
- chdir02
-
- Basic test for chdir(2).
-
- chdir03
-
- Testcase for testing that chdir(2) sets EACCES errno
-
- chdir04
-
- Testcase to test whether chdir(2) sets errno correctly.
-
-
- chmod01
-
- Verify that, chmod(2) succeeds when used to change the mode permissions
- of a file.
-
- chmod02
-
- Basic test for chmod(2).
-
- chmod03
-
- Verify that, chmod(2) will succeed to change the mode of a file
- and set the sticky bit on it if invoked by non-root (uid != 0)
- process with the following constraints,
- - the process is the owner of the file.
- - the effective group ID or one of the supplementary group ID's of the
- process is equal to the group ID of the file.
-
- chmod04
-
- Verify that, chmod(2) will succeed to change the mode of a directory
- and set the sticky bit on it if invoked by non-root (uid != 0) process
- with the following constraints,
- - the process is the owner of the directory.
- - the effective group ID or one of the supplementary group ID's of the
- process is equal to the group ID of the directory.
-
- chmod05
-
- Verify that, chmod(2) will succeed to change the mode of a directory
- but fails to set the setgid bit on it if invoked by non-root (uid != 0)
- process with the following constraints,
- - the process is the owner of the directory.
- - the effective group ID or one of the supplementary group ID's of the
- process is not equal to the group ID of the directory.
-
- chmod06
-
- Verify that,
- 1) chmod(2) returns -1 and sets errno to EPERM if the effective user id
- of process does not match the owner of the file and the process is
- not super user.
- 2) chmod(2) returns -1 and sets errno to EACCES if search permission is
- denied on a component of the path prefix.
- 3) chmod(2) returns -1 and sets errno to EFAULT if pathname points
- outside user's accessible address space.
- 4) chmod(2) returns -1 and sets errno to ENAMETOOLONG if the pathname
- component is too long.
- 5) chmod(2) returns -1 and sets errno to ENOTDIR if the directory
- component in pathname is not a directory.
- 6) chmod(2) returns -1 and sets errno to ENOENT if the specified file
- does not exists.
-
- chmod07
-
- Verify that, chmod(2) will succeed to change the mode of a file/directory
- and sets the sticky bit on it if invoked by root (uid = 0) process with
- the following constraints,
- - the process is not the owner of the file/directory.
- - the effective group ID or one of the supplementary group ID's of the
- process is equal to the group ID of the file/directory.
-
-
- chown01
-
- Basic test for chown(2).
-
- chown02
-
- Verify that, when chown(2) invoked by super-user to change the owner and
- group of a file specified by path to any numeric owner(uid)/group(gid)
- values,
- - clears setuid and setgid bits set on an executable file.
- - preserves setgid bit set on a non-group-executable file.
-
- chown03
-
- Verify that, chown(2) succeeds to change the group of a file specified
- by path when called by non-root user with the following constraints,
- - euid of the process is equal to the owner of the file.
- - the intended gid is either egid, or one of the supplementary gids
- of the process.
- Also, verify that chown() clears the setuid/setgid bits set on the file.
-
- chown04
-
- Verify that,
- 1) chown(2) returns -1 and sets errno to EPERM if the effective user id
- of process does not match the owner of the file and the process is
- not super user.
- 2) chown(2) returns -1 and sets errno to EACCES if search permission is
- denied on a component of the path prefix.
- 3) chown(2) returns -1 and sets errno to EFAULT if pathname points
- outside user's accessible address space.
- 4) chown(2) returns -1 and sets errno to ENAMETOOLONG if the pathname
- component is too long.
- 5) chown(2) returns -1 and sets errno to ENOTDIR if the directory
- component in pathname is not a directory.
- 6) chown(2) returns -1 and sets errno to ENOENT if the specified file
- does not exists.
-
- chown05
-
- Verify that, chown(2) succeeds to change the owner and group of a file
- specified by path to any numeric owner(uid)/group(gid) values when invoked
- by super-user.
-
-
- chroot01
-
- Testcase to check the whether chroot sets errno to EPERM.
-
- chroot02
-
- Test functionality of chroot(2)
-
- chroot03
-
- Testcase to test whether chroot(2) sets errno correctly.
-
-
- clone01
-
- Basic test for clone(2)
-
- clone02
-
- Functionality tests for clone(2)
-
- clone03
-
- Test for clone(2)
-
- clone04
-
- Test for checking error conditions for clone(2)
-
- clone05
-
- Test for CLONE_VFORK flag
-
- clone06
-
- Test to verify inheritance of environment variables.
-
-
- close01
-
- Test that closing a regular file and a pipe works correctly
-
- close02
-
- Check that an invalid file descriptor returns EBADF
-
- close08
-
- Basic test for close(2).
-
-
- confstr01
-
- Basic test for confstr().
-
-
- connect01
-
- Verify that connect() returns the proper errno for various failure cases
-
-
- creat01
-
- Testcase to check the basic functionality of the creat(2) system call.
-
- creat03
-
- Testcase to check whether the sticky bit cleared.
-
- creat04
-
- Testcase to check creat(2) fails with EACCES
-
- creat05
-
- Testcase to check that creat(2) system call returns EMFILE.
-
- creat06
-
- Testcase to check creat(2) sets the following errnos correctly:
- 1. EISDIR
- 2. ENAMETOOLONG
- 3. ENOENT
- 4. ENOTDIR
- 5. EFAULT
- 6. EACCES
-
- creat07
-
- Testcase to check creat(2) sets the following errnos correctly:
- 1. ETXTBSY
-
- creat08
-
- Verifies that the group ID and setgid bit are set correctly when
- a new file is created.
-
- creat09
-
- Basic test for creat(2) using 0700 argument.
-
- dup01
-
- Basic test for dup(2).
-
- dup02
-
- Negative test for dup(2) with bad fd.
-
- dup03
-
- Negative test for dup(2) (too many fds).
-
- dup04
-
- Basic test for dup(2) of a system pipe descriptor.
-
- dup05
-
- Basic test for dup(2) of a named pipe descriptor.
-
- dup06
-
- Test if dup returns -1 on the 21st file when _NFILE is 20.
-
- dup07
-
- Test if the access mode is the same for both file descriptors.
-
-
- dup201
-
- Negative tests for dup2() with bad fd (EBADF), and for "too many
- open files" (EMFILE)
-
- dup202
-
- Is the access mode the same for both file descriptors?
- 0: read only ? "0444"
- 1: write only ? "0222"
- 2: read/write ? "0666"
-
- dup203
-
- Testcase to check the basic functionality of dup2().
-
- dup204
-
- Testcase to check the basic functionality of dup2(2).
-
- dup205
-
- Testcase to check if -1 is returned on the 21st file when _NFILE is 20.
-
-
- execl01
-
- Basic test for execl(2).
-
-
- execle01
-
- Basic test for execle(2).
-
-
- execlp01
-
- Basic test for execlp(2).
-
-
- execv01
-
- Basic test for execv(2).
-
-
- execve01
-
- Basic test for execve(2).
-
- execve02
-
- Testcase to check whether execve(2) sets errno to EACCES correctly
-
- execve03
-
- Testcase to check execve sets the following errnos correctly:
- 1. ENAMETOOLONG
- 2. ENOENT
- 3. ENOTDIR
- 4. EFAULT
- 5. EACCES
- 6. ENOEXEC
-
- execve04
-
- Testcase to check execve sets the following errnos correctly:
- 1. ETXTBSY
-
- execve05
-
- This testcase tests the basic functionality of the execve(2) system
- call.
-
-
- execvp01
-
- Basic test for execvp(2)
-
-
- exit01
-
- Check that exit returns the correct values to the waiting parent
-
- exit02
-
- Check that exit flushes output file buffers and closes files upon
- exitting
-
-
- fchdir01
-
- fchdir01 - create a directory and cd into it.
-
- fchdir02
-
- fchdir02 - try to cd into a bad directory (bad fd).
-
-
- fchmod01
-
- Basic test for Fchmod(2).
-
- fchmod02
-
- Verify that, fchmod(2) will succeed to change the mode of a file/directory
- set the sticky bit on it if invoked by root (uid = 0) process with
- the following constraints,
- - the process is not the owner of the file/directory.
- - the effective group ID or one of the supplementary group ID's of the
- process is equal to the group ID of the file/directory.
-
- fchmod03
-
- Verify that, fchmod(2) will succeed to change the mode of a file
- and set the sticky bit on it if invoked by non-root (uid != 0)
- process with the following constraints,
- - the process is the owner of the file.
- - the effective group ID or one of the supplementary group ID's of the
- process is equal to the group ID of the file.
-
- fchmod04
-
- Verify that, fchmod(2) will succeed to change the mode of a directory
- and set the sticky bit on it if invoked by non-root (uid != 0) process
- with the following constraints,
- - the process is the owner of the directory.
- - the effective group ID or one of the supplementary group ID's of the
- process is equal to the group ID of the directory.
-
- fchmod05
-
- Verify that, fchmod(2) will succeed to change the mode of a directory
- but fails to set the setgid bit on it if invoked by non-root (uid != 0)
- process with the following constraints,
- - the process is the owner of the directory.
- - the effective group ID or one of the supplementary group ID's of the
- process is not equal to the group ID of the directory.
-
- fchmod06
-
- Verify that,
- 1) fchmod(2) returns -1 and sets errno to EPERM if the effective user id
- of process does not match the owner of the file and the process is
- not super user.
- 2) fchmod(2) returns -1 and sets errno to EBADF if the file descriptor
- of the specified file is not valid.
-
- fchmod07
-
- Verify that, fchmod(2) succeeds when used to change the mode permissions
- of a file specified by file descriptor.
-
-
- fchown01
-
- Basic test for fchown(2).
-
- fchown02
-
- Verify that, when fchown(2) invoked by super-user to change the owner and
- group of a file specified by file descriptor to any numeric
- owner(uid)/group(gid) values,
- - clears setuid and setgid bits set on an executable file.
- - preserves setgid bit set on a non-group-executable file.
-
- fchown03
-
- Verify that, fchown(2) succeeds to change the group of a file specified
- by path when called by non-root user with the following constraints,
- - euid of the process is equal to the owner of the file.
- - the intended gid is either egid, or one of the supplementary gids
- of the process.
- Also, verify that fchown() clears the setuid/setgid bits set on the file.
-
- fchown04
-
- Verify that,
- 1) fchown(2) returns -1 and sets errno to EPERM if the effective user id
- of process does not match the owner of the file and the process is
- not super user.
- 2) fchown(2) returns -1 and sets errno to EBADF if the file descriptor
- of the specified file is not valid.
-
- fchown05
-
- Verify that, fchown(2) succeeds to change the owner and group of a file
- specified by file descriptor to any numeric owner(uid)/group(gid) values
- when invoked by super-user.
-
-
- fcntl01
-
- Test F_DUPFD, F_SETFL cmds of fcntl
-
- fcntl02
-
- Basic test for fcntl(2) using F_DUPFD argument.
-
- fcntl03
-
- Basic test for fcntl(2) using F_GETFD argument.
-
- fcntl04
-
- Basic test for fcntl(2) using F_GETFL argument.
-
- fcntl05
-
- Basic test for fcntl(2) using F_GETLK argument.
-
- fcntl06
-
- Error checking conditions for remote locking of regions of a file.
-
- fcntl07
-
- Close-On-Exec functional test.
-
- fcntl07B
-
- Close-On-Exec of named pipe functional test.
-
- fcntl08
-
- Basic test for fcntl(2) using F_SETFL argument.
-
- fcntl09
-
- Basic test for fcntl(2) using F_SETLK argument.
-
- fcntl10
-
- Basic test for fcntl(2) using F_SETLKW argument.
-
- fcntl11
-
- Testcase to check locking of regions of a file
-
- fcntl12
-
- Testcase to test that fcntl() sets EMFILE for F_DUPFD command.
-
- fcntl13
-
- Testcase to test that fcntl() sets errno correctly.
-
- fcntl14
-
- File locking test cases for fcntl. In Linux, S_ENFMT is not implemented
- in the kernel. However all standard Unix kernels define S_ENFMT as
- S_ISGID. So this test defines S_ENFMT as S_ISGID.
-
- fcntl15
-
- Check that file locks are removed when file closed
-
- fcntl16
-
- Additional file locking test cases for checking proper notifictaion
- of processes on lock change
-
- fcntl17
-
- Check deadlock detection for file locking
-
- fcntl18
-
- Test to check the error conditions in fcntl system call
-
- fcntl19
-
- Testcase to check locking of regions of a file
-
- fcntl20
-
- Check locking of regions of a file
-
- fcntl21
-
- Check locking of regions of a file
-
-
- fdatasync01
-
- Basic test for fdatasync(2).
-
- fdatasync02
-
- Checking error conditions for fdatasync(2).
-
-
- flock01
-
- Basic test for flock(2)
-
- flock02
-
- Error condition test for flock(2)
-
- flock03
-
- Error condition test for flock(2)
-
- flock04
-
- Testing different locks on flock(2)
-
- flock05
-
- Testing different locks on flock(2)
-
- flock06
-
- Error condition test for flock(2)
-
-
- fmtmsg01
-
- Basic test of fmtmsg().
-
-
- fork01
-
- Basic test for fork(2).
-
- fork02
-
- Test correct operation of fork:
- pid == 0 in child;
- pid > 0 in parent from wait;
-
- fork03
-
- Check that child can use a large text space and do a large
- number of operations.
-
- fork04
-
- Child inheritance of Environment Variables after fork().
-
- fork05
-
- Make sure LDT is propagated correctly
-
- fork06
-
- Test that a process can fork children a large number of
- times in succession
-
- fork07
-
- Check that all children inherit parent's file descriptor
-
- fork08
-
- Check if the parent's file descriptors are affected by
- actions in the child; they should not be.
-
- fork09
-
- Check that child has access to a full set of files.
-
- fork10
-
- Check inheritance of file descriptor by children, they
- should all be refering to the same file.
-
- fork11
-
- Test that parent gets a pid from each child when doing wait
-
- fork12
-
- Check that all children inherit parent's file descriptor
-
-
- fpathconf
-
- Basic test for fpathconf(2)
-
-
- fstat01
-
- Basic test for fstat(2)
-
- fstat02
-
- Verify that, fstat(2) succeeds to get the status of a file and fills
- the stat structure elements though file pointed to by file descriptor
- not opened for reading.
-
- fstat03
-
- Verify that, fstat(2) returns -1 and sets errno to EBADF if the file
- pointed to by file descriptor is not valid.
-
- fstat04
-
- Verify that, fstat(2) succeeds to get the status of a file pointed by
- file descriptor and fills the stat structure elements.
-
- fstat05
-
- Verify that, if buffer points outside user's accessible address space
- fstat(2) either returns -1 and sets errno to EFAULT or
- SIGSEGV is returned instead of EFAULT.
-
-
- fstatfs01
-
- Basic test for fstatfs(2)
-
- fstatfs02
-
- Testcase to check fstatfs() sets errno correctly.
-
-
- fsync01
-
- Basic test for fsync(2)
-
- fsync02
-
- Create a sparse file, fsync it, and time the fsync
-
- fsync03
-
- Testcase to check that fsync(2) sets errno correctly.
-
-
- ftruncate01
-
- Verify that, ftruncate(2) succeeds to truncate a file to a specified
- length if the file indicated by file descriptor opened for writing.
-
- ftruncate02
-
- Verify that, ftruncate(2) succeeds to truncate a file to a certain length,
- but the attempt to read past the truncated length will fail.
-
- ftruncate03
-
- Verify that,
- 1) ftruncate(2) returns -1 and sets errno to EINVAL if the specified
- truncate length is less than 0.
- 2) ftruncate(2) returns -1 and sets errno to EBADF if the file descriptor
- of the specified file is not valid.
-
- ftruncate04
-
- Test ftruncate/truncate and mandatory record locking.
-
-
- getcwd01
-
- Testcase to test that getcwd(2) sets errno correctly.
-
- getcwd02
-
- Testcase to check the basic functionality of the getcwd(2) system call.
-
- getcwd03
-
- Testcase to check the basic functionality of the getcwd(2) system call
- for symbolically linked directories.
-
-
- getdents01
-
- getdents01 - get a directory entry
-
- getdents02
-
- getdents02 - check that we get a failure with a bad file descriptor
-
- getdents03
-
- getdents03 - check for an EINVAL error
-
- getdents04
-
- getdents04 - check for an ENOTDIR error
-
- getdents05
-
- getdents05 - check that we get a failure with a bad dirp address.
-
-
- getdomainname01
-
- Basic test for getdomainname().
-
-
- getegid01
-
- Basic test for getegid(2)
-
-
- geteuid01
-
- Basic test for geteuid(2)
-
-
- getgid01
-
- Basic test for getgid(2)
-
- getgid02
-
- Testcase to check the basic functionality of getgid().
-
- getgid03
-
- Testcase to check the basic functionality of getegid().
-
-
- getgroups01
-
- Getgroups system call critical test
-
- getgroups02
-
- Basic test for getgroups(2)
-
- getgroups03
-
- Verify that, getgroups() system call gets the supplementary group IDs
- of the calling process.
-
- getgroups04
-
- Verify that,
- getgroups() fails with -1 and sets errno to EINVAL if the size
- argument value is -ve.
-
-
- gethostid01
-
- Basic test for gethostid(2)
-
-
- gethostname01
-
- Basic test for gethostname(2)
-
-
- getitimer01
-
- Check that a correct call to getitimer() succeeds
-
- getitimer02
-
- Check that a getitimer() call fails as expected
- with an incorrect second argument.
- getitimer03
-
- Check that a getitimer() call fails as expected
- with an incorrect first argument.
-
-
- getpeername01
-
- Verify that getpeername() returns the proper errno for various failure cases
-
-
- getpgid01
-
- Testcase to check the basic functionality of getpgid().
-
- getpgid02
-
- Testcase to check the basic functionality of getpgid().
-
-
- getpgrp01
-
- Basic test for getpgrp(2)
-
-
- getpid01
-
- Basic test for getpid(2)
-
-
- getpid02
-
- Verify that getpid() system call gets the process ID of the of the
- calling process.
-
-
- getppid01
-
- Testcase to check the basic functionality of the getppid() syscall.
-
-
- getpriority01
-
- Verify that getpriority() succeeds get the scheduling priority of
- the current process, process group or user.
-
-
- getpriority02
-
- Verify that,
- 1) getpriority() sets errno to ESRCH if no process was located
- was located for 'which' and 'who' arguments.
- 2) getpriority() sets errno to EINVAL if 'which' argument was
- not one of PRIO_PROCESS, PRIO_PGRP, or PRIO_USER.
-
-
- getresgid01
-
- Verify that getresgid() will be successful to get the real, effective
- and saved user id of the calling process.
-
- getresgid02
-
- Verify that getresgid() will be successful to get the real, effective
- and saved user ids after calling process invokes setregid() to change
- the effective/saved gids to that of specified user.
-
- getresgid03
-
- Verify that getresgid() will be successful to get the real, effective
- and saved user ids after calling process invokes setresgid() to change
- the effective gid to that of specified user.
-
-
- getresuid01
-
- Verify that getresuid() will be successful to get the real, effective
- and saved user id of the calling process.
-
- getresuid02
-
- Verify that getresuid() will be successful to get the real, effective
- and saved user ids after calling process invokes setreuid() to change
- the effective/saved uids to that of specified user.
-
- getresuid03
-
- Verify that getresuid() will be successful to get the real, effective
- and saved user ids after calling process invokes setresuid() to change
- the effective uid to that of specified user.
-
-
- getsid01
-
- getsid01 - call getsid() and make sure it succeeds
-
- getsid02
-
- getsid02 - call getsid() with an invalid PID to produce a failure
-
-
- getsockname01
-
- Verify that getsockname() returns the proper errno for various failure cases
-
-
- getsockopt01
-
- Verify that getsockopt() returns the proper errno for various failure cases
-
-
- gettimeofday01
-
- Testcase to check that gettimeofday(2) sets errno to EFAULT.
-
- gettimeofday02
-
- Testcase to check if gettimeofday is monotonous.
-
-
- getuid01
-
- Basic test for getuid(2)
-
- getuid02
-
- Testcase to check the basic functionality of the geteuid() system call.
-
- getuid03
-
- Testcase to check the basic functionality of the getuid() system call.
-
-
- ioctl01
-
- Testcase to check the errnos set by the ioctl(2) system call.
-
- ioctl02
-
- Testcase to test the TCGETA, and TCSETA ioctl implementations for
- the tty driver
-
-
- ioperm01
-
- Basic test for ioperm().
-
- ioperm02
-
- Test for error conditions.
-
-
- iopl01
-
- Basic test for iopl().
-
- iopl02
-
- Test for error conditions.
-
-
- ipc
-
- msgctl
-
- msgctl01 - create a message queue, then issue the IPC_STAT command
- and RMID commands to test the functionality
-
- msgctl02 - create a message queue, then issue the IPC_SET command
- to lower the msg_qbytes value.
-
- msgctl03 - create a message queue, then issue the IPC_RMID command
-
- msgctl04 - test for EACCES, EFAULT and EINVAL errors using
- a variety of incorrect calls.
-
- msgctl05 - test for EPERM error
-
- msgget
-
- msgget01 - create a message queue, write a message to it and
- read it back.
-
- msgget02 - test for EEXIST and ENOENT errors
-
- msgget03 - test for an ENOSPC error by using up all available
- message queues.
-
- msgget04 - test for an EACCES error by creating a message queue
- with no read or write permission and then attempting
- to access it with various permissions.
-
- msgrcv
-
- msgrcv01 - test that msgrcv() receives the expected message
-
- msgrcv02 - test for EACCES and EFAULT errors
-
- msgrcv03 - test for EINVAL error
-
- msgrcv04 - test for E2BIG and ENOMSG errors
-
- msgrcv05 - test for EINTR error
-
- msgrcv06 - test for EIDRM error
-
- msgsnd
-
- msgsnd01 - test that msgsnd() enqueues a message correctly
-
- msgsnd02 - test for EACCES and EFAULT errors
-
- msgsnd03 - test for EINVAL error
-
- msgsnd04 - test for EAGAIN error
-
- msgsnd05 - test for EINTR error
-
- msgsnd06 - test for EIDRM error
-
- semctl
-
- semctl01 - test the 10 possible semctl() commands
-
- semctl02 - test for EACCES error
-
- semctl03 - test for EINVAL and EFAULT errors
-
- semctl04 - test for EPERM error
-
- semctl05 - test for ERANGE error
-
- semget
-
- semget01 - test that semget() correclty creates a semaphore set
-
- semget02 - test for EACCES and EEXIST errors
-
- semget03 - test for ENOENT error
-
- semget05 - test for ENOSPC error
-
- semget06 - test for EINVAL error
-
- semop
-
- semop01 - test that semop() basic functionality is correct
-
- semop02 - test for E2BIG, EACCES, EFAULT and EINVAL errors
-
- semop03 - test for EFBIG error
-
- semop04 - test for EAGAIN error
-
- semop05 - test for EINTR and EIDRM errors
-
- shmat
-
- shmat01 - test that shmat() works correctly
-
- shmat02 - check for EINVAL and EACCES errors
-
- shmat03 - test for EACCES error
-
- shmctl
-
- shmctl01 - test the IPC_STAT, IPC_SET and IPC_RMID commands as
- they are used with shmctl()
-
- shmctl02 - check for EACCES, EFAULT and EINVAL errors
-
- shmctl03 - check for EACCES, and EPERM errors
-
- shmdt
-
- shmdt01 - check that shared memory is detached correctly
-
- shmdt02 - check for EINVAL error
-
- shmget
-
- shmget01 - test that shmget() correctly creates a shared memory segment
-
- shmget02 - check for ENOENT, EEXIST and EINVAL errors
-
- shmget03 - test for ENOSPC error
-
- shmget04 - test for EACCES error
-
- shmget05 - test for EACCES error
-
-
- kill01
-
- Test case to check the basic functionality of kill().
-
- kill02
-
- Sending a signal to processes with the same process group ID
-
- kill03
-
- Test case to check that kill fails when given an invalid signal.
-
- kill04
-
- Test case to check that kill() fails when passed a non-existant pid.
-
- kill05
-
- Test case to check that kill() fails when passed a pid owned by another
- user.
-
- kill06
-
- Test case to check the basic functionality of kill() when killing an
- entire process group with a negative pid.
-
- kill07
-
- Test case to check that SIGKILL can not be caught.
-
- kill08
-
- Test case to check the basic functionality of kill() when kill an
- entire process group.
-
- kill09
-
- Basic test for kill(2)
-
- kill10
-
- Signal flooding test.
-
- kill11
-
- Check that when a child is killed by its parent, it returns the
- correct values to the waiting parent--child has default values.
-
- kill12
-
- Check that when a child is killed by its parent, it returns the
- correct values to the waiting parent--the child sets signal to
- ignore the kill.
-
-
- lchown01
-
- Verify that, lchown(2) succeeds to change the owner and group of a file
- specified by path to any numeric owner(uid)/group(gid) values when invoked
- by super-user.
-
-
- lchown02
-
- Verify that,
- 1) lchown(2) returns -1 and sets errno to EPERM if the effective user id
- of process does not match the owner of the file and the process is
- not super user.
- 2) lchown(2) returns -1 and sets errno to EACCES if search permission is
- denied on a component of the path prefix.
- 3) lchown(2) returns -1 and sets errno to EFAULT if pathname points
- outside user's accessible address space.
- 4) lchown(2) returns -1 and sets errno to ENAMETOOLONG if the pathname
- component is too long.
- 5) lchown(2) returns -1 and sets errno to ENOTDIR if the directory
- component in pathname is not a directory.
- 6) lchown(2) returns -1 and sets errno to ENOENT if the specified file
- does not exists.
-
-
- link02
-
- Basic test for link(2)
-
- link03
-
- Multi links tests
-
- link04
-
- Negative test cases for link(2)
-
- link05
-
- Multi links (EMLINK) negative test
-
-
- listen01
-
- Verify that listen() returns the proper errno for various failure cases
-
-
- llseek01
-
- Verify that, llseek() call succeeds to set the file pointer position
- to an offset larger than file size. Also, verify that any attempt
- to write to this location fails.
-
- llseek02
-
- Verify that,
- 1. llseek() returns -1 and sets errno to EINVAL, if the 'Whence' argument
- is not a proper value.
- 2. llseek() returns -1 and sets errno to EBADF, if the file handle of
- the specified file is not valid.
-
-
- lseek01
-
- Basic test for lseek(2)
-
- lseek02
-
- Negative test for lseek(2)
-
- lseek03
-
- Negative test for lseek(2) whence
-
- lseek04
-
- Negative test for lseek(2) of a fifo
-
- lseek05
-
- Negative test for lseek(2) of a pipe
-
- lseek06
-
- Verify that, lseek() call succeeds to set the file pointer position
- to less than or equal to the file size, when a file is opened for
- read or write.
-
- lseek07
-
- Verify that, lseek() call succeeds to set the file pointer position
- to more than the file size, when a file is opened for reading/writing.
-
- lseek08
-
- Verify that, lseek() call succeeds to set the file pointer position
- to the end of the file when 'whence' value set to SEEK_END and any
- attempts to read from that position should fail.
-
- lseek09
-
- Verify that, lseek() call succeeds to set the file pointer position
- to the current specified location, when 'whence' value is set to
- SEEK_CUR and the data read from the specified location should match
- the expected data.
-
- lseek10
-
- Verify that,
- 1. lseek() returns -1 and sets errno to ESPIPE, if the file handle of
- the specified file is associated with a pipe, socket, or FIFO.
- 2. lseek() returns -1 and sets errno to EINVAL, if the 'Whence' argument
- is not a proper value.
- 3. lseek() returns -1 and sets errno to EBADF, if the file handle of
- the specified file is not valid.
-
-
- lstat01
-
- Verify that, lstat(2) succeeds to get the status of a file pointed to by
- symlink and fills the stat structure elements.
-
- lstat02
-
- Basic test for lstat(2)
-
- lstat03
-
- Verify that,
- 1) lstat(2) returns -1 and sets errno to EACCES if search permission is
- denied on a component of the path prefix.
- 2) lstat(2) returns -1 and sets errno to ENOENT if the specified file
- does not exists or empty string.
- 3) lstat(2) returns -1 and sets errno to EFAULT if pathname points
- outside user's accessible address space.
- 4) lstat(2) returns -1 and sets errno to ENAMETOOLONG if the pathname
- component is too long.
- 5) lstat(2) returns -1 and sets errno to ENOTDIR if the directory
- component in pathname is not a directory.
-
-
- mallopt
-
- Test basic functionality of mallopt().
-
-
- memcmp
-
- Test basic functionality of memcmp().
-
-
- memcpy
-
- Test basic functionality of memcpy().
-
-
- memset
-
- Test basic functionality of memset().
-
-
- mkdir01
-
- Basic errno test for mkdir(2)
-
- mkdir02
-
- This test will verify that new directory created
- by mkdir(2) inherites the group ID from the parent
- directory and S_ISGID bit, if the S_ISGID bit is set
- in the parent directory.
-
- mkdir03
-
- Check mkdir() with various error conditions that should produce
- EFAULT, ENAMETOOLONG, EEXIST, ENOENT and ENOTDIR
-
- mkdir04
-
- Attempt to create a directory in a directory having no permissions.
-
- mkdir05
-
- This test will verify the mkdir(2) syscall basic functionality
-
- mkdir08
-
- Basic test for mkdir(2)
-
-
- mknod01
-
- Basic test for mknod(2)
-
- mknod02
-
- Verify that mknod(2) succeeds when used to create a filesystem
- node with set group-ID bit set on a directory without set group-ID bit set.
- The node created should have set group-ID bit set and its gid should be
- equal to that of its parent directory.
-
- mknod03
-
- Verify that mknod(2) succeeds when used to create a filesystem
- node with set group-ID bit set on a directory with set group-ID bit set.
- The node created should have set group-ID bit set and its gid should be
- equal to the effective gid of the process.
-
- mknod04
-
- Verify that mknod(2) succeeds when used to create a filesystem
- node on a directory with set group-ID bit set.
- The node created should not have group-ID bit set and its gid should be
- equal to the effective gid of the process.
-
- mknod05
-
- Verify that mknod(2) succeeds when used by root to create a filesystem
- node with set group-ID bit set on a directory with set group-ID bit set.
- The node created should have set group-ID bit set and its gid should be
- equal to that of its parent directory.
-
- mknod06
-
- Verify that,
- 1) mknod(2) returns -1 and sets errno to EEXIST if specified path
- already exists.
- 2) mknod(2) returns -1 and sets errno to EFAULT if pathname points
- outside user's accessible address space.
- 3) mknod(2) returns -1 and sets errno to ENOENT if the directory
- component in pathname does not exist.
- 4) mknod(2) returns -1 and sets errno to ENAMETOOLONG if the pathname
- component was too long.
- 5) mknod(2) returns -1 and sets errno to ENOTDIR if the directory
- component in pathname is not a directory.
-
- mknod07
-
- Verify that,
- 1) mknod(2) returns -1 and sets errno to EPERM if the process id of
- the caller is not super-user.
- 2) mknod(2) returns -1 and sets errno to EACCES if parent directory
- does not allow write permission to the process.
-
- mknod08
-
- Verify that mknod(2) succeeds when used to create a filesystem
- node on a directory without set group-ID bit set. The node created
- should not have set group-ID bit set and its gid should be equal to that
- of its parent directory.
-
-
- mlock01
-
- Test basic functionality of mlock().
-
- mlock02
-
- Test to see the proper errors are returned by mlock().
-
-
- mlockall01
-
- Test basic functionality of mlockall().
-
- mlockall02
-
- Test to see the proper errors are returned by mlockall().
-
-
- mmap001
-
- Tests mmapping a big file and writing it once
-
- mmap01
-
- Verify that, mmap() succeeds when used to map a file where size of the
- file is not a multiple of the page size, the memory area beyond the end
- of the file to the end of the page is accessible. Also, verify that
- this area is all zeroed and the modifications done to this area are
- not written to the file.
-
- mmap02
-
- Call mmap() with prot parameter set to PROT_READ and with the file
- descriptor being open for read, to map a file creating mapped memory
- with read access. The minimum file permissions should be 0444.
-
- mmap03
-
- Call mmap() to map a file creating a mapped region with execute access
- under the following conditions -
- - The prot parameter is set to PROT_EXE
- - The file descriptor is open for read
- - The file being mapped has execute permission bit set.
- - The minimum file permissions should be 0555.
-
- The call should succeed to map the file creating mapped memory with the
- required attributes.
-
- mmap04
-
- Call mmap() to map a file creating a mapped region with read/exec access
- under the following conditions -
- - The prot parameter is set to PROT_READ|PROT_EXEC
- - The file descriptor is open for read
- - The file being mapped has read and execute permission bit set.
- - The minimum file permissions should be 0555.
-
- The call should succeed to map the file creating mapped memory with the
- required attributes.
-
-
- mmap05
-
- Call mmap() to map a file creating mapped memory with no access under
- the following conditions -
- - The prot parameter is set to PROT_NONE
- - The file descriptor is open for read(any mode other than write)
- - The minimum file permissions should be 0444.
-
- The call should succeed to map the file creating mapped memory with the
- required attributes.
-
- mmap06
-
- Call mmap() to map a file creating a mapped region with read access
- under the following conditions -
- - The prot parameter is set to PROT_READ
- - The file descriptor is open for writing.
-
- The call should fail to map the file.
-
-
- mmap07
-
- Call mmap() to map a file creating a mapped region with read access
- under the following conditions -
- - The prot parameter is set to PROT_WRITE
- - The file descriptor is open for writing.
- - The flags parameter has MAP_PRIVATE set.
-
- The call should fail to map the file.
-
- mmap08
-
- Verify that mmap() fails to map a file creating a mapped region
- when the file specified by file descriptor is not valid.
-
- mmap09
-
- Verify that truncating a mmaped file works correctly.
-
-
- modify_ldt01
-
- Testcase to check the error conditions for modify_ldt(2)
-
- modify_ldt02
-
- Testcase to check the error conditions for modify_ldt(2)
-
-
- mount01
-
- Basic test for mount(2)
-
- mount02
-
- Test for checking basic error conditions for mount(2)
-
- mount03
-
- Test for checking mount(2) flags
-
- mount04
-
- Test for checking EPERM
-
-
- mprotect01
-
- Testcase to check the error conditions for mprotect(2)
-
- mprotect02
-
- Testcase to check the mprotect(2) system call.
-
- mprotect03
-
- Testcase to check the mprotect(2) system call.
-
-
- mremap01
-
- Verify that, mremap() succeeds when used to expand the existing
- virtual memory mapped region to the requested size where the
- virtual memory area was previously mapped to a file using mmap().
-
- mremap02
-
- Verify that,
- mremap() fails when used to expand the existing virtual memory mapped
- region to the requested size, if the virtual memory area previously
- mapped was not page aligned or invalid argument specified.
-
- mremap03
-
- Verify that,
- mremap() fails when used to expand the existing virtual memory mapped
- region to the requested size, if there already exists mappings that
- cover the whole address space requsted or the old address specified was
- not mapped.
-
- mremap04
-
- Verify that,
- mremap() fails when used to expand the existing virtual memory mapped
- region to the requested size, if the memory area cannot be expanded at
- the current virtual address and MREMAP_MAYMOVE flag not set.
-
-
- msync01
-
- Verify that, msync() succeeds, when the region to synchronize, is part
- of, or all of a mapped region.
-
- msync02
-
- Verify that msync() succeeds when the region to synchronize is mapped
- shared and the flags argument is MS_INVALIDATE.
-
- msync03
-
- Verify that, msync() fails, when the region to synchronize, is outside
- the address space of the process.
-
- msync04
-
- Verify that, msync() fails, when the region to synchronize, is mapped
- but the flags argument is invalid.
-
- msync05
-
- Verify that, msync() fails, when the region to synchronize, was not
- mapped.
-
-
- munmap01
-
- Verify that, munmap call will succeed to unmap a mapped file or
- anonymous shared memory region from the calling process's address space
- and after successful completion of munmap, the unmapped region is no
- longer accessible.
-
- munmap02
-
- Verify that, munmap call will succeed to unmap a mapped file or
- anonymous shared memory region from the calling process's address space
- if the region specified by the address and the length is part or all of
- the mapped region.
-
- munmap03
-
- Verify that, munmap call will fail to unmap a mapped file or anonymous
- shared memory region from the calling process's address space if the
- address and the length of the region to be unmapped points outside the
- calling process's address space
-
-
- nanosleep01
-
- Verify that nanosleep() will be successful to suspend the execution
- of a process for a specified time.
-
- nanosleep02
-
- Verify that nanosleep() will be successful to suspend the execution
- of a process, returns after the receipt of a signal and writes the
- remaining sleep time into the structure.
-
- nanosleep03
-
- Verify that nanosleep() will fail to suspend the execution
- of a process for a specified time if interrupted by a non-blocked signal.
-
- nanosleep04
-
- Verify that nanosleep() will fail to suspend the execution
- of a process if the specified pause time is invalid.
-
-
- nftw
-
- Basic test of nftw().
-
- nftw64
-
- Basic test of nftw64()
-
-
- nice01
-
- Verify that root can provide a negative value to nice()
- and hence root can decrease the nice value of the process
- using nice() system call
-
- nice02
-
- Verify that any user can successfully increase the nice value of
- the process by passing a higher increment value (> max. applicable limits)
- to nice() system call.
-
- nice03
-
- Verify that any user can successfully increase the nice value of
- the process by passing an increment value (< max. applicable limits) to
- nice() system call.
-
- nice04
-
- Verify that, nice(2) fails when, a non-root user attempts to increase
- the priority of a process by specifying a negative increment value.
-
- nice05
-
- Basic test for nice(2)
-
-
- open01
-
- Open a file with oflag = O_CREAT set, does it set the sticky bit off?
-
- Open "/tmp" with O_DIRECTORY, does it set the S_IFDIR bit on?
-
- open02
-
- Test if open without O_CREAT returns -1 if a file does not exist.
-
- open03
-
- Basic test for open(2)
-
- open04
-
- Testcase to check that open(2) sets EMFILE if a process opens files
- more than its descriptor size
-
- open05
-
- Testcase to check open(2) sets errno to EACCES correctly.
-
- open06
-
- Testcase to check open(2) sets errno to ENXIO correctly.
-
- open07
-
- Test the open(2) system call to ensure that it sets ELOOP correctly.
-
- open08
-
- Check for the following errors:
- 1. EEXIST
- 2. EISDIR
- 3. ENOTDIR
- 4. ENAMETOOLONG
- 5. EFAULT
- 6. ETXTBSY
-
- open09
-
- Does a read on a file opened with oflag set to O_WRONLY and checks for -1 return.
- Does a write on a file opened with oflag set to O_RDONLY and checks for -1 return.
-
- open10
-
- Verifies that the group ID and setgid bit are set correctly when a new file
- is created using open.
-
-
- pathconf01
-
- Basic test for pathconf(2)
-
-
- pause01
- Basic test for pause(2)
-
- pause02
-
- Verify that, pause() returns -1 and sets errno to EINTR after receipt
- of a signal which is caught by the calling process. Also, verify that
- the calling process will resume execution from the point of suspension.
-
- pause03
-
- Verify that a process is no longer accessible on receipt of SIGKILL
- signal after being suspended by pause().
-
-
- personality01
-
- personality01 - Check that we can set the personality for a process.
-
- personality02
-
- personality02 - Check that we get EINVAL for a bad personality.
-
-
- pipe01
-
- Testcase to check the basic functionality of the pipe(2) syscall:
- Check that both ends of the pipe (both file descriptors) are
- available to a process opening the pipe.
-
- pipe05
-
- Check what happens when pipe is passed a bad file descriptor.
-
- pipe06
-
- Check what happens when the system runs out of pipes.
-
- pipe08
-
- Check that a SIGPIPE signal is generated when a write is
- attempted on an empty pipe.
-
- pipe09
-
- Check that two processes can use the same pipe at the same time.
-
- pipe10
-
- Check that parent can open a pipe and have a child read from it
-
- pipe11
-
- Check if many children can read what is written to a pipe by the
- parent.
-
-
- poll01
-
- Verify that valid open file descriptor must be provided to poll() to
- succeed.
-
-
- prctl01
-
- Basic test of prctl().
-
- prctl02
-
- Test of error conditions for prctl().
-
-
- pread01
-
- Verify the functionality of pread() by writing known data using pwrite()
- to the file at various specified offsets and later read from the file from
- various specified offsets, comparing the data read aganist the data
- written.
-
- pread02
-
- Verify that,
- 1) pread() fails when attempted to read from an unnamed pipe.
- 2) pread() fails if the specified offset position was invalid.
-
-
- profil01
-
- Basic test of profil().
-
-
- ptrace01
-
- Functionality test for ptrace(2).
-
- ptrace02
-
- Functionality test for ptrace(2).
-
- ptrace3
-
- Tests for error conditions.
-
-
- pwrite01
-
- Verify the functionality of pwrite() by writing known data using pwrite()
- to the file at various specified offsets and later read from the file from
- various specified offsets, comparing the data written aganist the data
- read using read().
-
- pwrite02
-
- Verify that,
- 1) pwrite() fails when attempted to write to an unnamed pipe.
- 2) pwrite() fails if the specified offset position was invalid.
-
-
- read01
-
- Basic test for the read(2) system call
-
- read02
-
- test 1:
- Does read return -1 if file descriptor is not valid, check for EBADF
-
- test 2:
- Check if read sets EISDIR, if the fd refers to a directory
-
- test 3:
- Check if read sets EFAULT, if buf is -1.
-
- read03
-
- Testcase to check that read() sets errno to EAGAIN
-
- read04
-
- Testcase to check if read returns the number of bytes read correctly.
-
-
- readdir01
-
- Write multiple files and try to find them with readdir().
-
- readdir02
-
- Try to readdir with invalid directory stream descriptor dir.
-
-
- readlink01
-
- Verify that, readlink will succeed to read the contents of the symbolic
- link created the process.
-
- readlink02
-
- Basic test for the readlink(2) system call
-
- readlink03
-
- Verify that,
- 1) readlink(2) returns -1 and sets errno to EACCES if search/write
- permission is denied in the directory where the symbolic link
- resides.
- 2) readlink(2) returns -1 and sets errno to EINVAL if the buffer size
- is not positive.
- 3) readlink(2) returns -1 and sets errno to EINVAL if the specified
- file is not a symbolic link file.
- 4) readlink(2) returns -1 and sets errno to ENAMETOOLONG if the
- pathname component of symbolic link is too long (ie, > PATH_MAX).
- 5) readlink(2) returns -1 and sets errno to ENOENT if the component of
- symbolic link points to an empty string.
-
- readlink04
-
- Verify that, readlink call will succeed to read the contents of the
- symbolic link if invoked by non-root user who is not the owner of the
- symbolic link.
-
-
- readv01
-
- Testcase to check the basic functionality of the readv(2) system call.
-
- readv02
-
- Testcase to check the error conditions of the readv(2) system call.
-
-
- reboot01
-
- Test basic functionality of reboot().
-
- reboot02
-
- Test error conditions of reboot().
-
-
- recv01
-
- Verify that recv() returns the proper errno for various failure cases
-
-
- recvfrom01
-
- Verify that recvfrom() returns the proper errno for various failure cases
-
-
- recvmsg01
-
- Verify that recvmsg() returns the proper errno for various failure cases
-
-
- rename01
-
- This test will verify the rename(2) syscall basic functionality.
- Verify rename() works when the "new" file or directory does not exist.
-
- rename02
-
- Basic test for the rename(2) system call
-
- rename03
-
- This test will verify that rename(2) functions correctly
- when the "new" file or directory exists
-
- rename04
-
- This test will verify that rename(2) failed when newpath is
- a non-empty directory and return EEXIST or ENOTEMPTY
-
- rename05
-
- This test will verify that rename(2) fails with EISDIR
-
- rename06
-
- This test will verify that rename(2) failed in EINVAL
-
- rename07
-
- This test will verify that rename(2) failed in ENOTDIR
-
- rename08
-
- This test will verify that rename(2) syscall failed in EFAULT
-
- rename09
-
- check rename() fails with EACCES
-
- rename10
-
- This test will verify that rename(2) syscall fails with ENAMETOOLONG
- and ENOENT
-
- rename11
-
- This test will verify that rename(2) failed in EBUSY
-
- rename12
-
- check rename() fails with EPERM
-
- rename13
-
- Verify rename() return successfully and performs no other action
- when "old" file and "new" file link to the same file.
-
-
-
- rmdir01
-
- This test will verify that rmdir(2) syscall basic functionality.
- verify rmdir(2) returns a value of 0 and the directory being
- removed
-
- rmdir02
-
- This test will verify that rmdir(2) fail in
- 1. ENOTEMPTY
- 2. EBUSY
- 3. ENAMETOOLONG
- 4. ENOENT
- 5. ENOTDIR
- 6. EFAULT
- 7. EFAULT
-
- rmdir03
-
- check rmdir() fails with EPERM or EACCES
-
- rmdir04
-
- Basic test for the rmdir(2) system call
-
- rmdir05
-
- Verify that rmdir(2) returns a value of -1 and sets errno to indicate the error.
-
-
- sbrk01
-
- Basic test for the sbrk(2) system call.
-
-
- sched_get_priority_max01
-
- Basic test for sched_get_priority_max().
-
- sched_get_priority_max02
-
- Error condition test for sched_get_priority_max().
-
-
- sched_get_priority_min01
-
- Basic test for sched_get_priority_min().
-
- sched_get_priority_min02
-
- Error condition test for sched_get_priority_min().
-
-
- sched_getparam01
-
- Basic test for sched_getparam(2)
-
- sched_getparam02
-
- Get scheduling parametes for parent process
-
- sched_getparam03
-
- Testing error conditions for sched_getparam(2)
-
-
- sched_getscheduler01
-
- Testcase to check sched_getscheduler() returns correct return value
-
- sched_getscheduler02
-
- To check for the errno ESRCH
-
-
- sched_rr_get_interval01
-
- Basic test for sched_rr_get_interval(2)
-
- sched_rr_get_interval02
-
- Functionality test
-
- sched_rr_get_interval03
-
- Tests for error conditions
-
-
- sched_setparam01
-
- Basic test for sched_setparam(2)
-
- sched_setparam02
-
- Checks functionality for sched_setparam(2)
-
- sched_setparam03
-
- Checks functionality for sched_setparam(2) for pid!=0
-
- sched_setparam04
-
- Testing error conditions for sched_setparam(2)
-
- sched_setparam05
-
- Verify that sched_setparam() fails if the user does
-
-
- sched_setscheduler01
-
- Testcase to test whether sched_setscheduler(2) sets the errnos
- correctly.
-
- sched_setscheduler02
-
- Testcase to test whether sched_setscheduler(2) sets the errnos
- correctly.
-
-
- sched_yield01
-
- Testcase to check that sched_yield returns correct values.
-
-
- select01
-
- Basic test for the select(2) system call to a fd of regular file with no I/O
- and small timeout
-
- select02
-
- Basic test for the select(2) system call to fd of system pipe with no I/O
- and small timeout
-
- select03
-
- Basic test for the select(2) system call to fd of a named-pipe (FIFO)
-
- select04
-
- Verify that select(2) returns immediately (does not block) if the
- timeout value is zero.
-
- select05
-
- Verify that select(2) fails when one or more of the file descriptor sets
- specify a file descriptor which is not valid.
-
- select06
-
- Verify that select(2) fails when a signal is delivered before any of the
- selected events occur and before the timeout interval expires.
-
- select07
-
- Verify that select(2) fails when an invalid timeout interval is specified.
-
- select08
-
- Verify the functionality of select(2) by passing non-null writefds
- which points to a regular file, pipes or FIFO's.
-
- select09
-
- Verify the functionality of select(2) by passing non-null readfds
- which points to a regular file, pipes or FIFO's.
-
- select10
-
- Verify that a successful call to select() shall return the desired
- number of modified descriptors for which bits are set in the bit masks,
- where descriptors points to a regular file, pipes or FIFO's.
-
-
- send01
-
- Verify that send() returns the proper errno for various failure cases
-
-
- sendfile02
-
- Testcase to test the basic functionality of the sendfile(2) system call.
-
- sendfile03
-
- Testcase to test that sendfile(2) system call returns appropriete
- errnos on error.
-
-
- sendmsg01
-
- Verify that sendmsg() returns the proper errno for various failure cases
-
-
- sendto01
-
- Verify that sendto() returns the proper errno for various failure cases
-
-
- setdomainname01
-
- Basic test for setdomainame(2)
-
- setdomainname02
-
- Test for checking error conditions for setdomainame(2)
-
- setdomainname03
-
- Test for EPERM error value when run as non superuser
-
-
- setegid01
-
- Verify that setegid does not modify the saved gid or real gid.
-
-
- setfsgid01
-
- Testcase to check the basic functionality of setfsgid(2) system
- call.
-
-
- setfsuid01
-
- Testcase to test the basic functionality of the setfsuid(2) system
- call.
-
-
- setgid01
-
- Basic test for the setgid(2) system call.
-
- setgid02
-
- Testcase to ensure that the setgid() system call sets errno to EPERM
-
-
- setgroups01
-
- Basic test for the setgroups(2) system call.
-
- setgroups02
-
- Verify that,
- 1. setgroups() fails with -1 and sets errno to EINVAL if the size
- argument value is > NGROUPS
- 2. setgroups() fails with -1 and sets errno to EPERM if the
- calling process is not super-user.
-
- setgroups03
-
- Verify that, only root process can invoke setgroups() system call to
- set the supplementary group IDs of the process.
-
-
- setitimer01
-
- setitimer01 - check that a resonable setitimer() call succeeds.
-
- setitimer02
-
- setitimer02 - check that a setitimer() call fails as expected
- with incorrect values.
-
- setitimer03
-
- setitimer03 - check that a setitimer() call fails as expected
- with incorrect values.
-
- setpgid01
-
- Basic test for setpgid(2) system call.
-
- setpgid02
-
- Testcase to check that setpgid() sets errno correctly.
-
- setpgid03
-
- Test to check the error and trivial conditions in setpgid system call
-
-
- setpgrp01
-
- Basic test for the setpgrp(2) system call.
-
- setpgrp02
-
- Testcase to check the basic functionality of the setpgrp(2) syscall.
-
-
- setpriority01
-
- setpriority01 - set the priority for the test process lower.
-
- setpriority02
-
- setpriority02 - test for an expected failure by trying to raise
- the priority for the test process while not having
- permissions to do so.
-
- setpriority03
-
- setpriority03 - test for an expected failure by using an invalid
- PRIO value
- setpriority04
-
- setpriority04 - test for an expected failure by using an invalid
- process id
-
- setpriority05
-
- setpriority05 - test for an expected failure by trying to change
- a process with an ID that is different from the
- test process
-
- setregid01
-
- Basic test for the setregid(2) system call.
-
- setregid02
-
- Test that setregid() fails and sets the proper errno values when a
- non-root user attemps to change the real or effective group id to a
- value other than the current gid or the current effective gid.
-
- setregid03
-
- Test setregid() when executed by a non-root user.
-
- setregid04
-
- Test setregid() when executed by root.
-
-
- setresgid01
-
- Checks functionality of setresgid(2)
-
- setresgid02
-
- Checks functionality of setresgid(2) for non-root group id.
-
- setresgid03
-
- Checks error conditions for setresgid(2)
-
-
- setresuid01
-
- Test setresuid() when executed by root.
-
- setresuid02
-
- Test that a non-root user can change the real, effective and saved
- uid values through the setresuid system call.
-
- setresuid03
-
- Test that the setresuid system call sets the proper errno
- values when a non-root user attempts to change the real, effective or
- saved uid to a value other than one of the current uid, the current
- effective uid of the current saved uid. Also verify that setresuid
- fails if an invalid uid value is given.
-
-
- setreuid01
-
- Basic test for the setreuid(2) system call.
-
- setreuid02
-
- Test setreuid() when executed by root.
-
- setreuid03
-
- Test setreuid() when executed by an unpriviledged user.
-
- setreuid04
-
- Test that root can change the real and effective uid to an
- unpriviledged user.
-
- setreuid05
-
- Test the setreuid() feature, verifying the role of the saved-set-uid
- and setreuid's effect on it.
-
- setreuid06
-
- Test that EINVAL is set when setreuid is given an invalid user id.
-
-
- setrlimit01
-
- Testcase to check the basic functionality of the setrlimit system call.
-
- setrlimit02
-
- Testcase to test the different errnos set by setrlimit(2) system call.
-
- setrlimit03
-
- Test for EPERM when the super-user tries to increase RLIMIT_NOFILE
- beyond the system limit.
-
-
- setsid01
-
- Test to check the error and trivial conditions in setsid system call
-
-
- setsockopt01
-
- Verify that setsockopt() returns the proper errno for various failure cases
-
-
- settimeofday01
-
- Testcase to check the basic functionality of settimeofday().
-
- settimeofday02
-
- Testcase to check that settimeofday() sets errnos correctly.
-
-
- setuid01
-
- Basic test for the setuid(2) system call.
-
- setuid02
-
- Basic test for the setuid(2) system call as root.
-
- setuid03
-
- Test to check the error and trivial conditions in setuid
-
-
- sigaction01
-
- Test some features of sigaction (see below for more details)
-
-
- sigaction02
-
- Testcase to check the basic errnos set by the sigaction(2) syscall.
-
-
- sigaltstack01
-
- Send a signal using the main stack. While executing the signal handler
- compare a variable's address lying on the main stack with the stack
- boundaries returned by sigaltstack().
-
- sigaltstack02
-
- Verify that,
- 1. sigaltstack() fails and sets errno to EINVAL when "ss_flags" field
- pointed to by 'ss' contains invalid flags.
- 2. sigaltstack() fails and sets errno to ENOMEM when the size of alternate
- stack area is less than MINSIGSTKSZ.
-
-
- sighold02
-
- Basic test for the sighold02(2) system call.
-
-
- signal01
-
- signal01 - set the signal handler to our own function
-
- signal02
-
- signal02 - Test that we get an error using illegal signals
-
- signal03
-
- Boundary value and other invalid value checking of signal setup and signal
- sending.
-
- signal04
-
- signal04 - restore signals to default behavior
-
- signal05
-
- signal03 - set signals to be ignored
-
-
- sigpending02
-
- Test to see that the proper errors are returned by sigpending.
-
-
- sigprocmask01
-
- Verify that sigprocmask() succeeds to examine and change the calling
- process's signal mask.
- Also, verify that sigpending() succeeds to store signal mask that are
- blocked from delivery and pending for the calling process.
-
-
- sigrelse01
-
- Basic test for the sigrelse(2) system call.
-
-
- sigsuspend01
-
- Verify that sigsuspend() succeeds to change process's current signal
- mask with the specified signal mask and suspends the process execution
- until the delivery of a signal.
-
-
- socket01
-
- Verify that socket() returns the proper errno for various failure cases
-
-
- socketcall01
-
- Basic test for socketcall(2) for socket(2)
-
- socketcall02
-
- Error test for socketcall(2)
-
- socketcall03
-
- Basic test for socketcall(2) for bind(2)
-
- socketcall04
-
- Basic test for socketcall(2) for listen(2)
-
-
- socketpair01
-
- Verify that socketpair() returns the proper errno for various
- failure cases
-
-
- socketpair01
-
- Verify that socketpair() returns the proper errno for various failure cases
-
-
- sockioctl01
-
- Verify that ioctl() on sockets returns the proper errno for various
- failure cases
-
-
- stat01
-
- Verify that, stat(2) succeeds to get the status of a file and fills the
- stat structure elements.
-
- stat02
-
- Verify that, stat(2) succeeds to get the status of a file and fills the
- stat structure elements though process doesn't have read access to the
- file.
-
- stat03
-
- Verify that,
- 1) stat(2) returns -1 and sets errno to EACCES if search permission is
- denied on a component of the path prefix.
- 2) stat(2) returns -1 and sets errno to ENOENT if the specified file
- does not exists or empty string.
- 3) stat(2) returns -1 and sets errno to EFAULT if pathname points
- outside user's accessible address space.
- 4) stat(2) returns -1 and sets errno to ENAMETOOLONG if the pathname
- component is too long.
- 5) stat(2) returns -1 and sets errno to ENOTDIR if the directory
- component in pathname is not a directory.
-
- stat05
-
- Basic test for the stat05(2) system call.
-
-
- statfs01
-
- Basic test for the statfs(2) system call.
-
- statfs02
-
- Testcase to check that statfs(2) sets errno correctly.
-
-
- stime01
-
- Verify that the system call stime() successfully sets the system's idea
- of data and time if invoked by "root" user.
-
- stime02
-
- Verify that the system call stime() fails to set the system's idea
- of data and time if invoked by "non-root" user.
-
-
- string01
-
- Test string functions.
-
-
- swapoff01
-
- Basic test for swapoff(2)
-
- swapoff02
-
- Test checking for basic error conditions
-
-
- swapon01
-
- Basic test for swapon(2)
-
- swapon02
-
- Test checking for basic error conditions
-
-
- symlink01
-
- Test of various file function calls, such as rename or open, on a symbolic
- link file.
-
- symlink02
-
- Basic test for the symlink(2) system call.
-
- symlink03
-
- Verify that,
- 1) symlink(2) returns -1 and sets errno to EACCES if search/write
- permission is denied in the directory where the symbolic link is
- being created.
- 2) symlink(2) returns -1 and sets errno to EEXIST if the specified
- symbolic link already exists.
- 3) symlink(2) returns -1 and sets errno to EFAULT if the specified
- file or symbolic link points to invalid address.
- 4) symlink(2) returns -1 and sets errno to ENAMETOOLONG if the
- pathname component of symbolic link is too long (ie, > PATH_MAX).
- 5) symlink(2) returns -1 and sets errno to ENOTDIR if the directory
- component in pathname of symbolic link is not a directory.
- 6) symlink(2) returns -1 and sets errno to ENOENT if the component of
- symbolic link points to an empty string.
-
- symlink04
-
- Verify that, symlink will succeed to creat a symbolic link of an existing
- object name path.
-
- symlink05
-
- Verify that, symlink will succeed to creat a symbolic link of an
- non-existing object name path.
-
-
- sync01
-
- Basic test for the sync(2) system call.
-
- sync02
-
- Open a file for write; modify the file, then do a sync().
- Verify that the data has been written to disk by re-opening the file.
-
-
- syscall01
-
- Basic test for the syscall() system call.
-
-
- sysconf01
-
- Basic test for the sysconf() system call.
-
-
- sysctl01
-
- Testcase for testing the basic functionality of sysctl(2) system call.
- This testcase attempts to read the kernel parameters using
- sysctl({CTL_KERN, KERN_ }, ...) and compares it with the known
- values.
-
- sysctl03
-
- Testcase to check that sysctl(2) sets errno to EPERM correctly.
-
-
- sysctl04
-
- Testcase to check that sysctl(2) sets errno to ENOTDIR
-
-
- sysctl05
-
- Testcase to check that sysctl(2) sets errno to EFAULT
-
-
- sysfs01
-
- Basic test for sysfs(2)
-
- sysfs02
-
- Basic test for sysfs(2)
-
- sysfs03
-
- Basic test for sysfs(2)
-
- sysfs04
-
- Test checking for basic error conditions
-
- sysfs05
-
- Test checking for basic error conditions
-
- sysfs06
-
- Test checking for basic error conditions
-
-
- sysinfo01
-
- Verify that sysinfo() succeeds to get the system information and fills
- the structure passed.
-
- sysinfo02
-
- Verify that sysinfo() returns the correct error for an invalid address structure.
-
- syslog01
-
- Test whether messages are logged to the specified file
-
- syslog02
-
- Test if messages of all levels are logged.
-
- syslog03
-
- Do openlog(), log the messages and see whether
- ident string is prepended to the message.
-
- syslog04
-
- Test the logging option: LOG_PID
-
- syslog05
-
- Test the logging option: LOG_CONS
-
- syslog06
-
- Test the logging option: LOG_NDELAY
-
- syslog07
-
- Test the priorities.
-
- syslog08
-
- Test all the facilities at a particular level.
-
- syslog09
-
- Test setlogmask() with LOG_UPTO macro.
-
- syslog10
-
- Test setlogmask() with LOG_MASK macro.
-
- syslog11
-
- Basic test for syslog() function call.
-
- syslog12
-
- Check error conditions for syscall().
-
-
- time01
-
- Basic test for the time(2) system call.
-
- time02
-
- Verify that time(2) returns the value of time in seconds since
- the Epoch and stores this value in the memory pointed to by the parameter.
-
-
- times01
-
- Basic test for the times(2) system call.
-
- times03
-
- Testcase to check the basic functionality of the times() system call.
-
-
- truncate01
-
- Verify that, truncate(2) succeeds to truncate a file to a specified
- length.
-
- truncate02
-
- Verify that, truncate(2) succeeds to truncate a file to a certain length,
- but the attempt to read past the truncated length will fail.
-
- truncate03
-
- Verify that,
- 1) truncate(2) returns -1 and sets errno to EACCES if search/write
- permission denied for the process on the component of the path prefix
- or named file.
- 2) truncate(2) returns -1 and sets errno to ENOTDIR if the component of
- the path prefix is not a directory.
- 3) truncate(2) returns -1 and sets errno to EFAULT if pathname points
- outside user's accessible address space.
- 4) truncate(2) returns -1 and sets errno to ENAMETOOLONG if the component
- of a pathname exceeded 255 characters or entire pathname exceeds 1023
- characters.
- 5) truncate(2) returns -1 and sets errno to ENOENT if the named file
- does not exist.
-
-
- ulimit01
-
- Basic test for the ulimit(2) system call.
-
-
- umask01
-
- Basic test for the umask(2) system call.
-
- umask02
-
- Check that umask changes the mask, and that the previous
- value of the mask is returned correctly for each value.
-
- umask03
-
- Check that umask changes the mask, and that the previous
- value of the mask is returned correctly for each value.
-
-
- umount01
-
- Basic test for umount(2)
-
- umount02
-
- Test for checking basic error conditions for umount(2)
-
- umount03
-
- Test for checking EPERM
-
- umount04
-
- Test for checking EACCES
-
-
- uname01
-
- Basic test for the uname(2) system call.
-
- uname02
-
- Call uname() with an invalid address to produce a failure
-
- uname03
-
- Call uname() and make sure it succeeds
-
-
-
- unlink05
-
- Basic test for the unlink(2) system call.
-
- unlink06
-
- Test for the unlink(2) system call of a FIFO.
-
- unlink07
-
- Tests for error handling for the unlink(2) system call.
-
- unlink08
-
- More tests for error handling for the unlink(2) system call.
-
-
- ustat01
-
- Basic test for the ustat() system call.
-
- ustat02
-
- Test for error conditions of ustat().
-
-
- utime01
-
- Verify that the system call utime() successfully sets the modification
- and access times of a file to the current time, if the times argument
- is null, and the user ID of the process is "root".
-
- utime02
-
- Verify that the system call utime() successfully sets the modification
- and access times of a file to the current time, under the following
- constraints,
- - The times argument is null.
- - The user ID of the process is not "root".
- - The file is owned by the user ID of the process.
-
- utime03
-
- Verify that the system call utime() successfully sets the modification
- and access times of a file to the current time, under the following
- constraints,
- - The times argument is null.
- - The user ID of the process is not "root".
- - The file is not owned by the user ID of the process.
- - The user ID of the process has write access to the file.
-
- utime04
-
- Verify that the system call utime() successfully sets the modification
- and access times of a file to the time specified by times argument, if
- the times argument is not null, and the user ID of the process is "root".
-
- utime05
-
- Verify that the system call utime() successfully sets the modification
- and access times of a file to the value specified by the times argument
- under the following constraints,
- - The times argument is not null,
- - The user ID of the process is not "root".
- - The file is owned by the user ID of the process.
-
- utime06
-
- 1. Verify that the system call utime() fails to set the modification
- and access times of a file to the current time, under the following
- constraints,
- - The times argument is null.
- - The user ID of the process is not "root".
- - The file is not owned by the user ID of the process.
- - The user ID of the process does not have write access to the
- file.
- 2. Verify that the system call utime() fails to set the modification
- and access times of a file if the specified file doesn't exist.
-
-
- vfork01
-
- Fork a process using vfork() and verify that, the attribute values like
- euid, ruid, suid, egid, rgid, sgid, umask, inode and device number of
- root and current working directories are same as that of the parent
- process.
-
- vfork02
-
- Fork a process using vfork() and verify that, the pending signals in
- the parent are not pending in the child process.
-
-
- vhangup01
-
- Check the return value, and errno of vhangup(2)
- when a non-root user calls vhangup().
-
- vhangup02
-
- To test the basic functionality of vhangup(2)
-
-
- wait02
-
- Basic test for wait(2) system call.
-
-
- wait401
-
- wait401 - check that a call to wait4() correctly waits for a child
- process to exit
-
- wait402
-
- wait402 - check for ECHILD errno when using an illegal pid value
-
-
- waitpid01
-
- Check that when a child kills itself by generating an alarm
- exception, the waiting parent is correctly notified.
-
- waitpid02
-
- Check that when a child kills itself by generating an integer zero
- divide exception, the waiting parent is correctly notified.
-
- waitpid03
-
- Check that parent waits unitl specific child has returned.
-
- waitpid04
-
- test to check the error conditions in waitpid sys call
-
- waitpid05
-
- Check that when a child kills itself with a kill statement after
- determining its process id by using getpid, the parent receives a
- correct report of the cause of its death. This also indirectly
- checks that getpid returns the correct process id.
-
- waitpid06
-
- Tests to see if pid's returned from fork and waitpid are same.
-
- waitpid07
-
- Tests to see if pid's returned from fork and waitpid are same.
-
- waitpid08
-
- Tests to see if pid's returned from fork and waitpid are same
-
- waitpid09
-
- Check ability of parent to wait until child returns, and that the
- child's process id is returned through the waitpid. Check that
- waitpid returns immediately if no child is present.
-
- waitpid10
-
- Tests to see if pid's returned from fork and waitpid are same
-
-
- waitpid11
-
- Tests to see if pid's returned from fork and waitpid are same
-
-
- waitpid12
-
- Tests to see if pid's returned from fork and waitpid are same
-
-
- waitpid13
-
- Tests to see if pid's returned from fork and waitpid are same
-
-
- write01
-
- Basic test for write(2) system call.
-
- write02
-
- Basic functionality test: does the return from write match the count
- of the number of bytes written.
-
- write03
-
- Testcase to check that write(2) doesn't corrupt a file when it fails
-
- write04
-
- Testcase to check that write() sets errno to EAGAIN
-
- write05
-
- Check the return value, and errnos of write(2)
- - when the file descriptor is invalid - EBADF
- - when the buf parameter is invalid - EFAULT
- - on an attempt to write to a pipe that is not open for reading - EPIPE
-
-
- writev01
-
- Testcase to check the basic functionality of writev(2) system call.
-
- writev02
-
- In these testcases, writev() is called with partially valid data
- to be written in a sparse file.
-
-
- writev03
-
- The testcases are written calling writev() with partially valid data
- to overwrite the contents, to write in the beginning and to write in
- the end of the file.
-
- writev04
-
- The testcases are written calling writev() with partially valid data
- to overwrite the contents, to write in the beginning and to write in
- the end of the file. This is same as writev03, but the length of
- buffer used here is 8192 bytes.
-
- writev05
-
- These testcases are written to test writev() on sparse files. This
- is same as writev02. But the initial write() with valid data is
- done at the beginning of the file.
-
-
-
-timers
-------
- clock_gettime02
-
- Basic test for clock_gettime(2)
-
- clock_gettime03
-
- Test checking for basic error conditions for clock_gettime(2)
-
-
- clock_settime02
-
- Basic test for clock_settime(2)
-
- clock_settime03
-
- Test checking for basic error conditions for clock_settime(2)
-
-
- timer_create01
-
- Basic test for timer_create(2)
-
- timer_create02
-
- Basic test for timer_create(2)
-
- timer_create03
-
- Test checking for basic error conditions for timer_create(2)
-
-
- timer_delete01
-
- Basic test for timer_delete(2)
-
- timer_delete02
-
- Test checking for basic error conditions for timer_delete(2)
-
-
- timer_settime01
-
- Basic test for timer_settime(2)
-
- timer_settime02
-
- Test checking for basic error conditions for timer_settime(2)
-
-
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/sched/tool/time-schedule.c
+ <\test_location>
+<\testname>
+<testname=trace_sched>
+ <description>
+ This utility spawns N tasks, each task sets its priority by
+ making a system call to the scheduler. The thread function
+ reads the priority that tbe schedular sets for this task and
+ also reads from /proc the processor this task last executed on
+ the information that is gathered by the thread function may
+ be in real-time. Its only an approximation.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/sched/tool/trace_sched.c
+ <\test_location>
+<\testname>
+<testname=abort01>
+ <description>
+ Basic test for abort(3).
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/abort/abort01.c
+ <\test_location>
+<\testname>
+<testname=accept01>
+ <description>
+ Verify that accept() returns the proper errno for various failure cases
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/accept/accept01.c
+ <\test_location>
+<\testname>
+<testname=access01>
+ <description>
+ Basic test for access(2) using F_OK, R_OK, W_OK, and X_OK arguments.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/access/access01.c
+ <\test_location>
+<\testname>
+<testname=access02>
+ <description>
+ Verify that access() succeeds to check the read/write/execute permissions
+ on a file if the mode argument passed was R_OK/W_OK/X_OK.
+
+ Also verify that, access() succeeds to test the accessibility of the file
+ referred to by symbolic link if the pathname points to a symbolic link.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/access/access02.c
+ <\test_location>
+<\testname>
+<testname=access03>
+ <description>
+ EFAULT error testing for access(2).
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/access/access03.c
+ <\test_location>
+<\testname>
+<testname=access04>
+ <description>
+ Verify that,
+ 1. access() fails with -1 return value and sets errno to EACCES
+ if the permission bits of the file mode do not permit the
+ requested (Read/Write/Execute) access.
+ 2. access() fails with -1 return value and sets errno to EINVAL
+ if the specified access mode argument is invalid.
+ 3. access() fails with -1 return value and sets errno to EFAULT
+ if the pathname points outside allocate address space for the
+ process.
+ 4. access() fails with -1 return value and sets errno to ENOENT
+ if the specified file doesn't exist (or pathname is NULL).
+ 5. access() fails with -1 return value and sets errno to ENAMETOOLONG
+ if the pathname size is > PATH_MAX characters.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/access/access04.c
+ <\test_location>
+<\testname>
+<testname=access05>
+ <description>
+ Verify that access() succeeds to check the existance of a file if
+ search access is permitted on the pathname of the specified file.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/access/access05.c
+ <\test_location>
+<\testname>
+<testname=acct01>
+ <description>
+ Issues calls to acct() and tests the returned values against expected
+ results
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/acct/acct01.c
+ <\test_location>
+<\testname>
+<testname=acct02>
+ <description>
+ Issues calls to acct() and tests the returned values against expected
+ results
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/acct/acct02.c
+ <\test_location>
+<\testname>
+<testname=adjtimex01>
+ <description>
+ Basic test for adjtimex().
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/adjtimex/adjtimex01.c
+ <\test_location>
+<\testname>
+<testname=adjtimex02>
+ <description>
+ Tests for error conditions.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/adjtimex/adjtimex02.c
+ <\test_location>
+<\testname>
+<testname=alarm01>
+ <description>
+ Basic test for alarm(2).
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/alarm/alarm01.c
+ <\test_location>
+<\testname>
+<testname=alarm02>
+ <description>
+ Boundary Value Test for alarm(2).
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/alarm/alarm02.c
+ <\test_location>
+<\testname>
+<testname=alarm03>
+ <description>
+ Alarm(2) cleared by a fork.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/alarm/alarm03.c
+ <\test_location>
+<\testname>
+<testname=alarm04>
+ <description>
+ Check that when an alarm request is made, the signal SIGALRM is received
+ even after the process has done an exec().
+
+ <\description>
+ <test_location>
+ <\test_location>
+<\testname>
+<testname=alarm05>
+ <description>
+ Check the functionality of the Alarm system call when the time input
+ parameter is non zero.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/alarm/alarm05.c
+ <\test_location>
+<\testname>
+<testname=alarm06>
+ <description>
+ Check the functionality of the Alarm system call when the time input
+ parameter is zero.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/alarm/alarm06.c
+ <\test_location>
+<\testname>
+<testname=alarm07>
+ <description>
+ Check the functionality of the alarm() when the time input
+ parameter is non-zero and the process does a fork.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/alarm/alarm07.c
+ <\test_location>
+<\testname>
+<testname=asyncio02>
+ <description>
+ Write/close flushes data to the file.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/asyncio/asyncio02.c
+ <\test_location>
+<\testname>
+<testname=bind01>
+ <description>
+ Verify that bind() returns the proper errno for various failure cases
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/bind/bind01.c
+ <\test_location>
+<\testname>
+<testname=brk01>
+ <description>
+ Test the basic functionality of brk().
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/brk/brk01.c
+ <\test_location>
+<\testname>
+<testname=capget01>
+ <description>
+ Test the basic functionality of capget().
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/capget/capget01.c
+ <\test_location>
+<\testname>
+<testname=capget02>
+ <description>
+ Test the error conditions of capget().
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/capget/capget02.c
+ <\test_location>
+<\testname>
+<testname=capset01>
+ <description>
+ Test the basic functionality of capset().
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/capset/capset01.c
+ <\test_location>
+<\testname>
+<testname=capset02>
+ <description>
+ Test the error conditions of capset().
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/capset/capset02.c
+ <\test_location>
+<\testname>
+<testname=chdir01>
+ <description>
+ Check proper operation of chdir(): tests whether the
+ system call can it change the current, working directory, and find a
+ file there? Will it fail on a non-directory entry ?
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/chdir/chdir01.c
+ <\test_location>
+<\testname>
+<testname=chdir02>
+ <description>
+ Basic test for chdir(2).
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/chdir/chdir02.c
+ <\test_location>
+<\testname>
+<testname=chdir03>
+ <description>
+ Testcase for testing that chdir(2) sets EACCES errno
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/chdir/chdir03.c
+ <\test_location>
+<\testname>
+<testname=chdir04>
+ <description>
+ Testcase to test whether chdir(2) sets errno correctly.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/chdir/chdir04.c
+ <\test_location>
+<\testname>
+<testname=chmod01>
+ <description>
+ Verify that, chmod(2) succeeds when used to change the mode permissions
+ of a file.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/chmod/chmod01.c
+ <\test_location>
+<\testname>
+<testname=chmod02>
+ <description>
+ Basic test for chmod(2).
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/chmod/chmod02.c
+ <\test_location>
+<\testname>
+<testname=chmod03>
+ <description>
+ Verify that, chmod(2) will succeed to change the mode of a file
+ and set the sticky bit on it if invoked by non-root (uid != 0)
+ process with the following constraints,
+ - the process is the owner of the file.
+ - the effective group ID or one of the supplementary group ID's of the
+ process is equal to the group ID of the file.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/chmod/chmod03.c
+ <\test_location>
+<\testname>
+<testname=chmod04>
+ <description>
+ Verify that, chmod(2) will succeed to change the mode of a directory
+ and set the sticky bit on it if invoked by non-root (uid != 0) process
+ with the following constraints,
+ - the process is the owner of the directory.
+ - the effective group ID or one of the supplementary group ID's of the
+ process is equal to the group ID of the directory.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/chmod/chmod04.c
+ <\test_location>
+<\testname>
+<testname=chmod05>
+ <description>
+ Verify that, chmod(2) will succeed to change the mode of a directory
+ but fails to set the setgid bit on it if invoked by non-root (uid != 0)
+ process with the following constraints,
+ - the process is the owner of the directory.
+ - the effective group ID or one of the supplementary group ID's of the
+ process is not equal to the group ID of the directory.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/chmod/chmod05.c
+ <\test_location>
+<\testname>
+<testname=chmod06>
+ <description>
+ Verify that,
+ 1) chmod(2) returns -1 and sets errno to EPERM if the effective user id
+ of process does not match the owner of the file and the process is
+ not super user.
+ 2) chmod(2) returns -1 and sets errno to EACCES if search permission is
+ denied on a component of the path prefix.
+ 3) chmod(2) returns -1 and sets errno to EFAULT if pathname points
+ outside user's accessible address space.
+ 4) chmod(2) returns -1 and sets errno to ENAMETOOLONG if the pathname
+ component is too long.
+ 5) chmod(2) returns -1 and sets errno to ENOTDIR if the directory
+ component in pathname is not a directory.
+ 6) chmod(2) returns -1 and sets errno to ENOENT if the specified file
+ does not exists.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/chmod/chmod06.c
+ <\test_location>
+<\testname>
+<testname=chmod07>
+ <description>
+ Verify that, chmod(2) will succeed to change the mode of a file/directory
+ and sets the sticky bit on it if invoked by root (uid = 0) process with
+ the following constraints,
+ - the process is not the owner of the file/directory.
+ - the effective group ID or one of the supplementary group ID's of the
+ process is equal to the group ID of the file/directory.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/chmod/chmod07.c
+ <\test_location>
+<\testname>
+<testname=chown01>
+ <description>
+ Basic test for chown(2).
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/chown/chown01.c
+ <\test_location>
+<\testname>
+<testname=chown02>
+ <description>
+ Verify that, when chown(2) invoked by super-user to change the owner and
+ group of a file specified by path to any numeric owner(uid)/group(gid)
+ values,
+ - clears setuid and setgid bits set on an executable file.
+ - preserves setgid bit set on a non-group-executable file.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/chown/chown02.c
+ <\test_location>
+<\testname>
+<testname=chown03>
+ <description>
+ Verify that, chown(2) succeeds to change the group of a file specified
+ by path when called by non-root user with the following constraints,
+ - euid of the process is equal to the owner of the file.
+ - the intended gid is either egid, or one of the supplementary gids
+ of the process.
+ Also, verify that chown() clears the setuid/setgid bits set on the file.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/chown/chown03.c
+ <\test_location>
+<\testname>
+<testname=chown04>
+ <description>
+ Verify that,
+ 1) chown(2) returns -1 and sets errno to EPERM if the effective user id
+ of process does not match the owner of the file and the process is
+ not super user.
+ 2) chown(2) returns -1 and sets errno to EACCES if search permission is
+ denied on a component of the path prefix.
+ 3) chown(2) returns -1 and sets errno to EFAULT if pathname points
+ outside user's accessible address space.
+ 4) chown(2) returns -1 and sets errno to ENAMETOOLONG if the pathname
+ component is too long.
+ 5) chown(2) returns -1 and sets errno to ENOTDIR if the directory
+ component in pathname is not a directory.
+ 6) chown(2) returns -1 and sets errno to ENOENT if the specified file
+ does not exists.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/chown/chown04.c
+ <\test_location>
+<\testname>
+<testname=chown05>
+ <description>
+ Verify that, chown(2) succeeds to change the owner and group of a file
+ specified by path to any numeric owner(uid)/group(gid) values when invoked
+ by super-user.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/chown/chown05.c
+ <\test_location>
+<\testname>
+<testname=chroot01>
+ <description>
+ Testcase to check the whether chroot sets errno to EPERM.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/chroot/chroot01.c
+ <\test_location>
+<\testname>
+<testname=chroot02>
+ <description>
+ Test functionality of chroot(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/chroot/chroot02.c
+ <\test_location>
+<\testname>
+<testname=chroot03>
+ <description>
+ Testcase to test whether chroot(2) sets errno correctly.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/chroot/chroot03.c
+ <\test_location>
+<\testname>
+<testname=clone01>
+ <description>
+ Basic test for clone(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/clone/clone01.c
+ <\test_location>
+<\testname>
+<testname=clone02>
+ <description>
+ Functionality tests for clone(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/clone/clone02.c
+ <\test_location>
+<\testname>
+<testname=clone03>
+ <description>
+ Test for clone(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/clone/clone03.c
+ <\test_location>
+<\testname>
+<testname=clone04>
+ <description>
+ Test for checking error conditions for clone(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/clone/clone04.c
+ <\test_location>
+<\testname>
+<testname=clone05>
+ <description>
+ Test for CLONE_VFORK flag
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/clone/clone05.c
+ <\test_location>
+<\testname>
+<testname=clone06>
+ <description>
+ Test to verify inheritance of environment variables.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/clone/clone06.c
+ <\test_location>
+<\testname>
+<testname=close01>
+ <description>
+ Test that closing a regular file and a pipe works correctly
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/close/close01.c
+ <\test_location>
+<\testname>
+<testname=close02>
+ <description>
+ Check that an invalid file descriptor returns EBADF
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/close/close02.c
+ <\test_location>
+<\testname>
+<testname=close08>
+ <description>
+ Basic test for close(2).
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/close/close08.c
+ <\test_location>
+<\testname>
+<testname=confstr01>
+ <description>
+ Basic test for confstr().
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/confstr/confstr01.c
+ <\test_location>
+<\testname>
+<testname=connect01>
+ <description>
+ Verify that connect() returns the proper errno for various failure cases
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/connect/connect01.c
+ <\test_location>
+<\testname>
+<testname=creat01>
+ <description>
+ Testcase to check the basic functionality of the creat(2) system call.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/creat/creat01.c
+ <\test_location>
+<\testname>
+<testname=creat03>
+ <description>
+ Testcase to check whether the sticky bit cleared.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/creat/creat03.c
+ <\test_location>
+<\testname>
+<testname=creat04>
+ <description>
+ Testcase to check creat(2) fails with EACCES
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/creat/creat04.c
+ <\test_location>
+<\testname>
+<testname=creat05>
+ <description>
+ Testcase to check that creat(2) system call returns EMFILE.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/creat/creat05.c
+ <\test_location>
+<\testname>
+<testname=creat06>
+ <description>
+ Testcase to check creat(2) sets the following errnos correctly:
+ 1. EISDIR
+ 2. ENAMETOOLONG
+ 3. ENOENT
+ 4. ENOTDIR
+ 5. EFAULT
+ 6. EACCES
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/creat/creat06.c
+ <\test_location>
+<\testname>
+<testname=creat07>
+ <description>
+ Testcase to check creat(2) sets the following errnos correctly:
+ 1. ETXTBSY
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/creat/creat07.c
+ <\test_location>
+<\testname>
+<testname=creat08>
+ <description>
+ Verifies that the group ID and setgid bit are set correctly when
+ a new file is created.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/creat/creat08.c
+ <\test_location>
+<\testname>
+<testname=creat09>
+ <description>
+ Basic test for creat(2) using 0700 argument.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/creat/creat09.c
+ <\test_location>
+<\testname>
+<testname=dup01>
+ <description>
+ Basic test for dup(2).
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/dup/dup01.c
+ <\test_location>
+<\testname>
+<testname=dup02>
+ <description>
+ Negative test for dup(2) with bad fd.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/dup/dup02.c
+ <\test_location>
+<\testname>
+<testname=dup03>
+ <description>
+ Negative test for dup(2) (too many fds).
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/dup/dup03.c
+ <\test_location>
+<\testname>
+<testname=dup04>
+ <description>
+ Basic test for dup(2) of a system pipe descriptor.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/dup/dup04.c
+ <\test_location>
+<\testname>
+<testname=dup05>
+ <description>
+ Basic test for dup(2) of a named pipe descriptor.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/dup/dup05.c
+ <\test_location>
+<\testname>
+<testname=dup06>
+ <description>
+ Test if dup returns -1 on the 21st file when _NFILE is 20.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/dup/dup06.c
+ <\test_location>
+<\testname>
+<testname=dup07>
+ <description>
+ Test if the access mode is the same for both file descriptors.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/dup/dup07.c
+ <\test_location>
+<\testname>
+<testname=dup201>
+ <description>
+ Negative tests for dup2() with bad fd (EBADF), and for "too many
+ open files" (EMFILE)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/dup2/dup201.c
+ <\test_location>
+<\testname>
+<testname=dup202>
+ <description>
+ Is the access mode the same for both file descriptors?
+ 0: read only ? "0444"
+ 1: write only ? "0222"
+ 2: read/write ? "0666"
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/dup2/dup202.c
+ <\test_location>
+<\testname>
+<testname=dup203>
+ <description>
+ Testcase to check the basic functionality of dup2().
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/dup2/dup203.c
+ <\test_location>
+<\testname>
+<testname=dup204>
+ <description>
+ Testcase to check the basic functionality of dup2(2).
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/dup2/dup204.c
+ <\test_location>
+<\testname>
+<testname=dup205>
+ <description>
+ Testcase to check if -1 is returned on the 21st file when _NFILE is 20.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/dup2/dup205.c
+ <\test_location>
+<\testname>
+<testname=execl01>
+ <description>
+ Basic test for execl(2).
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/execl/execl01.c
+ <\test_location>
+<\testname>
+<testname=execle01>
+ <description>
+ Basic test for execle(2).
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/execle/execle01.c
+ <\test_location>
+<\testname>
+<testname=execlp01>
+ <description>
+ Basic test for execlp(2).
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/execlp/execlp01.c
+ <\test_location>
+<\testname>
+<testname=execv01>
+ <description>
+ Basic test for execv(2).
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/execv/execv01.c
+ <\test_location>
+<\testname>
+<testname=execve01>
+ <description>
+ Basic test for execve(2).
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/execve/execve01.c
+ <\test_location>
+<\testname>
+<testname=execve02>
+ <description>
+ Testcase to check whether execve(2) sets errno to EACCES correctly
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/execve/execve02.c
+ <\test_location>
+<\testname>
+<testname=execve03>
+ <description>
+ Testcase to check execve sets the following errnos correctly:
+ 1. ENAMETOOLONG
+ 2. ENOENT
+ 3. ENOTDIR
+ 4. EFAULT
+ 5. EACCES
+ 6. ENOEXEC
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/execve/execve03.c
+ <\test_location>
+<\testname>
+<testname=execve04>
+ <description>
+ Testcase to check execve(2) sets errno to EMFILE correctly
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/execve/execve04.c
+ <\test_location>
+<\testname>
+<testname=execve05>
+ <description>
+ Testcase to check execve sets the following errnos correctly:
+ 1. ETXTBSY
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/execve/execve05.c
+ <\test_location>
+<\testname>
+<testname=execvp01>
+ <description>
+ Basic test for execvp(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/execvp/execvp01.c
+ <\test_location>
+<\testname>
+<testname=exit01>
+ <description>
+ Check that exit returns the correct values to the waiting parent
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/exit/exit01.c
+ <\test_location>
+<\testname>
+<testname=exit02>
+ <description>
+ Check that exit flushes output file buffers and closes files upon
+ exitting
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/exit/exit02.c
+ <\test_location>
+<\testname>
+<testname=fchdir01>
+ <description>
+ create a directory and cd into it.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/fchdir/fchdir01.c
+ <\test_location>
+<\testname>
+<testname=fchdir02>
+ <description>
+ try to cd into a bad directory (bad fd).
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/fchdir/fchdir02.c
+ <\test_location>
+<\testname>
+<testname=fchmod01>
+ <description>
+ Basic test for Fchmod(2).
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/fchmod/fchmod01.c
+ <\test_location>
+<\testname>
+<testname=fchmod02>
+ <description>
+ Verify that, fchmod(2) will succeed to change the mode of a file/directory
+ set the sticky bit on it if invoked by root (uid = 0) process with
+ the following constraints,
+ - the process is not the owner of the file/directory.
+ - the effective group ID or one of the supplementary group ID's of the
+ process is equal to the group ID of the file/directory.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/fchmod/fchmod02.c
+ <\test_location>
+<\testname>
+<testname=fchmod03>
+ <description>
+ Verify that, fchmod(2) will succeed to change the mode of a file
+ and set the sticky bit on it if invoked by non-root (uid != 0)
+ process with the following constraints,
+ - the process is the owner of the file.
+ - the effective group ID or one of the supplementary group ID's of the
+ process is equal to the group ID of the file.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/fchmod/fchmod03.c
+ <\test_location>
+<\testname>
+<testname=fchmod04>
+ <description>
+ Verify that, fchmod(2) will succeed to change the mode of a directory
+ and set the sticky bit on it if invoked by non-root (uid != 0) process
+ with the following constraints,
+ - the process is the owner of the directory.
+ - the effective group ID or one of the supplementary group ID's of the
+ process is equal to the group ID of the directory.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/fchmod/fchmod04.c
+ <\test_location>
+<\testname>
+<testname=fchmod05>
+ <description>
+ Verify that, fchmod(2) will succeed to change the mode of a directory
+ but fails to set the setgid bit on it if invoked by non-root (uid != 0)
+ process with the following constraints,
+ - the process is the owner of the directory.
+ - the effective group ID or one of the supplementary group ID's of the
+ process is not equal to the group ID of the directory.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/fchmod/fchmod05.c
+ <\test_location>
+<\testname>
+<testname=fchmod06>
+ <description>
+ Verify that,
+ 1) fchmod(2) returns -1 and sets errno to EPERM if the effective user id
+ of process does not match the owner of the file and the process is
+ not super user.
+ 2) fchmod(2) returns -1 and sets errno to EBADF if the file descriptor
+ of the specified file is not valid.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/fchmod/fchmod06.c
+ <\test_location>
+<\testname>
+<testname=fchmod07>
+ <description>
+ Verify that, fchmod(2) succeeds when used to change the mode permissions
+ of a file specified by file descriptor.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/fchmod/fchmod07.c
+ <\test_location>
+<\testname>
+<testname=fchown01>
+ <description>
+ Basic test for fchown(2).
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/fchown/fchown01.c
+ <\test_location>
+<\testname>
+<testname=fchown02>
+ <description>
+ Verify that, when fchown(2) invoked by super-user to change the owner and
+ group of a file specified by file descriptor to any numeric
+ owner(uid)/group(gid) values,
+ - clears setuid and setgid bits set on an executable file.
+ - preserves setgid bit set on a non-group-executable file.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/fchown/fchown02.c
+ <\test_location>
+<\testname>
+<testname=fchown03>
+ <description>
+ Verify that, fchown(2) succeeds to change the group of a file specified
+ by path when called by non-root user with the following constraints,
+ - euid of the process is equal to the owner of the file.
+ - the intended gid is either egid, or one of the supplementary gids
+ of the process.
+ Also, verify that fchown() clears the setuid/setgid bits set on the file.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/fchown/fchown03.c
+ <\test_location>
+<\testname>
+<testname=fchown04>
+ <description>
+ Verify that,
+ 1) fchown(2) returns -1 and sets errno to EPERM if the effective user id
+ of process does not match the owner of the file and the process is
+ not super user.
+ 2) fchown(2) returns -1 and sets errno to EBADF if the file descriptor
+ of the specified file is not valid.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/fchown/fchown04.c
+ <\test_location>
+<\testname>
+<testname=fchown05>
+ <description>
+ Verify that, fchown(2) succeeds to change the owner and group of a file
+ specified by file descriptor to any numeric owner(uid)/group(gid) values
+ when invoked by super-user.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/fchown/fchown05.c
+ <\test_location>
+<\testname>
+<testname=fcntl01>
+ <description>
+ Test F_DUPFD, F_SETFL cmds of fcntl
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/fcntl/fcntl01.c
+ <\test_location>
+<\testname>
+<testname=fcntl02>
+ <description>
+ Basic test for fcntl(2) using F_DUPFD argument.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/fcntl/fcntl02.c
+ <\test_location>
+<\testname>
+<testname=fcntl03>
+ <description>
+ Basic test for fcntl(2) using F_GETFD argument.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/fcntl/fcntl03.c
+ <\test_location>
+<\testname>
+<testname=fcntl04>
+ <description>
+ Basic test for fcntl(2) using F_GETFL argument.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/fcntl/fcntl04.c
+ <\test_location>
+<\testname>
+<testname=fcntl05>
+ <description>
+ Basic test for fcntl(2) using F_GETLK argument.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/fcntl/fcntl05.c
+ <\test_location>
+<\testname>
+<testname=fcntl06>
+ <description>
+ Error checking conditions for remote locking of regions of a file.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/fcntl/fcntl06.c
+ <\test_location>
+<\testname>
+<testname=fcntl07>
+ <description>
+ Close-On-Exec functional test.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/fcntl/fcntl07.c
+ <\test_location>
+<\testname>
+<testname=fcntl07B>
+ <description>
+ Close-On-Exec of named pipe functional test.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/fcntl/fcntl07B.c
+ <\test_location>
+<\testname>
+<testname=fcntl08>
+ <description>
+ Basic test for fcntl(2) using F_SETFL argument.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/fcntl/fcntl08.c
+ <\test_location>
+<\testname>
+<testname=fcntl09>
+ <description>
+ Basic test for fcntl(2) using F_SETLK argument.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/fcntl/fcntl09.c
+ <\test_location>
+<\testname>
+<testname=fcntl10>
+ <description>
+ Basic test for fcntl(2) using F_SETLKW argument.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/fcntl/fcntl10.c
+ <\test_location>
+<\testname>
+<testname=fcntl11>
+ <description>
+ Testcase to check locking of regions of a file
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/fcntl/fcntl11.c
+ <\test_location>
+<\testname>
+<testname=fcntl12>
+ <description>
+ Testcase to test that fcntl() sets EMFILE for F_DUPFD command.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/fcntl/fcntl12.c
+ <\test_location>
+<\testname>
+<testname=fcntl13>
+ <description>
+ Testcase to test that fcntl() sets errno correctly.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/fcntl/fcntl13.c
+ <\test_location>
+<\testname>
+<testname=fcntl14>
+ <description>
+ File locking test cases for fcntl. In Linux, S_ENFMT is not implemented
+ in the kernel. However all standard Unix kernels define S_ENFMT as
+ S_ISGID. So this test defines S_ENFMT as S_ISGID.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/fcntl/fcntl14.c
+ <\test_location>
+<\testname>
+<testname=fcntl15>
+ <description>
+ Check that file locks are removed when file closed
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/fcntl/fcntl15.c
+ <\test_location>
+<\testname>
+<testname=fcntl16>
+ <description>
+ Additional file locking test cases for checking proper notifictaion
+ of processes on lock change
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/fcntl/fcntl16.c
+ <\test_location>
+<\testname>
+<testname=fcntl17>
+ <description>
+ Check deadlock detection for file locking
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/fcntl/fcntl17.c
+ <\test_location>
+<\testname>
+<testname=fcntl18>
+ <description>
+ Test to check the error conditions in fcntl system call
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/fcntl/fcntl18.c
+ <\test_location>
+<\testname>
+<testname=fcntl19>
+ <description>
+ Testcase to check locking of regions of a file
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/fcntl/fcntl19.c
+ <\test_location>
+<\testname>
+<testname=fcntl20>
+ <description>
+ Check locking of regions of a file
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/fcntl/fcntl20.c
+ <\test_location>
+<\testname>
+<testname=fcntl21>
+ <description>
+ Check locking of regions of a file
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/fcntl/fcntl21.c
+ <\test_location>
+<\testname>
+<testname=fdatasync01>
+ <description>
+ Basic test for fdatasync(2).
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/fdatasync/fdatasync01.c
+ <\test_location>
+<\testname>
+<testname=fdatasync02>
+ <description>
+ Checking error conditions for fdatasync(2).
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/fdatasync/fdatasync02.c
+ <\test_location>
+<\testname>
+<testname=flock01>
+ <description>
+ Basic test for flock(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/flock/flock01.c
+ <\test_location>
+<\testname>
+<testname=flock02>
+ <description>
+ Error condition test for flock(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/flock/flock02.c
+ <\test_location>
+<\testname>
+<testname=flock03>
+ <description>
+ Error condition test for flock(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/flock/flock03.c
+ <\test_location>
+<\testname>
+<testname=flock04>
+ <description>
+ Testing different locks on flock(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/flock/flock04.c
+ <\test_location>
+<\testname>
+<testname=flock05>
+ <description>
+ Testing different locks on flock(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/flock/flock05.c
+ <\test_location>
+<\testname>
+<testname=flock06>
+ <description>
+ Error condition test for flock(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/flock/flock06.c
+ <\test_location>
+<\testname>
+<testname=fmtmsg01>
+ <description>
+ Basic test of fmtmsg().
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/fmtmsg/fmtmsg01.c
+ <\test_location>
+<\testname>
+<testname=fork01>
+ <description>
+ Basic test for fork(2).
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/fork/fork01.c
+ <\test_location>
+<\testname>
+<testname=fork02>
+ <description>
+ Test correct operation of fork:
+ pid == 0 in child;
+ pid > 0 in parent from wait;
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/fork/fork02.c
+ <\test_location>
+<\testname>
+<testname=fork03>
+ <description>
+ Check that child can use a large text space and do a large
+ number of operations.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/fork/fork03.c
+ <\test_location>
+<\testname>
+<testname=fork04>
+ <description>
+ Child inheritance of Environment Variables after fork().
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/fork/fork04.c
+ <\test_location>
+<\testname>
+<testname=fork05>
+ <description>
+ Make sure LDT is propagated correctly
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/fork/fork05.c
+ <\test_location>
+<\testname>
+<testname=fork06>
+ <description>
+ Test that a process can fork children a large number of
+ times in succession
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/fork/fork06.c
+ <\test_location>
+<\testname>
+<testname=fork07>
+ <description>
+ Check that all children inherit parent's file descriptor
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/fork/fork07.c
+ <\test_location>
+<\testname>
+<testname=fork08>
+ <description>
+ Check if the parent's file descriptors are affected by
+ actions in the child; they should not be.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/fork/fork08.c
+ <\test_location>
+<\testname>
+<testname=fork09>
+ <description>
+ Check that child has access to a full set of files.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/fork/fork09.c
+ <\test_location>
+<\testname>
+<testname=fork10>
+ <description>
+ Check inheritance of file descriptor by children, they
+ should all be refering to the same file.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/fork/fork10.c
+ <\test_location>
+<\testname>
+<testname=fork11>
+ <description>
+ Test that parent gets a pid from each child when doing wait
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/fork/fork11.c
+ <\test_location>
+<\testname>
+<testname=fork12>
+ <description>
+ Check that all children inherit parent's file descriptor
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/fork/fork12.c
+ <\test_location>
+<\testname>
+<testname=fpathconf>
+ <description>
+ Basic test for fpathconf(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/fpathconf
+ <\test_location>
+<\testname>
+<testname=fstat01>
+ <description>
+ Basic test for fstat(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/fstat/fstat01.c
+ <\test_location>
+<\testname>
+<testname=fstat02>
+ <description>
+ Verify that, fstat(2) succeeds to get the status of a file and fills
+ the stat structure elements though file pointed to by file descriptor
+ not opened for reading.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/fstat/fstat02.c
+ <\test_location>
+<\testname>
+<testname=fstat03>
+ <description>
+ Verify that, fstat(2) returns -1 and sets errno to EBADF if the file
+ pointed to by file descriptor is not valid.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/fstat/fstat03.c
+ <\test_location>
+<\testname>
+<testname=fstat04>
+ <description>
+ Verify that, fstat(2) succeeds to get the status of a file pointed by
+ file descriptor and fills the stat structure elements.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/fstat/fstat04.c
+ <\test_location>
+<\testname>
+<testname=fstat05>
+ <description>
+ Verify that, if buffer points outside user's accessible address space
+ fstat(2) either returns -1 and sets errno to EFAULT or
+ SIGSEGV is returned instead of EFAULT.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/fstat/fstat05.c
+ <\test_location>
+<\testname>
+<testname=fstatfs01>
+ <description>
+ Basic test for fstatfs(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/fstatfs/fstatfs01.c
+ <\test_location>
+<\testname>
+<testname=fstatfs02>
+ <description>
+ Testcase to check fstatfs() sets errno correctly.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/fstatfs/fstatfs02.c
+ <\test_location>
+<\testname>
+<testname=fsync01>
+ <description>
+ Basic test for fsync(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/fsync/fsync01.c
+ <\test_location>
+<\testname>
+<testname=fsync02>
+ <description>
+ Create a sparse file, fsync it, and time the fsync
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/fsync/fsync02.c
+ <\test_location>
+<\testname>
+<testname=fsync03>
+ <description>
+ Testcase to check that fsync(2) sets errno correctly.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/fsync/fsync03.c
+ <\test_location>
+<\testname>
+<testname=ftruncate01>
+ <description>
+ Verify that, ftruncate(2) succeeds to truncate a file to a specified
+ length if the file indicated by file descriptor opened for writing.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/ftruncate/ftruncate01.c
+ <\test_location>
+<\testname>
+<testname=ftruncate02>
+ <description>
+ Verify that, ftruncate(2) succeeds to truncate a file to a certain length,
+ but the attempt to read past the truncated length will fail.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/ftruncate/ftruncate02.c
+ <\test_location>
+<\testname>
+<testname=ftruncate03>
+ <description>
+ Verify that,
+ 1) ftruncate(2) returns -1 and sets errno to EINVAL if the specified
+ truncate length is less than 0.
+ 2) ftruncate(2) returns -1 and sets errno to EBADF if the file descriptor
+ of the specified file is not valid.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/ftruncate/ftruncate03.c
+ <\test_location>
+<\testname>
+<testname=ftruncate04>
+ <description>
+ Test ftruncate/truncate and mandatory record locking.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/ftruncate/ftruncate04.c
+ <\test_location>
+<\testname>
+<testname=getcwd01>
+ <description>
+ Testcase to test that getcwd(2) sets errno correctly.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/getcwd/getcwd01.c
+ <\test_location>
+<\testname>
+<testname=getcwd02>
+ <description>
+ Testcase to check the basic functionality of the getcwd(2) system call.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/getcwd/getcwd02.c
+ <\test_location>
+<\testname>
+<testname=getcwd03>
+ <description>
+ Testcase to check the basic functionality of the getcwd(2) system call
+ for symbolically linked directories.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/getcwd/getcwd03.c
+ <\test_location>
+<\testname>
+<testname=getdents01>
+ <description>
+ get a directory entry
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/getdents/getdents01.c
+ <\test_location>
+<\testname>
+<testname=getdents02>
+ <description>
+ check that we get a failure with a bad file descriptor
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/getdents/getdents02.c
+ <\test_location>
+<\testname>
+<testname=getdents03>
+ <description>
+ check for an EINVAL error
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/getdents/getdents03.c
+ <\test_location>
+<\testname>
+<testname=getdents04>
+ <description>
+ check for an ENOTDIR error
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/getdents/getdents04.c
+ <\test_location>
+<\testname>
+<testname=getdents05>
+ <description>
+ check that we get a failure with a bad dirp address.
+
+ <\description>
+ <test_location>
+ <\test_location>
+<\testname>
+<testname=getdomainname01>
+ <description>
+ Basic test for getdomainname().
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/getdomainname/getdomainname01.c
+ <\test_location>
+<\testname>
+<testname=getegid01>
+ <description>
+ Basic test for getegid(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/getegid/getegid01.c
+ <\test_location>
+<\testname>
+<testname=geteuid01>
+ <description>
+ Basic test for geteuid(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/geteuid/geteuid01.c
+ <\test_location>
+<\testname>
+<testname=getgid01>
+ <description>
+ Basic test for getgid(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/getgid/getgid01.c
+ <\test_location>
+<\testname>
+<testname=getgid02>
+ <description>
+ Testcase to check the basic functionality of getgid().
+
+ <\description>
+ <test_location>
+ <\test_location>
+<\testname>
+<testname=getgid03>
+ <description>
+ Testcase to check the basic functionality of getegid().
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/getgid/getgid03.c
+ <\test_location>
+<\testname>
+<testname=getgroups01>
+ <description>
+ Getgroups system call critical test
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/getgroups/getgroups01.c
+ <\test_location>
+<\testname>
+<testname=getgroups02>
+ <description>
+ Basic test for getgroups(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/getgroups/getgroups02.c
+ <\test_location>
+<\testname>
+<testname=getgroups03>
+ <description>
+ Verify that, getgroups() system call gets the supplementary group IDs
+ of the calling process.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/getgroups/getgroups03.c
+ <\test_location>
+<\testname>
+<testname=getgroups04>
+ <description>
+ Verify that,
+ getgroups() fails with -1 and sets errno to EINVAL if the size
+ argument value is -ve.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/getgroups/getgroups04.c
+ <\test_location>
+<\testname>
+<testname=gethostid01>
+ <description>
+ Basic test for gethostid(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/gethostid/gethostid01.c
+ <\test_location>
+<\testname>
+<testname=gethostname01>
+ <description>
+ Basic test for gethostname(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/gethostname/gethostname01.c
+ <\test_location>
+<\testname>
+<testname=getitimer01>
+ <description>
+ Check that a correct call to getitimer() succeeds
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/getitimer/getitimer01.c
+ <\test_location>
+<\testname>
+<testname=getitimer02>
+ <description>
+ Check that a getitimer() call fails as expected
+ with an incorrect second argument.
+ getitimer03
+
+ Check that a getitimer() call fails as expected
+ with an incorrect first argument.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/getitimer/getitimer02.c
+ <\test_location>
+<\testname>
+<testname=getpeername01>
+ <description>
+ Verify that getpeername() returns the proper errno for various failure cases
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/getpeername/getpeername01.c
+ <\test_location>
+<\testname>
+<testname=getpgid01>
+ <description>
+ Testcase to check the basic functionality of getpgid().
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/getpgid/getpgid01.c
+ <\test_location>
+<\testname>
+<testname=getpgid02>
+ <description>
+ Testcase to check the basic functionality of getpgid().
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/getpgid/getpgid02.c
+ <\test_location>
+<\testname>
+<testname=getpgrp01>
+ <description>
+ Basic test for getpgrp(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/getpgrp/getpgrp01.c
+ <\test_location>
+<\testname>
+<testname=getpid01>
+ <description>
+ Basic test for getpid(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/getpid/getpid01.c
+ <\test_location>
+<\testname>
+<testname=getpid02>
+ <description>
+ Verify that getpid() system call gets the process ID of the of the
+ calling process.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/getpid/getpid02.c
+ <\test_location>
+<\testname>
+<testname=getppid01>
+ <description>
+ Testcase to check the basic functionality of the getppid() syscall.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/getppid/getppid01.c
+ <\test_location>
+<\testname>
+<testname=getpriority01>
+ <description>
+ Verify that getpriority() succeeds get the scheduling priority of
+ the current process, process group or user.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/getpriority/getpriority01.c
+ <\test_location>
+<\testname>
+<testname=getpriority02>
+ <description>
+ Verify that,
+ 1) getpriority() sets errno to ESRCH if no process was located
+ was located for 'which' and 'who' arguments.
+ 2) getpriority() sets errno to EINVAL if 'which' argument was
+ not one of PRIO_PROCESS, PRIO_PGRP, or PRIO_USER.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/getpriority/getpriority02.c
+ <\test_location>
+<\testname>
+<testname=getresgid01>
+ <description>
+ Verify that getresgid() will be successful to get the real, effective
+ and saved user id of the calling process.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/getresgid/getresgid01.c
+ <\test_location>
+<\testname>
+<testname=getresgid02>
+ <description>
+ Verify that getresgid() will be successful to get the real, effective
+ and saved user ids after calling process invokes setregid() to change
+ the effective/saved gids to that of specified user.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/getresgid/getresgid02.c
+ <\test_location>
+<\testname>
+<testname=getresgid03>
+ <description>
+ Verify that getresgid() will be successful to get the real, effective
+ and saved user ids after calling process invokes setresgid() to change
+ the effective gid to that of specified user.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/getresgid/getresgid03.c
+ <\test_location>
+<\testname>
+<testname=getresuid01>
+ <description>
+ Verify that getresuid() will be successful to get the real, effective
+ and saved user id of the calling process.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/getresuid/getresuid01.c
+ <\test_location>
+<\testname>
+<testname=getresuid02>
+ <description>
+ Verify that getresuid() will be successful to get the real, effective
+ and saved user ids after calling process invokes setreuid() to change
+ the effective/saved uids to that of specified user.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/getresuid/getresuid02.c
+ <\test_location>
+<\testname>
+<testname=getresuid03>
+ <description>
+ Verify that getresuid() will be successful to get the real, effective
+ and saved user ids after calling process invokes setresuid() to change
+ the effective uid to that of specified user.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/getresuid/getresuid03.c
+ <\test_location>
+<\testname>
+<testname=getsid01>
+ <description>
+ call getsid() and make sure it succeeds
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/getsid/getsid01.c
+ <\test_location>
+<\testname>
+<testname=getsid02>
+ <description>
+ call getsid() with an invalid PID to produce a failure
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/getsid/getsid02.c
+ <\test_location>
+<\testname>
+<testname=getsockname01>
+ <description>
+ Verify that getsockname() returns the proper errno for various failure cases
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/getsockname/getsockname01.c
+ <\test_location>
+<\testname>
+<testname=getsockopt01>
+ <description>
+ Verify that getsockopt() returns the proper errno for various failure cases
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/getsockopt/getsockopt01.c
+ <\test_location>
+<\testname>
+<testname=gettimeofday01>
+ <description>
+ Testcase to check that gettimeofday(2) sets errno to EFAULT.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/gettimeofday/gettimeofday01.c
+ <\test_location>
+<\testname>
+<testname=gettimeofday02>
+ <description>
+ Testcase to check if gettimeofday is monotonous.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/gettimeofday/gettimeofday02.c
+ <\test_location>
+<\testname>
+<testname=getuid01>
+ <description>
+ Basic test for getuid(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/getuid/getuid01.c
+ <\test_location>
+<\testname>
+<testname=getuid02>
+ <description>
+ Testcase to check the basic functionality of the geteuid() system call.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/getuid/getuid02.c
+ <\test_location>
+<\testname>
+<testname=getuid03>
+ <description>
+ Testcase to check the basic functionality of the getuid() system call.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/getuid/getuid03.c
+ <\test_location>
+<\testname>
+<testname=ioctl01>
+ <description>
+ Testcase to check the errnos set by the ioctl(2) system call.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/ioctl/ioctl01.c
+ <\test_location>
+<\testname>
+<testname=ioctl02>
+ <description>
+ Testcase to test the TCGETA, and TCSETA ioctl implementations for
+ the tty driver
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/ioctl/ioctl02.c
+ <\test_location>
+<\testname>
+<testname=ioperm01>
+ <description>
+ Basic test for ioperm().
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/ioperm/ioperm01.c
+ <\test_location>
+<\testname>
+<testname=ioperm02>
+ <description>
+ Test for error conditions.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/ioperm/ioperm02.c
+ <\test_location>
+<\testname>
+<testname=iopl01>
+ <description>
+ Basic test for iopl().
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/iopl/iopl01.c
+ <\test_location>
+<\testname>
+<testname=iopl02>
+ <description>
+ Test for error conditions.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/iopl/iopl02.c
+ <\test_location>
+<\testname>
+<testname=msgctl01>
+ <description>
+ create a message queue, then issue the IPC_STAT command
+ and RMID commands to test the functionality
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/ipc/msgctl/msgctl01.c
+ <\test_location>
+<\testname>
+<testname=msgctl02>
+ <description>
+ create a message queue, then issue the IPC_SET command
+ to lower the msg_qbytes value.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/ipc/msgctl/msgctl02.c
+ <\test_location>
+<\testname>
+<testname=msgctl03>
+ <description>
+ create a message queue, then issue the IPC_RMID command
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/ipc/msgctl/msgctl03.c
+ <\test_location>
+<\testname>
+<testname=msgctl04>
+ <description>
+ test for EACCES, EFAULT and EINVAL errors using
+ a variety of incorrect calls.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/ipc/msgctl/msgctl04.c
+ <\test_location>
+<\testname>
+<testname=msgctl05>
+ <description>
+ test for EPERM error
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/ipc/msgctl/msgctl05.c
+ <\test_location>
+<\testname>
+<testname=msgget01>
+ <description>
+ create a message queue, write a message to it and
+ read it back.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/ipc/msgget/msgget01.c
+ <\test_location>
+<\testname>
+<testname=msgget02>
+ <description>
+ test for EEXIST and ENOENT errors
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/ipc/msgget/msgget02.c
+ <\test_location>
+<\testname>
+<testname=msgget03>
+ <description>
+ test for an ENOSPC error by using up all available
+ message queues.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/ipc/msgget/msgget03.c
+ <\test_location>
+<\testname>
+<testname=msgget04>
+ <description>
+ test for an EACCES error by creating a message queue
+ with no read or write permission and then attempting
+ to access it with various permissions.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/ipc/msgget/msgget04.c
+ <\test_location>
+<\testname>
+<testname=msgrcv01>
+ <description>
+ test that msgrcv() receives the expected message
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/ipc/msgrcv/msgrcv01.c
+ <\test_location>
+<\testname>
+<testname=msgrcv02>
+ <description>
+ test for EACCES and EFAULT errors
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/ipc/msgrcv/msgrcv02.c
+ <\test_location>
+<\testname>
+<testname=msgrcv03>
+ <description>
+ test for EINVAL error
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/ipc/msgrcv/msgrcv03.c
+ <\test_location>
+<\testname>
+<testname=msgrcv04>
+ <description>
+ test for E2BIG and ENOMSG errors
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/ipc/msgrcv/msgrcv04.c
+ <\test_location>
+<\testname>
+<testname=msgrcv05>
+ <description>
+ test for EINTR error
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/ipc/msgrcv/msgrcv05.c
+ <\test_location>
+<\testname>
+<testname=msgrcv06>
+ <description>
+ test for EIDRM error
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/ipc/msgrcv/msgrcv06.c
+ <\test_location>
+<\testname>
+<testname=msgsnd01>
+ <description>
+ test that msgsnd() enqueues a message correctly
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/ipc/msgsnd/msgsnd01.c
+ <\test_location>
+<\testname>
+<testname=msgsnd02>
+ <description>
+ test for EACCES and EFAULT errors
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/ipc/msgsnd/msgsnd02.c
+ <\test_location>
+<\testname>
+<testname=msgsnd03>
+ <description>
+ test for EINVAL error
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/ipc/msgsnd/msgsnd03.c
+ <\test_location>
+<\testname>
+<testname=msgsnd04>
+ <description>
+ test for EAGAIN error
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/ipc/msgsnd/msgsnd04.c
+ <\test_location>
+<\testname>
+<testname=msgsnd05>
+ <description>
+ test for EINTR error
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/ipc/msgsnd/msgsnd05.c
+ <\test_location>
+<\testname>
+<testname=msgsnd06>
+ <description>
+ test for EIDRM error
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/ipc/msgsnd/msgsnd06.c
+ <\test_location>
+<\testname>
+<testname=semctl01>
+ <description>
+ test the 10 possible semctl() commands
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/ipc/semctl/semctl01.c
+ <\test_location>
+<\testname>
+<testname=semctl02>
+ <description>
+ test for EACCES error
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/ipc/semctl/semctl02.c
+ <\test_location>
+<\testname>
+<testname=semctl03>
+ <description>
+ test for EINVAL and EFAULT errors
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/ipc/semctl/semctl03.c
+ <\test_location>
+<\testname>
+<testname=semctl04>
+ <description>
+ test for EPERM error
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/ipc/semctl/semctl04.c
+ <\test_location>
+<\testname>
+<testname=semctl05>
+ <description>
+ test for ERANGE error
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/ipc/semctl/semctl05.c
+ <\test_location>
+<\testname>
+<testname=semget01>
+ <description>
+ test that semget() correclty creates a semaphore set
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/ipc/semget/semget01.c
+ <\test_location>
+<\testname>
+<testname=semget02>
+ <description>
+ test for EACCES and EEXIST errors
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/ipc/semget/semget02.c
+ <\test_location>
+<\testname>
+<testname=semget03>
+ <description>
+ test for ENOENT error
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/ipc/semget/semget03.c
+ <\test_location>
+<\testname>
+<testname=semget05>
+ <description>
+ test for ENOSPC error
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/ipc/semget/semget05.c
+ <\test_location>
+<\testname>
+<testname=semget06>
+ <description>
+ test for EINVAL error
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/ipc/semget/semget06.c
+ <\test_location>
+<\testname>
+<testname=semop01>
+ <description>
+ test that semop() basic functionality is correct
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/ipc/semop/semop01.c
+ <\test_location>
+<\testname>
+<testname=semop02>
+ <description>
+ test for E2BIG, EACCES, EFAULT and EINVAL errors
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/ipc/semop/semop02.c
+ <\test_location>
+<\testname>
+<testname=semop03>
+ <description>
+ test for EFBIG error
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/ipc/semop/semop03.c
+ <\test_location>
+<\testname>
+<testname=semop04>
+ <description>
+ test for EAGAIN error
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/ipc/semop/semop04.c
+ <\test_location>
+<\testname>
+<testname=semop05>
+ <description>
+ test for EINTR and EIDRM errors
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/ipc/semop/semop05.c
+ <\test_location>
+<\testname>
+<testname=shmat01>
+ <description>
+ test that shmat() works correctly
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/ipc/shmat/shmat01.c
+ <\test_location>
+<\testname>
+<testname=shmat02>
+ <description>
+ check for EINVAL and EACCES errors
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/ipc/shmat/shmat02.c
+ <\test_location>
+<\testname>
+<testname=shmat03>
+ <description>
+ test for EACCES error
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/ipc/shmat/shmat03.c
+ <\test_location>
+<\testname>
+<testname=shmctl01>
+ <description>
+ test the IPC_STAT, IPC_SET and IPC_RMID commands as
+ they are used with shmctl()
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/ipc/shmctl/shmctl01.c
+ <\test_location>
+<\testname>
+<testname=shmctl02>
+ <description>
+ check for EACCES, EFAULT and EINVAL errors
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/ipc/shmctl/shmctl02.c
+ <\test_location>
+<\testname>
+<testname=shmctl03>
+ <description>
+ check for EACCES, and EPERM errors
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/ipc/shmctl/shmctl03.c
+ <\test_location>
+<\testname>
+<testname=shmdt01>
+ <description>
+ check that shared memory is detached correctly
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/ipc/shmdt/shmdt01.c
+ <\test_location>
+<\testname>
+<testname=shmdt02>
+ <description>
+ check for EINVAL error
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/ipc/shmdt/shmdt02.c
+ <\test_location>
+<\testname>
+<testname=shmget01>
+ <description>
+ test that shmget() correctly creates a shared memory segment
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/ipc/shmget/shmget01.c
+ <\test_location>
+<\testname>
+<testname=shmget02>
+ <description>
+ check for ENOENT, EEXIST and EINVAL errors
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/ipc/shmget/shmget02.c
+ <\test_location>
+<\testname>
+<testname=shmget03>
+ <description>
+ test for ENOSPC error
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/ipc/shmget/shmget03.c
+ <\test_location>
+<\testname>
+<testname=shmget04>
+ <description>
+ test for EACCES error
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/ipc/shmget/shmget04.c
+ <\test_location>
+<\testname>
+<testname=shmget05>
+ <description>
+ test for EACCES error
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/ipc/shmget/shmget05.c
+ <\test_location>
+<\testname>
+<testname=kill01>
+ <description>
+ Test case to check the basic functionality of kill().
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/kill/kill01.c
+ <\test_location>
+<\testname>
+<testname=kill02>
+ <description>
+ Sending a signal to processes with the same process group ID
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/kill/kill02.c
+ <\test_location>
+<\testname>
+<testname=kill03>
+ <description>
+ Test case to check that kill fails when given an invalid signal.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/kill/kill03.c
+ <\test_location>
+<\testname>
+<testname=kill04>
+ <description>
+ Test case to check that kill() fails when passed a non-existant pid.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/kill/kill04.c
+ <\test_location>
+<\testname>
+<testname=kill05>
+ <description>
+ Test case to check that kill() fails when passed a pid owned by another
+ user.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/kill/kill05.c
+ <\test_location>
+<\testname>
+<testname=kill06>
+ <description>
+ Test case to check the basic functionality of kill() when killing an
+ entire process group with a negative pid.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/kill/kill06.c
+ <\test_location>
+<\testname>
+<testname=kill07>
+ <description>
+ Test case to check that SIGKILL can not be caught.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/kill/kill07.c
+ <\test_location>
+<\testname>
+<testname=kill08>
+ <description>
+ Test case to check the basic functionality of kill() when kill an
+ entire process group.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/kill/kill08.c
+ <\test_location>
+<\testname>
+<testname=kill09>
+ <description>
+ Basic test for kill(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/kill/kill09.c
+ <\test_location>
+<\testname>
+<testname=kill10>
+ <description>
+ Signal flooding test.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/kill/kill10.c
+ <\test_location>
+<\testname>
+<testname=kill11>
+ <description>
+ Check that when a child is killed by its parent, it returns the
+ correct values to the waiting parent--child has default values.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/kill/kill11.c
+ <\test_location>
+<\testname>
+<testname=kill12>
+ <description>
+ Check that when a child is killed by its parent, it returns the
+ correct values to the waiting parent--the child sets signal to
+ ignore the kill.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/kill/kill12.c
+ <\test_location>
+<\testname>
+<testname=lchown01>
+ <description>
+ Verify that, lchown(2) succeeds to change the owner and group of a file
+ specified by path to any numeric owner(uid)/group(gid) values when invoked
+ by super-user.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/lchown/lchown01.c
+ <\test_location>
+<\testname>
+<testname=lchown02>
+ <description>
+ Verify that,
+ 1) lchown(2) returns -1 and sets errno to EPERM if the effective user id
+ of process does not match the owner of the file and the process is
+ not super user.
+ 2) lchown(2) returns -1 and sets errno to EACCES if search permission is
+ denied on a component of the path prefix.
+ 3) lchown(2) returns -1 and sets errno to EFAULT if pathname points
+ outside user's accessible address space.
+ 4) lchown(2) returns -1 and sets errno to ENAMETOOLONG if the pathname
+ component is too long.
+ 5) lchown(2) returns -1 and sets errno to ENOTDIR if the directory
+ component in pathname is not a directory.
+ 6) lchown(2) returns -1 and sets errno to ENOENT if the specified file
+ does not exists.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/lchown/lchown02.c
+ <\test_location>
+<\testname>
+<testname=link02>
+ <description>
+ Basic test for link(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/link/link02.c
+ <\test_location>
+<\testname>
+<testname=link03>
+ <description>
+ Multi links tests
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/link/link03.c
+ <\test_location>
+<\testname>
+<testname=link04>
+ <description>
+ Negative test cases for link(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/link/link04.c
+ <\test_location>
+<\testname>
+<testname=link05>
+ <description>
+ Multi links (EMLINK) negative test
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/link/link05.c
+ <\test_location>
+<\testname>
+<testname=listen01>
+ <description>
+ Verify that listen() returns the proper errno for various failure cases
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/listen/listen01.c
+ <\test_location>
+<\testname>
+<testname=llseek01>
+ <description>
+ Verify that, llseek() call succeeds to set the file pointer position
+ to an offset larger than file size. Also, verify that any attempt
+ to write to this location fails.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/llseek/llseek01.c
+ <\test_location>
+<\testname>
+<testname=llseek02>
+ <description>
+ Verify that,
+ 1. llseek() returns -1 and sets errno to EINVAL, if the 'Whence' argument
+ is not a proper value.
+ 2. llseek() returns -1 and sets errno to EBADF, if the file handle of
+ the specified file is not valid.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/llseek/llseek02.c
+ <\test_location>
+<\testname>
+<testname=lseek01>
+ <description>
+ Basic test for lseek(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/lseek/lseek01.c
+ <\test_location>
+<\testname>
+<testname=lseek02>
+ <description>
+ Negative test for lseek(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/lseek/lseek02.c
+ <\test_location>
+<\testname>
+<testname=lseek03>
+ <description>
+ Negative test for lseek(2) whence
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/lseek/lseek03.c
+ <\test_location>
+<\testname>
+<testname=lseek04>
+ <description>
+ Negative test for lseek(2) of a fifo
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/lseek/lseek04.c
+ <\test_location>
+<\testname>
+<testname=lseek05>
+ <description>
+ Negative test for lseek(2) of a pipe
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/lseek/lseek05.c
+ <\test_location>
+<\testname>
+<testname=lseek06>
+ <description>
+ Verify that, lseek() call succeeds to set the file pointer position
+ to less than or equal to the file size, when a file is opened for
+ read or write.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/lseek/lseek06.c
+ <\test_location>
+<\testname>
+<testname=lseek07>
+ <description>
+ Verify that, lseek() call succeeds to set the file pointer position
+ to more than the file size, when a file is opened for reading/writing.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/lseek/lseek07.c
+ <\test_location>
+<\testname>
+<testname=lseek08>
+ <description>
+ Verify that, lseek() call succeeds to set the file pointer position
+ to the end of the file when 'whence' value set to SEEK_END and any
+ attempts to read from that position should fail.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/lseek/lseek08.c
+ <\test_location>
+<\testname>
+<testname=lseek09>
+ <description>
+ Verify that, lseek() call succeeds to set the file pointer position
+ to the current specified location, when 'whence' value is set to
+ SEEK_CUR and the data read from the specified location should match
+ the expected data.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/lseek/lseek09.c
+ <\test_location>
+<\testname>
+<testname=lseek10>
+ <description>
+ Verify that,
+ 1. lseek() returns -1 and sets errno to ESPIPE, if the file handle of
+ the specified file is associated with a pipe, socket, or FIFO.
+ 2. lseek() returns -1 and sets errno to EINVAL, if the 'Whence' argument
+ is not a proper value.
+ 3. lseek() returns -1 and sets errno to EBADF, if the file handle of
+ the specified file is not valid.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/lseek/lseek10.c
+ <\test_location>
+<\testname>
+<testname=lstat01>
+ <description>
+ Verify that, lstat(2) succeeds to get the status of a file pointed to by
+ symlink and fills the stat structure elements.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/lstat/lstat01.c
+ <\test_location>
+<\testname>
+<testname=lstat02>
+ <description>
+ Basic test for lstat(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/lstat/lstat02.c
+ <\test_location>
+<\testname>
+<testname=lstat03>
+ <description>
+ Verify that,
+ 1) lstat(2) returns -1 and sets errno to EACCES if search permission is
+ denied on a component of the path prefix.
+ 2) lstat(2) returns -1 and sets errno to ENOENT if the specified file
+ does not exists or empty string.
+ 3) lstat(2) returns -1 and sets errno to EFAULT if pathname points
+ outside user's accessible address space.
+ 4) lstat(2) returns -1 and sets errno to ENAMETOOLONG if the pathname
+ component is too long.
+ 5) lstat(2) returns -1 and sets errno to ENOTDIR if the directory
+ component in pathname is not a directory.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/lstat/lstat03.c
+ <\test_location>
+<\testname>
+<testname=mallopt>
+ <description>
+ Test basic functionality of mallopt().
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/mallopt
+ <\test_location>
+<\testname>
+<testname=memcmp>
+ <description>
+ Test basic functionality of memcmp().
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/memcmp
+ <\test_location>
+<\testname>
+<testname=memcpy>
+ <description>
+ Test basic functionality of memcpy().
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/memcpy
+ <\test_location>
+<\testname>
+<testname=memset>
+ <description>
+ Test basic functionality of memset().
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/memset
+ <\test_location>
+<\testname>
+<testname=mkdir01>
+ <description>
+ Basic errno test for mkdir(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/mkdir/mkdir01.c
+ <\test_location>
+<\testname>
+<testname=mkdir02>
+ <description>
+ This test will verify that new directory created
+ by mkdir(2) inherites the group ID from the parent
+ directory and S_ISGID bit, if the S_ISGID bit is set
+ in the parent directory.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/mkdir/mkdir02.c
+ <\test_location>
+<\testname>
+<testname=mkdir03>
+ <description>
+ Check mkdir() with various error conditions that should produce
+ EFAULT, ENAMETOOLONG, EEXIST, ENOENT and ENOTDIR
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/mkdir/mkdir03.c
+ <\test_location>
+<\testname>
+<testname=mkdir04>
+ <description>
+ Attempt to create a directory in a directory having no permissions.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/mkdir/mkdir04.c
+ <\test_location>
+<\testname>
+<testname=mkdir05>
+ <description>
+ This test will verify the mkdir(2) syscall basic functionality
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/mkdir/mkdir05.c
+ <\test_location>
+<\testname>
+<testname=mkdir08>
+ <description>
+ Basic test for mkdir(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/mkdir/mkdir08.c
+ <\test_location>
+<\testname>
+<testname=mknod01>
+ <description>
+ Basic test for mknod(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/mknod/mknod01.c
+ <\test_location>
+<\testname>
+<testname=mknod02>
+ <description>
+ Verify that mknod(2) succeeds when used to create a filesystem
+ node with set group-ID bit set on a directory without set group-ID bit set.
+ The node created should have set group-ID bit set and its gid should be
+ equal to that of its parent directory.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/mknod/mknod02.c
+ <\test_location>
+<\testname>
+<testname=mknod03>
+ <description>
+ Verify that mknod(2) succeeds when used to create a filesystem
+ node with set group-ID bit set on a directory with set group-ID bit set.
+ The node created should have set group-ID bit set and its gid should be
+ equal to the effective gid of the process.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/mknod/mknod03.c
+ <\test_location>
+<\testname>
+<testname=mknod04>
+ <description>
+ Verify that mknod(2) succeeds when used to create a filesystem
+ node on a directory with set group-ID bit set.
+ The node created should not have group-ID bit set and its gid should be
+ equal to the effective gid of the process.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/mknod/mknod04.c
+ <\test_location>
+<\testname>
+<testname=mknod05>
+ <description>
+ Verify that mknod(2) succeeds when used by root to create a filesystem
+ node with set group-ID bit set on a directory with set group-ID bit set.
+ The node created should have set group-ID bit set and its gid should be
+ equal to that of its parent directory.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/mknod/mknod05.c
+ <\test_location>
+<\testname>
+<testname=mknod06>
+ <description>
+ Verify that,
+ 1) mknod(2) returns -1 and sets errno to EEXIST if specified path
+ already exists.
+ 2) mknod(2) returns -1 and sets errno to EFAULT if pathname points
+ outside user's accessible address space.
+ 3) mknod(2) returns -1 and sets errno to ENOENT if the directory
+ component in pathname does not exist.
+ 4) mknod(2) returns -1 and sets errno to ENAMETOOLONG if the pathname
+ component was too long.
+ 5) mknod(2) returns -1 and sets errno to ENOTDIR if the directory
+ component in pathname is not a directory.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/mknod/mknod06.c
+ <\test_location>
+<\testname>
+<testname=mknod07>
+ <description>
+ Verify that,
+ 1) mknod(2) returns -1 and sets errno to EPERM if the process id of
+ the caller is not super-user.
+ 2) mknod(2) returns -1 and sets errno to EACCES if parent directory
+ does not allow write permission to the process.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/mknod/mknod07.c
+ <\test_location>
+<\testname>
+<testname=mknod08>
+ <description>
+ Verify that mknod(2) succeeds when used to create a filesystem
+ node on a directory without set group-ID bit set. The node created
+ should not have set group-ID bit set and its gid should be equal to that
+ of its parent directory.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/mknod/mknod08.c
+ <\test_location>
+<\testname>
+<testname=mlock01>
+ <description>
+ Test basic functionality of mlock().
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/mlock/mlock01.c
+ <\test_location>
+<\testname>
+<testname=mlock02>
+ <description>
+ Test to see the proper errors are returned by mlock().
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/mlock/mlock02.c
+ <\test_location>
+<\testname>
+<testname=mlockall01>
+ <description>
+ Test basic functionality of mlockall().
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/mlockall/mlockall01.c
+ <\test_location>
+<\testname>
+<testname=mlockall02>
+ <description>
+ Test to see the proper errors are returned by mlockall().
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/mlockall/mlockall02.c
+ <\test_location>
+<\testname>
+<testname=mmap001>
+ <description>
+ Tests mmapping a big file and writing it once
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/mmap/mmap001.c
+ <\test_location>
+<\testname>
+<testname=mmap01>
+ <description>
+ Verify that, mmap() succeeds when used to map a file where size of the
+ file is not a multiple of the page size, the memory area beyond the end
+ of the file to the end of the page is accessible. Also, verify that
+ this area is all zeroed and the modifications done to this area are
+ not written to the file.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/mmap/mmap01.c
+ <\test_location>
+<\testname>
+<testname=mmap02>
+ <description>
+ Call mmap() with prot parameter set to PROT_READ and with the file
+ descriptor being open for read, to map a file creating mapped memory
+ with read access. The minimum file permissions should be 0444.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/mmap/mmap02.c
+ <\test_location>
+<\testname>
+<testname=mmap03>
+ <description>
+ Call mmap() to map a file creating a mapped region with execute access
+ under the following conditions -
+ - The prot parameter is set to PROT_EXE
+ - The file descriptor is open for read
+ - The file being mapped has execute permission bit set.
+ - The minimum file permissions should be 0555.
+
+ The call should succeed to map the file creating mapped memory with the
+ required attributes.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/mmap/mmap03.c
+ <\test_location>
+<\testname>
+<testname=mmap04>
+ <description>
+ Call mmap() to map a file creating a mapped region with read/exec access
+ under the following conditions -
+ - The prot parameter is set to PROT_READ|PROT_EXEC
+ - The file descriptor is open for read
+ - The file being mapped has read and execute permission bit set.
+ - The minimum file permissions should be 0555.
+
+ The call should succeed to map the file creating mapped memory with the
+ required attributes.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/mmap/mmap04.c
+ <\test_location>
+<\testname>
+<testname=mmap05>
+ <description>
+ Call mmap() to map a file creating mapped memory with no access under
+ the following conditions -
+ - The prot parameter is set to PROT_NONE
+ - The file descriptor is open for read(any mode other than write)
+ - The minimum file permissions should be 0444.
+
+ The call should succeed to map the file creating mapped memory with the
+ required attributes.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/mmap/mmap05.c
+ <\test_location>
+<\testname>
+<testname=mmap06>
+ <description>
+ Call mmap() to map a file creating a mapped region with read access
+ under the following conditions -
+ - The prot parameter is set to PROT_READ
+ - The file descriptor is open for writing.
+
+ The call should fail to map the file.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/mmap/mmap06.c
+ <\test_location>
+<\testname>
+<testname=mmap07>
+ <description>
+ Call mmap() to map a file creating a mapped region with read access
+ under the following conditions -
+ - The prot parameter is set to PROT_WRITE
+ - The file descriptor is open for writing.
+ - The flags parameter has MAP_PRIVATE set.
+
+ The call should fail to map the file.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/mmap/mmap07.c
+ <\test_location>
+<\testname>
+<testname=mmap08>
+ <description>
+ Verify that mmap() fails to map a file creating a mapped region
+ when the file specified by file descriptor is not valid.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/mmap/mmap08.c
+ <\test_location>
+<\testname>
+<testname=mmap09>
+ <description>
+ Verify that truncating a mmaped file works correctly.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/mmap/mmap09.c
+ <\test_location>
+<\testname>
+<testname=modify_ldt01>
+ <description>
+ Testcase to check the error conditions for modify_ldt(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/modify_ldt/modify_ldt01.c
+ <\test_location>
+<\testname>
+<testname=modify_ldt02>
+ <description>
+ Testcase to check the error conditions for modify_ldt(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/modify_ldt/modify_ldt02.c
+ <\test_location>
+<\testname>
+<testname=mount01>
+ <description>
+ Basic test for mount(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/mount/mount01.c
+ <\test_location>
+<\testname>
+<testname=mount02>
+ <description>
+ Test for checking basic error conditions for mount(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/mount/mount02.c
+ <\test_location>
+<\testname>
+<testname=mount03>
+ <description>
+ Test for checking mount(2) flags
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/mount/mount03.c
+ <\test_location>
+<\testname>
+<testname=mount04>
+ <description>
+ Test for checking EPERM
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/mount/mount04.c
+ <\test_location>
+<\testname>
+<testname=mprotect01>
+ <description>
+ Testcase to check the error conditions for mprotect(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/mprotect/mprotect01.c
+ <\test_location>
+<\testname>
+<testname=mprotect02>
+ <description>
+ Testcase to check the mprotect(2) system call.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/mprotect/mprotect02.c
+ <\test_location>
+<\testname>
+<testname=mprotect03>
+ <description>
+ Testcase to check the mprotect(2) system call.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/mprotect/mprotect03.c
+ <\test_location>
+<\testname>
+<testname=mremap01>
+ <description>
+ Verify that, mremap() succeeds when used to expand the existing
+ virtual memory mapped region to the requested size where the
+ virtual memory area was previously mapped to a file using mmap().
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/mremap/mremap01.c
+ <\test_location>
+<\testname>
+<testname=mremap02>
+ <description>
+ Verify that,
+ mremap() fails when used to expand the existing virtual memory mapped
+ region to the requested size, if the virtual memory area previously
+ mapped was not page aligned or invalid argument specified.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/mremap/mremap02.c
+ <\test_location>
+<\testname>
+<testname=mremap03>
+ <description>
+ Verify that,
+ mremap() fails when used to expand the existing virtual memory mapped
+ region to the requested size, if there already exists mappings that
+ cover the whole address space requsted or the old address specified was
+ not mapped.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/mremap/mremap03.c
+ <\test_location>
+<\testname>
+<testname=mremap04>
+ <description>
+ Verify that,
+ mremap() fails when used to expand the existing virtual memory mapped
+ region to the requested size, if the memory area cannot be expanded at
+ the current virtual address and MREMAP_MAYMOVE flag not set.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/mremap/mremap04.c
+ <\test_location>
+<\testname>
+<testname=msync01>
+ <description>
+ Verify that, msync() succeeds, when the region to synchronize, is part
+ of, or all of a mapped region.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/msync/msync01.c
+ <\test_location>
+<\testname>
+<testname=msync02>
+ <description>
+ Verify that msync() succeeds when the region to synchronize is mapped
+ shared and the flags argument is MS_INVALIDATE.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/msync/msync02.c
+ <\test_location>
+<\testname>
+<testname=msync03>
+ <description>
+ Verify that, msync() fails, when the region to synchronize, is outside
+ the address space of the process.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/msync/msync03.c
+ <\test_location>
+<\testname>
+<testname=msync04>
+ <description>
+ Verify that, msync() fails, when the region to synchronize, is mapped
+ but the flags argument is invalid.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/msync/msync04.c
+ <\test_location>
+<\testname>
+<testname=msync05>
+ <description>
+ Verify that, msync() fails, when the region to synchronize, was not
+ mapped.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/msync/msync05.c
+ <\test_location>
+<\testname>
+<testname=munmap01>
+ <description>
+ Verify that, munmap call will succeed to unmap a mapped file or
+ anonymous shared memory region from the calling process's address space
+ and after successful completion of munmap, the unmapped region is no
+ longer accessible.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/munmap/munmap01.c
+ <\test_location>
+<\testname>
+<testname=munmap02>
+ <description>
+ Verify that, munmap call will succeed to unmap a mapped file or
+ anonymous shared memory region from the calling process's address space
+ if the region specified by the address and the length is part or all of
+ the mapped region.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/munmap/munmap02.c
+ <\test_location>
+<\testname>
+<testname=munmap03>
+ <description>
+ Verify that, munmap call will fail to unmap a mapped file or anonymous
+ shared memory region from the calling process's address space if the
+ address and the length of the region to be unmapped points outside the
+ calling process's address space
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/munmap/munmap03.c
+ <\test_location>
+<\testname>
+<testname=nanosleep01>
+ <description>
+ Verify that nanosleep() will be successful to suspend the execution
+ of a process for a specified time.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/nanosleep/nanosleep01.c
+ <\test_location>
+<\testname>
+<testname=nanosleep02>
+ <description>
+ Verify that nanosleep() will be successful to suspend the execution
+ of a process, returns after the receipt of a signal and writes the
+ remaining sleep time into the structure.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/nanosleep/nanosleep02.c
+ <\test_location>
+<\testname>
+<testname=nanosleep03>
+ <description>
+ Verify that nanosleep() will fail to suspend the execution
+ of a process for a specified time if interrupted by a non-blocked signal.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/nanosleep/nanosleep03.c
+ <\test_location>
+<\testname>
+<testname=nanosleep04>
+ <description>
+ Verify that nanosleep() will fail to suspend the execution
+ of a process if the specified pause time is invalid.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/nanosleep/nanosleep04.c
+ <\test_location>
+<\testname>
+<testname=nftw>
+ <description>
+ Basic test of nftw().
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/nftw/nftw.c
+ <\test_location>
+<\testname>
+<testname=nftw64>
+ <description>
+ Basic test of nftw64()
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/nftw/nftw64.c
+ <\test_location>
+<\testname>
+<testname=nice01>
+ <description>
+ Verify that root can provide a negative value to nice()
+ and hence root can decrease the nice value of the process
+ using nice() system call
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/nice/nice01.c
+ <\test_location>
+<\testname>
+<testname=nice02>
+ <description>
+ Verify that any user can successfully increase the nice value of
+ the process by passing a higher increment value (> max. applicable limits)
+ to nice() system call.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/nice/nice02.c
+ <\test_location>
+<\testname>
+<testname=nice03>
+ <description>
+ Verify that any user can successfully increase the nice value of
+ the process by passing an increment value (< max. applicable limits) to
+ nice() system call.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/nice/nice03.c
+ <\test_location>
+<\testname>
+<testname=nice04>
+ <description>
+ Verify that, nice(2) fails when, a non-root user attempts to increase
+ the priority of a process by specifying a negative increment value.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/nice/nice04.c
+ <\test_location>
+<\testname>
+<testname=nice05>
+ <description>
+ Basic test for nice(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/nice/nice05.c
+ <\test_location>
+<\testname>
+<testname=open01>
+ <description>
+ Open a file with oflag = O_CREAT set, does it set the sticky bit off?
+
+ Open "/tmp" with O_DIRECTORY, does it set the S_IFDIR bit on?
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/open/open01.c
+ <\test_location>
+<\testname>
+<testname=open02>
+ <description>
+ Test if open without O_CREAT returns -1 if a file does not exist.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/open/open02.c
+ <\test_location>
+<\testname>
+<testname=open03>
+ <description>
+ Basic test for open(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/open/open03.c
+ <\test_location>
+<\testname>
+<testname=open04>
+ <description>
+ Testcase to check that open(2) sets EMFILE if a process opens files
+ more than its descriptor size
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/open/open04.c
+ <\test_location>
+<\testname>
+<testname=open05>
+ <description>
+ Testcase to check open(2) sets errno to EACCES correctly.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/open/open05.c
+ <\test_location>
+<\testname>
+<testname=open06>
+ <description>
+ Testcase to check open(2) sets errno to ENXIO correctly.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/open/open06.c
+ <\test_location>
+<\testname>
+<testname=open07>
+ <description>
+ Test the open(2) system call to ensure that it sets ELOOP correctly.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/open/open07.c
+ <\test_location>
+<\testname>
+<testname=open08>
+ <description>
+ Check for the following errors:
+ 1. EEXIST
+ 2. EISDIR
+ 3. ENOTDIR
+ 4. ENAMETOOLONG
+ 5. EFAULT
+ 6. ETXTBSY
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/open/open08.c
+ <\test_location>
+<\testname>
+<testname=open09>
+ <description>
+ Does a read on a file opened with oflag set to O_WRONLY and checks for -1 return.
+ Does a write on a file opened with oflag set to O_RDONLY and checks for -1 return.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/open/open09.c
+ <\test_location>
+<\testname>
+<testname=open10>
+ <description>
+ Verifies that the group ID and setgid bit are set correctly when a new file
+ is created using open.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/open/open10.c
+ <\test_location>
+<\testname>
+<testname=pathconf01>
+ <description>
+ Basic test for pathconf(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/pathconf/pathconf01.c
+ <\test_location>
+<\testname>
+<testname=pause01>
+ <description>
+ Basic test for pause(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/pause/pause01.c
+ <\test_location>
+<\testname>
+<testname=pause02>
+ <description>
+ Verify that, pause() returns -1 and sets errno to EINTR after receipt
+ of a signal which is caught by the calling process. Also, verify that
+ the calling process will resume execution from the point of suspension.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/pause/pause02.c
+ <\test_location>
+<\testname>
+<testname=pause03>
+ <description>
+ Verify that a process is no longer accessible on receipt of SIGKILL
+ signal after being suspended by pause().
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/pause/pause03.c
+ <\test_location>
+<\testname>
+<testname=personality01>
+ <description>
+ Check that we can set the personality for a process.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/personality/personality01.c
+ <\test_location>
+<\testname>
+<testname=personality02>
+ <description>
+ Check that we get EINVAL for a bad personality.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/personality/personality02.c
+ <\test_location>
+<\testname>
+<testname=pipe01>
+ <description>
+ Testcase to check the basic functionality of the pipe(2) syscall:
+ Check that both ends of the pipe (both file descriptors) are
+ available to a process opening the pipe.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/pipe/pipe01.c
+ <\test_location>
+<\testname>
+<testname=pipe05>
+ <description>
+ Check what happens when pipe is passed a bad file descriptor.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/pipe/pipe05.c
+ <\test_location>
+<\testname>
+<testname=pipe06>
+ <description>
+ Check what happens when the system runs out of pipes.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/pipe/pipe06.c
+ <\test_location>
+<\testname>
+<testname=pipe08>
+ <description>
+ Check that a SIGPIPE signal is generated when a write is
+ attempted on an empty pipe.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/pipe/pipe08.c
+ <\test_location>
+<\testname>
+<testname=pipe09>
+ <description>
+ Check that two processes can use the same pipe at the same time.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/pipe/pipe09.c
+ <\test_location>
+<\testname>
+<testname=pipe10>
+ <description>
+ Check that parent can open a pipe and have a child read from it
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/pipe/pipe10.c
+ <\test_location>
+<\testname>
+<testname=pipe11>
+ <description>
+ Check if many children can read what is written to a pipe by the
+ parent.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/pipe/pipe11.c
+ <\test_location>
+<\testname>
+<testname=poll01>
+ <description>
+ Verify that valid open file descriptor must be provided to poll() to
+ succeed.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/poll/poll01.c
+ <\test_location>
+<\testname>
+<testname=prctl01>
+ <description>
+ Basic test of prctl().
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/prctl/prctl01.c
+ <\test_location>
+<\testname>
+<testname=prctl02>
+ <description>
+ Test of error conditions for prctl().
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/prctl/prctl02.c
+ <\test_location>
+<\testname>
+<testname=pread01>
+ <description>
+ Verify the functionality of pread() by writing known data using pwrite()
+ to the file at various specified offsets and later read from the file from
+ various specified offsets, comparing the data read aganist the data
+ written.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/pread/pread01.c
+ <\test_location>
+<\testname>
+<testname=pread02>
+ <description>
+ Verify that,
+ 1) pread() fails when attempted to read from an unnamed pipe.
+ 2) pread() fails if the specified offset position was invalid.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/pread/pread02.c
+ <\test_location>
+<\testname>
+<testname=profil01>
+ <description>
+ Basic test of profil().
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/profil/profil01.c
+ <\test_location>
+<\testname>
+<testname=ptrace01>
+ <description>
+ Functionality test for ptrace(2).
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/ptrace/ptrace01.c
+ <\test_location>
+<\testname>
+<testname=ptrace02>
+ <description>
+ Functionality test for ptrace(2).
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/ptrace/ptrace02.c
+ <\test_location>
+<\testname>
+<testname=ptrace3>
+ <description>
+ Tests for error conditions.
+
+ <\description>
+ <test_location>
+ <\test_location>
+<\testname>
+<testname=pwrite01>
+ <description>
+ Verify the functionality of pwrite() by writing known data using pwrite()
+ to the file at various specified offsets and later read from the file from
+ various specified offsets, comparing the data written aganist the data
+ read using read().
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/pwrite/pwrite01.c
+ <\test_location>
+<\testname>
+<testname=pwrite02>
+ <description>
+ Verify that,
+ 1) pwrite() fails when attempted to write to an unnamed pipe.
+ 2) pwrite() fails if the specified offset position was invalid.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/pwrite/pwrite02.c
+ <\test_location>
+<\testname>
+<testname=read01>
+ <description>
+ Basic test for the read(2) system call
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/read/read01.c
+ <\test_location>
+<\testname>
+<testname=read02>
+ <description>
+ test 1:
+ Does read return -1 if file descriptor is not valid, check for EBADF
+
+ test 2:
+ Check if read sets EISDIR, if the fd refers to a directory
+
+ test 3:
+ Check if read sets EFAULT, if buf is -1.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/read/read02.c
+ <\test_location>
+<\testname>
+<testname=read03>
+ <description>
+ Testcase to check that read() sets errno to EAGAIN
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/read/read03.c
+ <\test_location>
+<\testname>
+<testname=read04>
+ <description>
+ Testcase to check if read returns the number of bytes read correctly.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/read/read04.c
+ <\test_location>
+<\testname>
+<testname=readdir01>
+ <description>
+ Write multiple files and try to find them with readdir().
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/readdir/readdir01.c
+ <\test_location>
+<\testname>
+<testname=readdir02>
+ <description>
+ Try to readdir with invalid directory stream descriptor dir.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/readdir/readdir02.c
+ <\test_location>
+<\testname>
+<testname=readlink01>
+ <description>
+ Verify that, readlink will succeed to read the contents of the symbolic
+ link created the process.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/readlink/readlink01.c
+ <\test_location>
+<\testname>
+<testname=readlink02>
+ <description>
+ Basic test for the readlink(2) system call
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/readlink/readlink02.c
+ <\test_location>
+<\testname>
+<testname=readlink03>
+ <description>
+ Verify that,
+ 1) readlink(2) returns -1 and sets errno to EACCES if search/write
+ permission is denied in the directory where the symbolic link
+ resides.
+ 2) readlink(2) returns -1 and sets errno to EINVAL if the buffer size
+ is not positive.
+ 3) readlink(2) returns -1 and sets errno to EINVAL if the specified
+ file is not a symbolic link file.
+ 4) readlink(2) returns -1 and sets errno to ENAMETOOLONG if the
+ pathname component of symbolic link is too long (ie, > PATH_MAX).
+ 5) readlink(2) returns -1 and sets errno to ENOENT if the component of
+ symbolic link points to an empty string.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/readlink/readlink03.c
+ <\test_location>
+<\testname>
+<testname=readlink04>
+ <description>
+ Verify that, readlink call will succeed to read the contents of the
+ symbolic link if invoked by non-root user who is not the owner of the
+ symbolic link.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/readlink/readlink04.c
+ <\test_location>
+<\testname>
+<testname=readv01>
+ <description>
+ Testcase to check the basic functionality of the readv(2) system call.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/readv/readv01.c
+ <\test_location>
+<\testname>
+<testname=readv02>
+ <description>
+ Testcase to check the error conditions of the readv(2) system call.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/readv/readv02.c
+ <\test_location>
+<\testname>
+<testname=reboot01>
+ <description>
+ Test basic functionality of reboot().
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/reboot/reboot01.c
+ <\test_location>
+<\testname>
+<testname=reboot02>
+ <description>
+ Test error conditions of reboot().
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/reboot/reboot02.c
+ <\test_location>
+<\testname>
+<testname=recv01>
+ <description>
+ Verify that recv() returns the proper errno for various failure cases
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/recv/recv01.c
+ <\test_location>
+<\testname>
+<testname=recvfrom01>
+ <description>
+ Verify that recvfrom() returns the proper errno for various failure cases
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/recvfrom/recvfrom01.c
+ <\test_location>
+<\testname>
+<testname=recvmsg01>
+ <description>
+ Verify that recvmsg() returns the proper errno for various failure cases
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/recvmsg/recvmsg01.c
+ <\test_location>
+<\testname>
+<testname=rename01>
+ <description>
+ This test will verify the rename(2) syscall basic functionality.
+ Verify rename() works when the "new" file or directory does not exist.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/rename/rename01.c
+ <\test_location>
+<\testname>
+<testname=rename02>
+ <description>
+ Basic test for the rename(2) system call
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/rename/rename02.c
+ <\test_location>
+<\testname>
+<testname=rename03>
+ <description>
+ This test will verify that rename(2) functions correctly
+ when the "new" file or directory exists
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/rename/rename03.c
+ <\test_location>
+<\testname>
+<testname=rename04>
+ <description>
+ This test will verify that rename(2) failed when newpath is
+ a non-empty directory and return EEXIST or ENOTEMPTY
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/rename/rename04.c
+ <\test_location>
+<\testname>
+<testname=rename05>
+ <description>
+ This test will verify that rename(2) fails with EISDIR
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/rename/rename05.c
+ <\test_location>
+<\testname>
+<testname=rename06>
+ <description>
+ This test will verify that rename(2) failed in EINVAL
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/rename/rename06.c
+ <\test_location>
+<\testname>
+<testname=rename07>
+ <description>
+ This test will verify that rename(2) failed in ENOTDIR
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/rename/rename07.c
+ <\test_location>
+<\testname>
+<testname=rename08>
+ <description>
+ This test will verify that rename(2) syscall failed in EFAULT
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/rename/rename08.c
+ <\test_location>
+<\testname>
+<testname=rename09>
+ <description>
+ check rename() fails with EACCES
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/rename/rename09.c
+ <\test_location>
+<\testname>
+<testname=rename10>
+ <description>
+ This test will verify that rename(2) syscall fails with ENAMETOOLONG
+ and ENOENT
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/rename/rename10.c
+ <\test_location>
+<\testname>
+<testname=rename11>
+ <description>
+ This test will verify that rename(2) failed in EBUSY
+
+ <\description>
+ <test_location>
+ <\test_location>
+<\testname>
+<testname=rename12>
+ <description>
+ check rename() fails with EPERM
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/rename/rename12.c
+ <\test_location>
+<\testname>
+<testname=rename13>
+ <description>
+ Verify rename() return successfully and performs no other action
+ when "old" file and "new" file link to the same file.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/rename/rename13.c
+ <\test_location>
+<\testname>
+<testname=rmdir01>
+ <description>
+ This test will verify that rmdir(2) syscall basic functionality.
+ verify rmdir(2) returns a value of 0 and the directory being
+ removed
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/rmdir/rmdir01.c
+ <\test_location>
+<\testname>
+<testname=rmdir02>
+ <description>
+ This test will verify that rmdir(2) fail in
+ 1. ENOTEMPTY
+ 2. EBUSY
+ 3. ENAMETOOLONG
+ 4. ENOENT
+ 5. ENOTDIR
+ 6. EFAULT
+ 7. EFAULT
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/rmdir/rmdir02.c
+ <\test_location>
+<\testname>
+<testname=rmdir03>
+ <description>
+ check rmdir() fails with EPERM or EACCES
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/rmdir/rmdir03.c
+ <\test_location>
+<\testname>
+<testname=rmdir04>
+ <description>
+ Basic test for the rmdir(2) system call
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/rmdir/rmdir04.c
+ <\test_location>
+<\testname>
+<testname=rmdir05>
+ <description>
+ Verify that rmdir(2) returns a value of -1 and sets errno to indicate the error.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/rmdir/rmdir05.c
+ <\test_location>
+<\testname>
+<testname=sbrk01>
+ <description>
+ Basic test for the sbrk(2) system call.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/sbrk/sbrk01.c
+ <\test_location>
+<\testname>
+<testname=sched_get_priority_max01>
+ <description>
+ Basic test for sched_get_priority_max().
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/sched_get_priority_max/sched_get_priority_max01.c
+ <\test_location>
+<\testname>
+<testname=sched_get_priority_max02>
+ <description>
+ Error condition test for sched_get_priority_max().
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/sched_get_priority_max/sched_get_priority_max02.c
+ <\test_location>
+<\testname>
+<testname=sched_get_priority_min01>
+ <description>
+ Basic test for sched_get_priority_min().
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/sched_get_priority_min/sched_get_priority_min01.c
+ <\test_location>
+<\testname>
+<testname=sched_get_priority_min02>
+ <description>
+ Error condition test for sched_get_priority_min().
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/sched_get_priority_min/sched_get_priority_min02.c
+ <\test_location>
+<\testname>
+<testname=sched_getparam01>
+ <description>
+ Basic test for sched_getparam(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/sched_getparam/sched_getparam01.c
+ <\test_location>
+<\testname>
+<testname=sched_getparam02>
+ <description>
+ Get scheduling parametes for parent process
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/sched_getparam/sched_getparam02.c
+ <\test_location>
+<\testname>
+<testname=sched_getparam03>
+ <description>
+ Testing error conditions for sched_getparam(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/sched_getparam/sched_getparam03.c
+ <\test_location>
+<\testname>
+<testname=sched_getscheduler01>
+ <description>
+ Testcase to check sched_getscheduler() returns correct return value
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/sched_getscheduler/sched_getscheduler01.c
+ <\test_location>
+<\testname>
+<testname=sched_getscheduler02>
+ <description>
+ To check for the errno ESRCH
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/sched_getscheduler/sched_getscheduler02.c
+ <\test_location>
+<\testname>
+<testname=sched_rr_get_interval01>
+ <description>
+ Basic test for sched_rr_get_interval(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/sched_rr_get_interval/sched_rr_get_interval01.c
+ <\test_location>
+<\testname>
+<testname=sched_rr_get_interval02>
+ <description>
+ Functionality test
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/sched_rr_get_interval/sched_rr_get_interval02.c
+ <\test_location>
+<\testname>
+<testname=sched_rr_get_interval03>
+ <description>
+ Tests for error conditions
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/sched_rr_get_interval/sched_rr_get_interval03.c
+ <\test_location>
+<\testname>
+<testname=sched_setparam01>
+ <description>
+ Basic test for sched_setparam(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/sched_setparam/sched_setparam01.c
+ <\test_location>
+<\testname>
+<testname=sched_setparam02>
+ <description>
+ Checks functionality for sched_setparam(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/sched_setparam/sched_setparam02.c
+ <\test_location>
+<\testname>
+<testname=sched_setparam03>
+ <description>
+ Checks functionality for sched_setparam(2) for pid!=0
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/sched_setparam/sched_setparam03.c
+ <\test_location>
+<\testname>
+<testname=sched_setparam04>
+ <description>
+ Testing error conditions for sched_setparam(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/sched_setparam/sched_setparam04.c
+ <\test_location>
+<\testname>
+<testname=sched_setparam05>
+ <description>
+ Verify that sched_setparam() fails if the user does
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/sched_setparam/sched_setparam05.c
+ <\test_location>
+<\testname>
+<testname=sched_setscheduler01>
+ <description>
+ Testcase to test whether sched_setscheduler(2) sets the errnos
+ correctly.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/sched_setscheduler/sched_setscheduler01.c
+ <\test_location>
+<\testname>
+<testname=sched_setscheduler02>
+ <description>
+ Testcase to test whether sched_setscheduler(2) sets the errnos
+ correctly.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/sched_setscheduler/sched_setscheduler02.c
+ <\test_location>
+<\testname>
+<testname=sched_yield01>
+ <description>
+ Testcase to check that sched_yield returns correct values.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/sched_yield/sched_yield01.c
+ <\test_location>
+<\testname>
+<testname=select01>
+ <description>
+ Basic test for the select(2) system call to a fd of regular file with no I/O
+ and small timeout
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/select/select01.c
+ <\test_location>
+<\testname>
+<testname=select02>
+ <description>
+ Basic test for the select(2) system call to fd of system pipe with no I/O
+ and small timeout
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/select/select02.c
+ <\test_location>
+<\testname>
+<testname=select03>
+ <description>
+ Basic test for the select(2) system call to fd of a named-pipe (FIFO)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/select/select03.c
+ <\test_location>
+<\testname>
+<testname=select04>
+ <description>
+ Verify that select(2) returns immediately (does not block) if the
+ timeout value is zero.
+
+ <\description>
+ <test_location>
+ <\test_location>
+<\testname>
+<testname=select05>
+ <description>
+ Verify that select(2) fails when one or more of the file descriptor sets
+ specify a file descriptor which is not valid.
+
+ <\description>
+ <test_location>
+ <\test_location>
+<\testname>
+<testname=select06>
+ <description>
+ Verify that select(2) fails when a signal is delivered before any of the
+ selected events occur and before the timeout interval expires.
+
+ <\description>
+ <test_location>
+ <\test_location>
+<\testname>
+<testname=select07>
+ <description>
+ Verify that select(2) fails when an invalid timeout interval is specified.
+
+ <\description>
+ <test_location>
+ <\test_location>
+<\testname>
+<testname=select08>
+ <description>
+ Verify the functionality of select(2) by passing non-null writefds
+ which points to a regular file, pipes or FIFO's.
+
+ <\description>
+ <test_location>
+ <\test_location>
+<\testname>
+<testname=select09>
+ <description>
+ Verify the functionality of select(2) by passing non-null readfds
+ which points to a regular file, pipes or FIFO's.
+
+ <\description>
+ <test_location>
+ <\test_location>
+<\testname>
+<testname=select10>
+ <description>
+ Verify that a successful call to select() shall return the desired
+ number of modified descriptors for which bits are set in the bit masks,
+ where descriptors points to a regular file, pipes or FIFO's.
+
+ <\description>
+ <test_location>
+ <\test_location>
+<\testname>
+<testname=send01>
+ <description>
+ Verify that send() returns the proper errno for various failure cases
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/send/send01.c
+ <\test_location>
+<\testname>
+<testname=sendfile02>
+ <description>
+ Testcase to test the basic functionality of the sendfile(2) system call.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/sendfile/sendfile02.c
+ <\test_location>
+<\testname>
+<testname=sendfile03>
+ <description>
+ Testcase to test that sendfile(2) system call returns appropriete
+ errnos on error.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/sendfile/sendfile03.c
+ <\test_location>
+<\testname>
+<testname=sendmsg01>
+ <description>
+ Verify that sendmsg() returns the proper errno for various failure cases
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/sendmsg/sendmsg01.c
+ <\test_location>
+<\testname>
+<testname=sendto01>
+ <description>
+ Verify that sendto() returns the proper errno for various failure cases
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/sendto/sendto01.c
+ <\test_location>
+<\testname>
+<testname=setdomainname01>
+ <description>
+ Basic test for setdomainame(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/setdomainname/setdomainname01.c
+ <\test_location>
+<\testname>
+<testname=setdomainname02>
+ <description>
+ Test for checking error conditions for setdomainame(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/setdomainname/setdomainname02.c
+ <\test_location>
+<\testname>
+<testname=setdomainname03>
+ <description>
+ Test for EPERM error value when run as non superuser
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/setdomainname/setdomainname03.c
+ <\test_location>
+<\testname>
+<testname=setegid01>
+ <description>
+ Verify that setegid does not modify the saved gid or real gid.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/setegid/setegid01.c
+ <\test_location>
+<\testname>
+<testname=setfsgid01>
+ <description>
+ Testcase to check the basic functionality of setfsgid(2) system
+ call.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/setfsgid/setfsgid01.c
+ <\test_location>
+<\testname>
+<testname=setfsuid01>
+ <description>
+ Testcase to test the basic functionality of the setfsuid(2) system
+ call.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/setfsuid/setfsuid01.c
+ <\test_location>
+<\testname>
+<testname=setgid01>
+ <description>
+ Basic test for the setgid(2) system call.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/setgid/setgid01.c
+ <\test_location>
+<\testname>
+<testname=setgid02>
+ <description>
+ Testcase to ensure that the setgid() system call sets errno to EPERM
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/setgid/setgid02.c
+ <\test_location>
+<\testname>
+<testname=setgroups01>
+ <description>
+ Basic test for the setgroups(2) system call.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/setgroups/setgroups01.c
+ <\test_location>
+<\testname>
+<testname=setgroups02>
+ <description>
+ Verify that,
+ 1. setgroups() fails with -1 and sets errno to EINVAL if the size
+ argument value is > NGROUPS
+ 2. setgroups() fails with -1 and sets errno to EPERM if the
+ calling process is not super-user.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/setgroups/setgroups02.c
+ <\test_location>
+<\testname>
+<testname=setgroups03>
+ <description>
+ Verify that, only root process can invoke setgroups() system call to
+ set the supplementary group IDs of the process.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/setgroups/setgroups03.c
+ <\test_location>
+<\testname>
+<testname=setitimer01>
+ <description>
+ check that a resonable setitimer() call succeeds.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/setitimer/setitimer01.c
+ <\test_location>
+<\testname>
+<testname=setitimer02>
+ <description>
+ check that a setitimer() call fails as expected
+ with incorrect values.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/setitimer/setitimer02.c
+ <\test_location>
+<\testname>
+<testname=setitimer03>
+ <description>
+ check that a setitimer() call fails as expected
+ with incorrect values.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/setitimer/setitimer03.c
+ <\test_location>
+<\testname>
+<testname=setpgid01>
+ <description>
+ Basic test for setpgid(2) system call.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/setpgid/setpgid01.c
+ <\test_location>
+<\testname>
+<testname=setpgid02>
+ <description>
+ Testcase to check that setpgid() sets errno correctly.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/setpgid/setpgid02.c
+ <\test_location>
+<\testname>
+<testname=setpgid03>
+ <description>
+ Test to check the error and trivial conditions in setpgid system call
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/setpgid/setpgid03.c
+ <\test_location>
+<\testname>
+<testname=setpgrp01>
+ <description>
+ Basic test for the setpgrp(2) system call.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/setpgrp/setpgrp01.c
+ <\test_location>
+<\testname>
+<testname=setpgrp02>
+ <description>
+ Testcase to check the basic functionality of the setpgrp(2) syscall.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/setpgrp/setpgrp02.c
+ <\test_location>
+<\testname>
+<testname=setpriority01>
+ <description>
+ set the priority for the test process lower.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/setpriority/setpriority01.c
+ <\test_location>
+<\testname>
+<testname=setpriority02>
+ <description>
+ test for an expected failure by trying to raise
+ the priority for the test process while not having
+ permissions to do so.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/setpriority/setpriority02.c
+ <\test_location>
+<\testname>
+<testname=setpriority03>
+ <description>
+ test for an expected failure by using an invalid
+ PRIO value
+ setpriority04
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/setpriority/setpriority03.c
+ <\test_location>
+<\testname>
+<testname=setpriority04>
+ <description>
+ test for an expected failure by using an invalid
+ process id
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/setpriority/setpriority04.c
+ <\test_location>
+<\testname>
+<testname=setpriority05>
+ <description>
+ test for an expected failure by trying to change
+ a process with an ID that is different from the
+ test process
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/setpriority/setpriority05.c
+ <\test_location>
+<\testname>
+<testname=setregid01>
+ <description>
+ Basic test for the setregid(2) system call.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/setregid/setregid01.c
+ <\test_location>
+<\testname>
+<testname=setregid02>
+ <description>
+ Test that setregid() fails and sets the proper errno values when a
+ non-root user attemps to change the real or effective group id to a
+ value other than the current gid or the current effective gid.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/setregid/setregid02.c
+ <\test_location>
+<\testname>
+<testname=setregid03>
+ <description>
+ Test setregid() when executed by a non-root user.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/setregid/setregid03.c
+ <\test_location>
+<\testname>
+<testname=setregid04>
+ <description>
+ Test setregid() when executed by root.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/setregid/setregid04.c
+ <\test_location>
+<\testname>
+<testname=setresgid01>
+ <description>
+ Checks functionality of setresgid(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/setresgid/setresgid01.c
+ <\test_location>
+<\testname>
+<testname=setresgid02>
+ <description>
+ Checks functionality of setresgid(2) for non-root group id.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/setresgid/setresgid02.c
+ <\test_location>
+<\testname>
+<testname=setresgid03>
+ <description>
+ Checks error conditions for setresgid(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/setresgid/setresgid03.c
+ <\test_location>
+<\testname>
+<testname=setresuid01>
+ <description>
+ Test setresuid() when executed by root.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/setresuid/setresuid01.c
+ <\test_location>
+<\testname>
+<testname=setresuid02>
+ <description>
+ Test that a non-root user can change the real, effective and saved
+ uid values through the setresuid system call.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/setresuid/setresuid02.c
+ <\test_location>
+<\testname>
+<testname=setresuid03>
+ <description>
+ Test that the setresuid system call sets the proper errno
+ values when a non-root user attempts to change the real, effective or
+ saved uid to a value other than one of the current uid, the current
+ effective uid of the current saved uid. Also verify that setresuid
+ fails if an invalid uid value is given.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/setresuid/setresuid03.c
+ <\test_location>
+<\testname>
+<testname=setreuid01>
+ <description>
+ Basic test for the setreuid(2) system call.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/setreuid/setreuid01.c
+ <\test_location>
+<\testname>
+<testname=setreuid02>
+ <description>
+ Test setreuid() when executed by root.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/setreuid/setreuid02.c
+ <\test_location>
+<\testname>
+<testname=setreuid03>
+ <description>
+ Test setreuid() when executed by an unpriviledged user.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/setreuid/setreuid03.c
+ <\test_location>
+<\testname>
+<testname=setreuid04>
+ <description>
+ Test that root can change the real and effective uid to an
+ unpriviledged user.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/setreuid/setreuid04.c
+ <\test_location>
+<\testname>
+<testname=setreuid05>
+ <description>
+ Test the setreuid() feature, verifying the role of the saved-set-uid
+ and setreuid's effect on it.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/setreuid/setreuid05.c
+ <\test_location>
+<\testname>
+<testname=setreuid06>
+ <description>
+ Test that EINVAL is set when setreuid is given an invalid user id.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/setreuid/setreuid06.c
+ <\test_location>
+<\testname>
+<testname=setrlimit01>
+ <description>
+ Testcase to check the basic functionality of the setrlimit system call.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/setrlimit/setrlimit01.c
+ <\test_location>
+<\testname>
+<testname=setrlimit02>
+ <description>
+ Testcase to test the different errnos set by setrlimit(2) system call.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/setrlimit/setrlimit02.c
+ <\test_location>
+<\testname>
+<testname=setrlimit03>
+ <description>
+ Test for EPERM when the super-user tries to increase RLIMIT_NOFILE
+ beyond the system limit.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/setrlimit/setrlimit03.c
+ <\test_location>
+<\testname>
+<testname=setsid01>
+ <description>
+ Test to check the error and trivial conditions in setsid system call
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/setsid/setsid01.c
+ <\test_location>
+<\testname>
+<testname=setsockopt01>
+ <description>
+ Verify that setsockopt() returns the proper errno for various failure cases
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/setsockopt/setsockopt01.c
+ <\test_location>
+<\testname>
+<testname=settimeofday01>
+ <description>
+ Testcase to check the basic functionality of settimeofday().
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/settimeofday/settimeofday01.c
+ <\test_location>
+<\testname>
+<testname=settimeofday02>
+ <description>
+ Testcase to check that settimeofday() sets errnos correctly.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/settimeofday/settimeofday02.c
+ <\test_location>
+<\testname>
+<testname=setuid01>
+ <description>
+ Basic test for the setuid(2) system call.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/setuid/setuid01.c
+ <\test_location>
+<\testname>
+<testname=setuid02>
+ <description>
+ Basic test for the setuid(2) system call as root.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/setuid/setuid02.c
+ <\test_location>
+<\testname>
+<testname=setuid03>
+ <description>
+ Test to check the error and trivial conditions in setuid
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/setuid/setuid03.c
+ <\test_location>
+<\testname>
+<testname=sigaction01>
+ <description>
+ Test some features of sigaction (see below for more details)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/sigaction/sigaction01.c
+ <\test_location>
+<\testname>
+<testname=sigaction02>
+ <description>
+ Testcase to check the basic errnos set by the sigaction(2) syscall.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/sigaction/sigaction02.c
+ <\test_location>
+<\testname>
+<testname=sigaltstack01>
+ <description>
+ Send a signal using the main stack. While executing the signal handler
+ compare a variable's address lying on the main stack with the stack
+ boundaries returned by sigaltstack().
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/sigaltstack/sigaltstack01.c
+ <\test_location>
+<\testname>
+<testname=sigaltstack02>
+ <description>
+ Verify that,
+ 1. sigaltstack() fails and sets errno to EINVAL when "ss_flags" field
+ pointed to by 'ss' contains invalid flags.
+ 2. sigaltstack() fails and sets errno to ENOMEM when the size of alternate
+ stack area is less than MINSIGSTKSZ.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/sigaltstack/sigaltstack02.c
+ <\test_location>
+<\testname>
+<testname=sighold02>
+ <description>
+ Basic test for the sighold02(2) system call.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/sighold/sighold02.c
+ <\test_location>
+<\testname>
+<testname=signal01>
+ <description>
+ set the signal handler to our own function
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/signal/signal01.c
+ <\test_location>
+<\testname>
+<testname=signal02>
+ <description>
+ Test that we get an error using illegal signals
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/signal/signal02.c
+ <\test_location>
+<\testname>
+<testname=signal03>
+ <description>
+ Boundary value and other invalid value checking of signal setup and signal
+ sending.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/signal/signal03.c
+ <\test_location>
+<\testname>
+<testname=signal04>
+ <description>
+ restore signals to default behavior
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/signal/signal04.c
+ <\test_location>
+<\testname>
+<testname=signal03>
+ <description>
+ set signals to be ignored
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/signal/signal03.c
+ <\test_location>
+<\testname>
+<testname=sigpending02>
+ <description>
+ Test to see that the proper errors are returned by sigpending.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/sigpending/sigpending02.c
+ <\test_location>
+<\testname>
+<testname=sigprocmask01>
+ <description>
+ Verify that sigprocmask() succeeds to examine and change the calling
+ process's signal mask.
+ Also, verify that sigpending() succeeds to store signal mask that are
+ blocked from delivery and pending for the calling process.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/sigprocmask/sigprocmask01.c
+ <\test_location>
+<\testname>
+<testname=sigrelse01>
+ <description>
+ Basic test for the sigrelse(2) system call.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/sigrelse/sigrelse01.c
+ <\test_location>
+<\testname>
+<testname=sigsuspend01>
+ <description>
+ Verify that sigsuspend() succeeds to change process's current signal
+ mask with the specified signal mask and suspends the process execution
+ until the delivery of a signal.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/sigsuspend/sigsuspend01.c
+ <\test_location>
+<\testname>
+<testname=socket01>
+ <description>
+ Verify that socket() returns the proper errno for various failure cases
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/socket/socket01.c
+ <\test_location>
+<\testname>
+<testname=socketcall01>
+ <description>
+ Basic test for socketcall(2) for socket(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/socketcall/socketcall01.c
+ <\test_location>
+<\testname>
+<testname=socketcall02>
+ <description>
+ Error test for socketcall(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/socketcall/socketcall02.c
+ <\test_location>
+<\testname>
+<testname=socketcall03>
+ <description>
+ Basic test for socketcall(2) for bind(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/socketcall/socketcall03.c
+ <\test_location>
+<\testname>
+<testname=socketcall04>
+ <description>
+ Basic test for socketcall(2) for listen(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/socketcall/socketcall04.c
+ <\test_location>
+<\testname>
+<testname=socketpair01>
+ <description>
+ Verify that socketpair() returns the proper errno for various
+ failure cases
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/socketpair/socketpair01.c
+ <\test_location>
+<\testname>
+<testname=socketpair01>
+ <description>
+ Verify that socketpair() returns the proper errno for various failure cases
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/socketpair/socketpair01.c
+ <\test_location>
+<\testname>
+<testname=sockioctl01>
+ <description>
+ Verify that ioctl() on sockets returns the proper errno for various
+ failure cases
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/sockioctl/sockioctl01.c
+ <\test_location>
+<\testname>
+<testname=stat01>
+ <description>
+ Verify that, stat(2) succeeds to get the status of a file and fills the
+ stat structure elements.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/stat/stat01.c
+ <\test_location>
+<\testname>
+<testname=stat02>
+ <description>
+ Verify that, stat(2) succeeds to get the status of a file and fills the
+ stat structure elements though process doesn't have read access to the
+ file.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/stat/stat02.c
+ <\test_location>
+<\testname>
+<testname=stat03>
+ <description>
+ Verify that,
+ 1) stat(2) returns -1 and sets errno to EACCES if search permission is
+ denied on a component of the path prefix.
+ 2) stat(2) returns -1 and sets errno to ENOENT if the specified file
+ does not exists or empty string.
+ 3) stat(2) returns -1 and sets errno to EFAULT if pathname points
+ outside user's accessible address space.
+ 4) stat(2) returns -1 and sets errno to ENAMETOOLONG if the pathname
+ component is too long.
+ 5) stat(2) returns -1 and sets errno to ENOTDIR if the directory
+ component in pathname is not a directory.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/stat/stat03.c
+ <\test_location>
+<\testname>
+<testname=stat05>
+ <description>
+ Basic test for the stat05(2) system call.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/stat/stat05.c
+ <\test_location>
+<\testname>
+<testname=statfs01>
+ <description>
+ Basic test for the statfs(2) system call.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/statfs/statfs01.c
+ <\test_location>
+<\testname>
+<testname=statfs02>
+ <description>
+ Testcase to check that statfs(2) sets errno correctly.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/statfs/statfs02.c
+ <\test_location>
+<\testname>
+<testname=stime01>
+ <description>
+ Verify that the system call stime() successfully sets the system's idea
+ of data and time if invoked by "root" user.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/stime/stime01.c
+ <\test_location>
+<\testname>
+<testname=stime02>
+ <description>
+ Verify that the system call stime() fails to set the system's idea
+ of data and time if invoked by "non-root" user.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/stime/stime02.c
+ <\test_location>
+<\testname>
+<testname=string01>
+ <description>
+ Test string functions.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/string/string01.c
+ <\test_location>
+<\testname>
+<testname=swapoff01>
+ <description>
+ Basic test for swapoff(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/swapoff/swapoff01.c
+ <\test_location>
+<\testname>
+<testname=swapoff02>
+ <description>
+ Test checking for basic error conditions
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/swapoff/swapoff02.c
+ <\test_location>
+<\testname>
+<testname=swapon01>
+ <description>
+ Basic test for swapon(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/swapon/swapon01.c
+ <\test_location>
+<\testname>
+<testname=swapon02>
+ <description>
+ Test checking for basic error conditions
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/swapon/swapon02.c
+ <\test_location>
+<\testname>
+<testname=symlink01>
+ <description>
+ Test of various file function calls, such as rename or open, on a symbolic
+ link file.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/symlink/symlink01.c
+ <\test_location>
+<\testname>
+<testname=symlink02>
+ <description>
+ Basic test for the symlink(2) system call.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/symlink/symlink02.c
+ <\test_location>
+<\testname>
+<testname=symlink03>
+ <description>
+ Verify that,
+ 1) symlink(2) returns -1 and sets errno to EACCES if search/write
+ permission is denied in the directory where the symbolic link is
+ being created.
+ 2) symlink(2) returns -1 and sets errno to EEXIST if the specified
+ symbolic link already exists.
+ 3) symlink(2) returns -1 and sets errno to EFAULT if the specified
+ file or symbolic link points to invalid address.
+ 4) symlink(2) returns -1 and sets errno to ENAMETOOLONG if the
+ pathname component of symbolic link is too long (ie, > PATH_MAX).
+ 5) symlink(2) returns -1 and sets errno to ENOTDIR if the directory
+ component in pathname of symbolic link is not a directory.
+ 6) symlink(2) returns -1 and sets errno to ENOENT if the component of
+ symbolic link points to an empty string.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/symlink/symlink03.c
+ <\test_location>
+<\testname>
+<testname=symlink04>
+ <description>
+ Verify that, symlink will succeed to creat a symbolic link of an existing
+ object name path.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/symlink/symlink04.c
+ <\test_location>
+<\testname>
+<testname=symlink05>
+ <description>
+ Verify that, symlink will succeed to creat a symbolic link of an
+ non-existing object name path.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/symlink/symlink05.c
+ <\test_location>
+<\testname>
+<testname=sync01>
+ <description>
+ Basic test for the sync(2) system call.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/sync/sync01.c
+ <\test_location>
+<\testname>
+<testname=sync02>
+ <description>
+ Open a file for write; modify the file, then do a sync().
+ Verify that the data has been written to disk by re-opening the file.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/sync/sync02.c
+ <\test_location>
+<\testname>
+<testname=syscall01>
+ <description>
+ Basic test for the syscall() system call.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/syscall/syscall01.c
+ <\test_location>
+<\testname>
+<testname=sysconf01>
+ <description>
+ Basic test for the sysconf() system call.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/sysconf/sysconf01.c
+ <\test_location>
+<\testname>
+<testname=sysctl01>
+ <description>
+ Testcase for testing the basic functionality of sysctl(2) system call.
+ This testcase attempts to read the kernel parameters using
+ sysctl({CTL_KERN, KERN_ }, ...) and compares it with the known
+ values.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/sysctl/sysctl01.c
+ <\test_location>
+<\testname>
+<testname=sysctl03>
+ <description>
+ Testcase to check that sysctl(2) sets errno to EPERM correctly.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/sysctl/sysctl03.c
+ <\test_location>
+<\testname>
+<testname=sysctl04>
+ <description>
+ Testcase to check that sysctl(2) sets errno to ENOTDIR
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/sysctl/sysctl04.c
+ <\test_location>
+<\testname>
+<testname=sysctl05>
+ <description>
+ Testcase to check that sysctl(2) sets errno to EFAULT
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/sysctl/sysctl05.c
+ <\test_location>
+<\testname>
+<testname=sysfs01>
+ <description>
+ Basic test for sysfs(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/sysfs/sysfs01.c
+ <\test_location>
+<\testname>
+<testname=sysfs02>
+ <description>
+ Basic test for sysfs(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/sysfs/sysfs02.c
+ <\test_location>
+<\testname>
+<testname=sysfs03>
+ <description>
+ Basic test for sysfs(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/sysfs/sysfs03.c
+ <\test_location>
+<\testname>
+<testname=sysfs04>
+ <description>
+ Test checking for basic error conditions
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/sysfs/sysfs04.c
+ <\test_location>
+<\testname>
+<testname=sysfs05>
+ <description>
+ Test checking for basic error conditions
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/sysfs/sysfs05.c
+ <\test_location>
+<\testname>
+<testname=sysfs06>
+ <description>
+ Test checking for basic error conditions
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/sysfs/sysfs06.c
+ <\test_location>
+<\testname>
+<testname=sysinfo01>
+ <description>
+ Verify that sysinfo() succeeds to get the system information and fills
+ the structure passed.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/sysinfo/sysinfo01.c
+ <\test_location>
+<\testname>
+<testname=sysinfo02>
+ <description>
+ Verify that sysinfo() returns the correct error for an invalid address structure.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/sysinfo/sysinfo02.c
+ <\test_location>
+<\testname>
+<testname=syslog01>
+ <description>
+ Test whether messages are logged to the specified file
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/syslog/syslog01
+ <\test_location>
+<\testname>
+<testname=syslog02>
+ <description>
+ Test if messages of all levels are logged.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/syslog/syslog02
+ <\test_location>
+<\testname>
+<testname=syslog03>
+ <description>
+ Do openlog(), log the messages and see whether
+ ident string is prepended to the message.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/syslog/syslog03
+ <\test_location>
+<\testname>
+<testname=syslog04>
+ <description>
+ Test the logging option: LOG_PID
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/syslog/syslog04
+ <\test_location>
+<\testname>
+<testname=syslog05>
+ <description>
+ Test the logging option: LOG_CONS
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/syslog/syslog05
+ <\test_location>
+<\testname>
+<testname=syslog06>
+ <description>
+ Test the logging option: LOG_NDELAY
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/syslog/syslog06
+ <\test_location>
+<\testname>
+<testname=syslog07>
+ <description>
+ Test the priorities.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/syslog/syslog07
+ <\test_location>
+<\testname>
+<testname=syslog08>
+ <description>
+ Test all the facilities at a particular level.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/syslog/syslog08
+ <\test_location>
+<\testname>
+<testname=syslog09>
+ <description>
+ Test setlogmask() with LOG_UPTO macro.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/syslog/syslog09
+ <\test_location>
+<\testname>
+<testname=syslog10>
+ <description>
+ Test setlogmask() with LOG_MASK macro.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/syslog/syslog10
+ <\test_location>
+<\testname>
+<testname=syslog11>
+ <description>
+ Basic test for syslog() function call.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/syslog/syslog11.c
+ <\test_location>
+<\testname>
+<testname=syslog12>
+ <description>
+ Check error conditions for syscall().
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/syslog/syslog12.c
+ <\test_location>
+<\testname>
+<testname=time01>
+ <description>
+ Basic test for the time(2) system call.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/time/time01.c
+ <\test_location>
+<\testname>
+<testname=time02>
+ <description>
+ Verify that time(2) returns the value of time in seconds since
+ the Epoch and stores this value in the memory pointed to by the parameter.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/time/time02.c
+ <\test_location>
+<\testname>
+<testname=times01>
+ <description>
+ Basic test for the times(2) system call.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/times/times01.c
+ <\test_location>
+<\testname>
+<testname=times03>
+ <description>
+ Testcase to check the basic functionality of the times() system call.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/times/times03.c
+ <\test_location>
+<\testname>
+<testname=truncate01>
+ <description>
+ Verify that, truncate(2) succeeds to truncate a file to a specified
+ length.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/truncate/truncate01.c
+ <\test_location>
+<\testname>
+<testname=truncate02>
+ <description>
+ Verify that, truncate(2) succeeds to truncate a file to a certain length,
+ but the attempt to read past the truncated length will fail.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/truncate/truncate02.c
+ <\test_location>
+<\testname>
+<testname=truncate03>
+ <description>
+ Verify that,
+ 1) truncate(2) returns -1 and sets errno to EACCES if search/write
+ permission denied for the process on the component of the path prefix
+ or named file.
+ 2) truncate(2) returns -1 and sets errno to ENOTDIR if the component of
+ the path prefix is not a directory.
+ 3) truncate(2) returns -1 and sets errno to EFAULT if pathname points
+ outside user's accessible address space.
+ 4) truncate(2) returns -1 and sets errno to ENAMETOOLONG if the component
+ of a pathname exceeded 255 characters or entire pathname exceeds 1023
+ characters.
+ 5) truncate(2) returns -1 and sets errno to ENOENT if the named file
+ does not exist.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/truncate/truncate03.c
+ <\test_location>
+<\testname>
+<testname=ulimit01>
+ <description>
+ Basic test for the ulimit(2) system call.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/ulimit/ulimit01.c
+ <\test_location>
+<\testname>
+<testname=umask01>
+ <description>
+ Basic test for the umask(2) system call.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/umask/umask01.c
+ <\test_location>
+<\testname>
+<testname=umask02>
+ <description>
+ Check that umask changes the mask, and that the previous
+ value of the mask is returned correctly for each value.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/umask/umask02.c
+ <\test_location>
+<\testname>
+<testname=umask03>
+ <description>
+ Check that umask changes the mask, and that the previous
+ value of the mask is returned correctly for each value.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/umask/umask03.c
+ <\test_location>
+<\testname>
+<testname=umount01>
+ <description>
+ Basic test for umount(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/umount/umount01.c
+ <\test_location>
+<\testname>
+<testname=umount02>
+ <description>
+ Test for checking basic error conditions for umount(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/umount/umount02.c
+ <\test_location>
+<\testname>
+<testname=umount03>
+ <description>
+ Test for checking EPERM
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/umount/umount03.c
+ <\test_location>
+<\testname>
+<testname=umount04>
+ <description>
+ Test for checking EACCES
+
+ <\description>
+ <test_location>
+ <\test_location>
+<\testname>
+<testname=uname01>
+ <description>
+ Basic test for the uname(2) system call.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/uname/uname01.c
+ <\test_location>
+<\testname>
+<testname=uname02>
+ <description>
+ Call uname() with an invalid address to produce a failure
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/uname/uname02.c
+ <\test_location>
+<\testname>
+<testname=uname03>
+ <description>
+ Call uname() and make sure it succeeds
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/uname/uname03.c
+ <\test_location>
+<\testname>
+<testname=unlink05>
+ <description>
+ Basic test for the unlink(2) system call.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/unlink/unlink05.c
+ <\test_location>
+<\testname>
+<testname=unlink06>
+ <description>
+ Test for the unlink(2) system call of a FIFO.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/unlink/unlink06.c
+ <\test_location>
+<\testname>
+<testname=unlink07>
+ <description>
+ Tests for error handling for the unlink(2) system call.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/unlink/unlink07.c
+ <\test_location>
+<\testname>
+<testname=unlink08>
+ <description>
+ More tests for error handling for the unlink(2) system call.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/unlink/unlink08.c
+ <\test_location>
+<\testname>
+<testname=ustat01>
+ <description>
+ Basic test for the ustat() system call.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/ustat/ustat01.c
+ <\test_location>
+<\testname>
+<testname=ustat02>
+ <description>
+ Test for error conditions of ustat().
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/ustat/ustat02.c
+ <\test_location>
+<\testname>
+<testname=utime01>
+ <description>
+ Verify that the system call utime() successfully sets the modification
+ and access times of a file to the current time, if the times argument
+ is null, and the user ID of the process is "root".
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/utime/utime01.c
+ <\test_location>
+<\testname>
+<testname=utime02>
+ <description>
+ Verify that the system call utime() successfully sets the modification
+ and access times of a file to the current time, under the following
+ constraints,
+ - The times argument is null.
+ - The user ID of the process is not "root".
+ - The file is owned by the user ID of the process.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/utime/utime02.c
+ <\test_location>
+<\testname>
+<testname=utime03>
+ <description>
+ Verify that the system call utime() successfully sets the modification
+ and access times of a file to the current time, under the following
+ constraints,
+ - The times argument is null.
+ - The user ID of the process is not "root".
+ - The file is not owned by the user ID of the process.
+ - The user ID of the process has write access to the file.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/utime/utime03.c
+ <\test_location>
+<\testname>
+<testname=utime04>
+ <description>
+ Verify that the system call utime() successfully sets the modification
+ and access times of a file to the time specified by times argument, if
+ the times argument is not null, and the user ID of the process is "root".
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/utime/utime04.c
+ <\test_location>
+<\testname>
+<testname=utime05>
+ <description>
+ Verify that the system call utime() successfully sets the modification
+ and access times of a file to the value specified by the times argument
+ under the following constraints,
+ - The times argument is not null,
+ - The user ID of the process is not "root".
+ - The file is owned by the user ID of the process.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/utime/utime05.c
+ <\test_location>
+<\testname>
+<testname=utime06>
+ <description>
+ 1. Verify that the system call utime() fails to set the modification
+ and access times of a file to the current time, under the following
+ constraints,
+
+ The times argument is null.
+
+ The user ID of the process is not "root".
+
+ The file is not owned by the user ID of the process.
+
+ The user ID of the process does not have write access to the
+ file.
+ 2. Verify that the system call utime() fails to set the modification
+ and access times of a file if the specified file doesn't exist.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/utime/utime06.c
+ <\test_location>
+<\testname>
+<testname=vfork01>
+ <description>
+ Fork a process using vfork() and verify that, the attribute values like
+ euid, ruid, suid, egid, rgid, sgid, umask, inode and device number of
+ root and current working directories are same as that of the parent
+ process.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/vfork/vfork01.c
+ <\test_location>
+<\testname>
+<testname=vfork02>
+ <description>
+ Fork a process using vfork() and verify that, the pending signals in
+ the parent are not pending in the child process.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/vfork/vfork02.c
+ <\test_location>
+<\testname>
+<testname=vhangup01>
+ <description>
+ Check the return value, and errno of vhangup(2)
+ when a non-root user calls vhangup().
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/vhangup/vhangup01.c
+ <\test_location>
+<\testname>
+<testname=vhangup02>
+ <description>
+ To test the basic functionality of vhangup(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/vhangup/vhangup02.c
+ <\test_location>
+<\testname>
+<testname=wait02>
+ <description>
+ Basic test for wait(2) system call.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/wait/wait02.c
+ <\test_location>
+<\testname>
+<testname=wait401>
+ <description>
+ check that a call to wait4() correctly waits for a child
+ process to exit
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/wait4/wait401.c
+ <\test_location>
+<\testname>
+<testname=wait402>
+ <description>
+ check for ECHILD errno when using an illegal pid value
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/wait4/wait402.c
+ <\test_location>
+<\testname>
+<testname=waitpid01>
+ <description>
+ Check that when a child kills itself by generating an alarm
+ exception, the waiting parent is correctly notified.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/waitpid/waitpid01.c
+ <\test_location>
+<\testname>
+<testname=waitpid02>
+ <description>
+ Check that when a child kills itself by generating an integer zero
+ divide exception, the waiting parent is correctly notified.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/waitpid/waitpid02.c
+ <\test_location>
+<\testname>
+<testname=waitpid03>
+ <description>
+ Check that parent waits unitl specific child has returned.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/waitpid/waitpid03.c
+ <\test_location>
+<\testname>
+<testname=waitpid04>
+ <description>
+ test to check the error conditions in waitpid sys call
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/waitpid/waitpid04.c
+ <\test_location>
+<\testname>
+<testname=waitpid05>
+ <description>
+ Check that when a child kills itself with a kill statement after
+ determining its process id by using getpid, the parent receives a
+ correct report of the cause of its death. This also indirectly
+ checks that getpid returns the correct process id.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/waitpid/waitpid05.c
+ <\test_location>
+<\testname>
+<testname=waitpid06>
+ <description>
+ Tests to see if pid's returned from fork and waitpid are same.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/waitpid/waitpid06.c
+ <\test_location>
+<\testname>
+<testname=waitpid07>
+ <description>
+ Tests to see if pid's returned from fork and waitpid are same.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/waitpid/waitpid07.c
+ <\test_location>
+<\testname>
+<testname=waitpid08>
+ <description>
+ Tests to see if pid's returned from fork and waitpid are same
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/waitpid/waitpid08.c
+ <\test_location>
+<\testname>
+<testname=waitpid09>
+ <description>
+ Check ability of parent to wait until child returns, and that the
+ child's process id is returned through the waitpid. Check that
+ waitpid returns immediately if no child is present.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/waitpid/waitpid09.c
+ <\test_location>
+<\testname>
+<testname=waitpid10>
+ <description>
+ Tests to see if pid's returned from fork and waitpid are same
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/waitpid/waitpid10.c
+ <\test_location>
+<\testname>
+<testname=waitpid11>
+ <description>
+ Tests to see if pid's returned from fork and waitpid are same
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/waitpid/waitpid11.c
+ <\test_location>
+<\testname>
+<testname=waitpid12>
+ <description>
+ Tests to see if pid's returned from fork and waitpid are same
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/waitpid/waitpid12.c
+ <\test_location>
+<\testname>
+<testname=waitpid13>
+ <description>
+ Tests to see if pid's returned from fork and waitpid are same
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/waitpid/waitpid13.c
+ <\test_location>
+<\testname>
+<testname=write01>
+ <description>
+ Basic test for write(2) system call.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/write/write01.c
+ <\test_location>
+<\testname>
+<testname=write02>
+ <description>
+ Basic functionality test: does the return from write match the count
+ of the number of bytes written.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/write/write02.c
+ <\test_location>
+<\testname>
+<testname=write03>
+ <description>
+ Testcase to check that write(2) doesn't corrupt a file when it fails
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/write/write03.c
+ <\test_location>
+<\testname>
+<testname=write04>
+ <description>
+ Testcase to check that write() sets errno to EAGAIN
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/write/write04.c
+ <\test_location>
+<\testname>
+<testname=write05>
+ <description>
+ Check the return value, and errnos of write(2)
+ - when the file descriptor is invalid
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/write/write05.c
+ <\test_location>
+<\testname>
+<testname=EBADF>
+ <description>
+ - when the buf parameter is invalid
+
+ <\description>
+ <test_location>
+ <\test_location>
+<\testname>
+<testname=EFAULT>
+ <description>
+ - on an attempt to write to a pipe that is not open for reading
+
+ <\description>
+ <test_location>
+ <\test_location>
+<\testname>
+<testname=writev01>
+ <description>
+ Testcase to check the basic functionality of writev(2) system call.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/writev/writev01.c
+ <\test_location>
+<\testname>
+<testname=writev02>
+ <description>
+ In these testcases, writev() is called with partially valid data
+ to be written in a sparse file.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/writev/writev02.c
+ <\test_location>
+<\testname>
+<testname=writev03>
+ <description>
+ The testcases are written calling writev() with partially valid data
+ to overwrite the contents, to write in the beginning and to write in
+ the end of the file.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/writev/writev03.c
+ <\test_location>
+<\testname>
+<testname=writev04>
+ <description>
+ The testcases are written calling writev() with partially valid data
+ to overwrite the contents, to write in the beginning and to write in
+ the end of the file. This is same as writev03, but the length of
+ buffer used here is 8192 bytes.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/writev/writev04.c
+ <\test_location>
+<\testname>
+<testname=writev05>
+ <description>
+ These testcases are written to test writev() on sparse files. This
+ is same as writev02. But the initial write() with valid data is
+ done at the beginning of the file.
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/syscalls/writev/writev05.c
+ <\test_location>
+<\testname>
+<testname=clock_gettime02>
+ <description>
+ Basic test for clock_gettime(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/timers/clock_gettime/clock_gettime02.c
+ <\test_location>
+<\testname>
+<testname=clock_gettime03>
+ <description>
+ Test checking for basic error conditions for clock_gettime(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/timers/clock_gettime/clock_gettime03.c
+ <\test_location>
+<\testname>
+<testname=clock_settime02>
+ <description>
+ Basic test for clock_settime(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/timers/clock_settime/clock_settime02.c
+ <\test_location>
+<\testname>
+<testname=clock_settime03>
+ <description>
+ Test checking for basic error conditions for clock_settime(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/timers/clock_settime/clock_settime03.c
+ <\test_location>
+<\testname>
+<testname=timer_create01>
+ <description>
+ Basic test for timer_create(2)
+
+ <\description>
+ <test_location>
+ <\test_location>
+<\testname>
+<testname=timer_create02>
+ <description>
+ Basic test for timer_create(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/timers/timer_create/timer_create02.c
+ <\test_location>
+<\testname>
+<testname=timer_create03>
+ <description>
+ Test checking for basic error conditions for timer_create(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/timers/timer_create/timer_create03.c
+ <\test_location>
+<\testname>
+<testname=timer_delete01>
+ <description>
+ Basic test for timer_delete(2)
+
+ <\description>
+ <test_location>
+ <\test_location>
+<\testname>
+<testname=timer_delete02>
+ <description>
+ Test checking for basic error conditions for timer_delete(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/timers/timer_delete/timer_delete02.c
+ <\test_location>
+<\testname>
+<testname=timer_settime01>
+ <description>
+ Basic test for timer_settime(2)
+
+ <\description>
+ <test_location>
+ <\test_location>
+<\testname>
+<testname=timers>
+ <description>
+ Test checking for basic error conditions for timer_settime(2)
+
+ <\description>
+ <test_location>
+ ltp/testcases/kernel/timers
+ <\test_location>
+<\testname>
diff -ruN ltp-full-20090531_orig/doc/testcases/misc.txt ltp-full-20090531/doc/testcases/misc.txt
--- ltp-full-20090531_orig/doc/testcases/misc.txt 2003-07-19 03:00:11.000000000 +0530
+++ ltp-full-20090531/doc/testcases/misc.txt 2009-06-19 11:31:28.000000000 +0530
@@ -1,100 +1,131 @@
-crash
------
-crash01
-
- A signal handler is set up so that in most cases the machine exception
- generated by the illegal instructions, bad operands, etc in the procedure
- made up of random data are caught; and another round of randomness may
- be tried. Eventually a random instruction may corrupt the program or
- the machine state in such a way that the program must halt. This is
- a test of the robustness of the hardware/software for instruction
- fault handling.
-
- Note: Running this program just a few times, using total CPU time of
- less than a few seconds SHOULD NOT GIVE YOU ANY CONFIDENCE in system
- robustness. Having it run for hours, with tens of thousands of cases
- would be a different thing. It would also make sense to run this
- stress test at the same time you run other tests, like a multi-user
- benchmark.
-
-
-crash02
-
- A signal handler is set up so that in most cases the machine exception
- generated by the illegal syscall, bad operands, etc in the procedure
- made up of random data are caught; and another round of randomness may
- be tried. Eventually a random syscall may corrupt the program or
- the machine state in such a way that the program must halt. This is
- a test of the robustness of the hardware/software for instruction
- fault handling.
-
- Note: Running this program just a few times, using total CPU time of
- less than a few seconds SHOULD NOT GIVE YOU ANY CONFIDENCE in system
- robustness. Having it run for hours, with tens of thousands of cases
- would be a different thing. It would also make sense to run this
- stress test at the same time you run other tests, like a multi-user
- benchmark.
-
- CAUTION: running this program may crash your system, your disk and all
- your data along! DO NOT RUN IT ON PRODUCTION SYSTEMS!
- CONSIDER YOUR DISK FRIED.
- REMEMBER THE DISCLAIMER PART OF THE LICENSE.
-
- Running as user nobody and with all your filesystems
- remounted to readonly may be wise..
-
-
-
-f00f
-----
-f00f
-
- This is a simple test for handling of the pentium f00f bug.
- It is an example of a catistrophic test case. If the system
- doesn't correctly handle this test, it will likely lockup.
-
-
-
-math
-----
-abs
-
- Test the basic functionality of the abs() system call.
-
-atof
-
- Test the basic functionality of the atof() system call.
-
-float
-
- Increase CPUs workload - verify that results of some math functions are stable
-
- Floating testcases are related to :
- ----------------------------------
- - trigonometric (acos, asin, atan, atan2, cos, sin, tan),
- - Euclidean distance function (hypot),
- - Computes the natural logarithm of the gamma function (lgamma),
- - Functions that manipulate floating-point numbers (modf, ldexp, frexp),
- - exponential and logarithmic functions (exp, log, log10),
- - hyperbolic (cosh, sinh, tanh),
- - Bessel (j0, j1, y0, y1),
- - and power functions (ceil, fabs, floor, fmod, pow, sqrt).
-
- The testcase is splitted into 5 sets:
- -------------------------------------
- float_bessel, float_exp_log, float_iperb, float_power, float_trigo
-
-fptests
-
- Additional floating point tests.
-
-nextafter
-
- Test basic functionality of nextafter() system call.
-
-
-
-tcore_patch_test_suites
------------------------
-
- Test suite for multi-thread core dump kernel patch.
+<testname=crash01>
+ <description>
+ A signal handler is set up so that in most cases the machine exception
+ generated by the illegal instructions, bad operands, etc in the procedure
+ made up of random data are caught; and another round of randomness may
+ be tried. Eventually a random instruction may corrupt the program or
+ the machine state in such a way that the program must halt. This is
+ a test of the robustness of the hardware/software for instruction
+ fault handling.
+
+ Note: Running this program just a few times, using total CPU time of
+ less than a few seconds SHOULD NOT GIVE YOU ANY CONFIDENCE in system
+ robustness. Having it run for hours, with tens of thousands of cases
+ would be a different thing. It would also make sense to run this
+ stress test at the same time you run other tests, like a multi-user
+ benchmark.
+
+ <\description>
+ <test_location>
+ ltp/testcases/misc/crash/crash01.c
+ <\test_location>
+<\testname>
+<testname=crash02>
+ <description>
+ A signal handler is set up so that in most cases the machine exception
+ generated by the illegal syscall, bad operands, etc in the procedure
+ made up of random data are caught; and another round of randomness may
+ be tried. Eventually a random syscall may corrupt the program or
+ the machine state in such a way that the program must halt. This is
+ a test of the robustness of the hardware/software for instruction
+ fault handling.
+
+ Note: Running this program just a few times, using total CPU time of
+ less than a few seconds SHOULD NOT GIVE YOU ANY CONFIDENCE in system
+ robustness. Having it run for hours, with tens of thousands of cases
+ would be a different thing. It would also make sense to run this
+ stress test at the same time you run other tests, like a multi-user
+ benchmark.
+
+ CAUTION: running this program may crash your system, your disk and all
+ your data along! DO NOT RUN IT ON PRODUCTION SYSTEMS!
+ CONSIDER YOUR DISK FRIED.
+ REMEMBER THE DISCLAIMER PART OF THE LICENSE.
+
+ Running as user nobody and with all your filesystems
+ remounted to readonly may be wise..
+
+ <\description>
+ <test_location>
+ ltp/testcases/misc/crash/crash02.c
+ <\test_location>
+<\testname>
+<testname=f00f>
+ <description>
+ This is a simple test for handling of the pentium f00f bug.
+ It is an example of a catistrophic test case. If the system
+ doesn't correctly handle this test, it will likely lockup.
+
+ <\description>
+ <test_location>
+ ltp/testcases/misc/f00f/f00f.c
+ <\test_location>
+<\testname>
+<testname=abs>
+ <description>
+ Test the basic functionality of the abs() system call.
+
+ <\description>
+ <test_location>
+ ltp/testcases/misc/math/abs
+ <\test_location>
+<\testname>
+<testname=atof>
+ <description>
+ Test the basic functionality of the atof() system call.
+
+ <\description>
+ <test_location>
+ ltp/testcases/misc/math/atof
+ <\test_location>
+<\testname>
+<testname=float>
+ <description>
+ Increase CPUs workload - verify that results of some math functions are stable
+
+ Floating testcases are related to :
+ ----------------------------------
+ - trigonometric (acos, asin, atan, atan2, cos, sin, tan),
+ - Euclidean distance function (hypot),
+ - Computes the natural logarithm of the gamma function (lgamma),
+ - Functions that manipulate floating-point numbers (modf, ldexp, frexp),
+ - exponential and logarithmic functions (exp, log, log10),
+ - hyperbolic (cosh, sinh, tanh),
+ - Bessel (j0, j1, y0, y1),
+ - and power functions (ceil, fabs, floor, fmod, pow, sqrt).
+
+ The testcase is splitted into 5 sets:
+ -------------------------------------
+ float_bessel, float_exp_log, float_iperb, float_power, float_trigo
+
+ <\description>
+ <test_location>
+ ltp/testcases/misc/math/float
+ <\test_location>
+<\testname>
+<testname=fptests>
+ <description>
+ Additional floating point tests.
+
+ <\description>
+ <test_location>
+ ltp/testcases/misc/math/fptests
+ <\test_location>
+<\testname>
+<testname=nextafter>
+ <description>
+ Test basic functionality of nextafter() system call.
+
+ <\description>
+ <test_location>
+ ltp/testcases/misc/math/nextafter
+ <\test_location>
+<\testname>
+<testname=tcore_patch_test_suites>
+ <description>
+ Test suite for multi-thread core dump kernel patch.
+ <\description>
+ <test_location>
+ ltp/testcases/misc/tcore_patch_test_suites
+ <\test_location>
+<\testname>
diff -ruN ltp-full-20090531_orig/doc/testcases/network.txt ltp-full-20090531/doc/testcases/network.txt
--- ltp-full-20090531_orig/doc/testcases/network.txt 2008-06-27 16:53:25.000000000 +0530
+++ ltp-full-20090531/doc/testcases/network.txt 2009-06-19 11:31:29.000000000 +0530
@@ -1,331 +1,570 @@
-dhcpd
------
-dhcpd_tests.sh
-
- Test basic functionality of dhcpd server.
-
-
-ipchains
---------
-ipchains_tests.sh
-
- Test basic functionality of ipchains.
-
-
-iproute
--------
-ip_tests.sh
-
- Test basic functionality of ip command in route2 package
-
-
-ipv6
-----
-echo601
-
- Stresses the inetd/xinetd daemon using the `echo` service.
-
-finger601
-
- test the basic functionality of the `finger` command.
-
-ftp601
-
- test the basic functionality of the `ftp` command.
-
-perf_lan6
-
- Generates LAN traffic using ICMP echo packets.
-
-ping601
-
- test the basic functionality of the `ping` command.
-
-rcp601
-
- test the basic functionality of the `rcp` command.
-
-
-rlogin601
-
- Tests the basic functionality of `rlogin`.
-
-rsh601
-
- test the basic functionality of the `rsh` command.
-
-rwho601
-
- test the basic functionality of the rwhod daemon using the
-
-sendfile601
-
- Copy files from server to client using the sendfile()
- function.
-
-tcpdump6
-
- test the basic functionality of `tcpdump`.
-
-telnet601
-
- Tests the basic functionality of `telnet`.
-
-
-
-multicast
----------
-
-mc_cmds
-
- To determine the stability of the IP Multicast product
- and to verify the accuracy and usablility of IP Multicast
- related publications associated with changes and/or
- additions to command level interfaces for this implementations
- of IP Multicast.
-
-mc_commo
-
- To verify that IP Multicast can be used to send UDP datagrams
- between two or more nodes on the same subnetwork using
- a specific IP Multicast group and a specific port address.
-
-mc_member
-
- To verify that two of the new options for level IPPROTO_IP
- Service Interface allow the list of host group memberships
- to be updated properly in response to the JoinHostGroup and
- LeaveHostGroup requests. To test boundary conditions while
- exercising IP Multicast JoinHostGroup and LeaveHostGroup
- Service Interfaces.
-
-mc_opts
-
- To verify that three of the new options for level IPPROTO_IP
- Service Interface are initially set to the default values as
- defined in the documentation and that each of the new options
- can be set and read properly by the setsockopt and getsockopt
- routines, respectively. To test boundary conditions and to
- generate errors while exercising the IP Multicast Service
- Interface options.
-
-
-
-nfs
----
-fsx-linux
- Created by NeXT Software (Apple Computer, Inc.). This test will
- thrash your NFS filesystem and has uncovered numerous bugs within
- the Linux implementation.
-
-nfs01
-
- Stresses NFS by opening a large number of files on a nfs
- mounted filesystem.
-
-nfs02
-
- Tests NFS copy of various filesizes, file consistency between copies
- and preservation of write/nowrite permissions.
-
-nfs03
- Runs the LTP filesystem test: fs_inod, on an NFS mountpoint.
-
-
-nfslock01
-
- Two processes open FLOCK_IDATA file simultaneously
- each one locks odd and even lines of the file simultaneously
- and fill them with '0's and '1's. After they find eof, the
- datafiles are compared.
-
-nfsstat01
-
- Tests the 'nfsstat' command. This test runs locally, so no
- actual network connection is needed.
-
-nfsstress
-
- This program is designed stress the NFS implimentation.
- Many bugs were uncovered in the AIX operating system
- implimentation of NFS when AIX kernel was built over NFS.
- Source directory on a remote machine (one server many clients)
- NFS-mounted on to a directory on a local machine from which
- the kernel build was initiated. Apparently many defects/bugs
- were uncovered when multiple users tried to build the kernel
- by NFS mounting the kernel source from a remote machine and
- tried to build the kernel on a local machine. AIX build envi-
- ronment is set up to create the object files and executable
- on the local machine.
- This testcase will try to recreate such a senario.
- Spawn N number of threads. Each thread does the following.
- * Create a directory tree.
- * Populate it with ".c" files and makefiles.
- * initate a build. Executable will print hello world when executed
- * clean up all the executables that were created.
- * recurssively remove each subdir and its contents.
- The test is aimed at stressing the NFS client and server.
-
-
-
-rpc/basic_tests
----------------
-
- Tests for SunRPC API
-
-rpc01
-
- Test rpc using file transfers between a client & server
-
-rpcinfo01
-
- Basic test for the `rpcinfo` command.
-
-rup01
-
- Basic test for the `rup` command.
-
-rusers01
-
- Basic test for the `rusers` command.
-
-rpc/rpc-tirpc-full-test-suite
------------------------------
-
- Full test for SunRPC and TI-RPC API
-
-sctp
-----
-accept01-sctp
-
- Verify that accept() returns the proper errno for various failure cases
-
-bind01-sctp-udp/tcp
-
- Verify that bind() returns the proper errno for various failure cases
-
-listen01-sctp-udp/tcp
-
- Verify that listen() returns the proper errno for various failure cases
-
-recv01-sctp-udp/tcp
-
- Verify that recv() returns the proper errno for various failure cases
-
-recvfrom01-sctp-udp/tcp
-
- Verify that recvfrom() returns the proper errno for various failure cases
-
-recvmsg01-sctp-udp/tcp
-
- Verify that recvmsg() returns the proper errno for various failure cases
-
-send01-sctp-udp/tcp
-
- Verify that send() returns the proper errno for various failure cases
-
-sendmsg01-sctp-udp/tcp
-
- Verify that sendmsg() returns the proper errno for various failure cases
-
-sendto01-sctp-udp/tcp
-
- Verify that sendto() returns the proper errno for various failure cases
-
-setsockopt01-sctp-udp/tcp
-
- Verify that setsockopt() returns the proper errno for various failure cases
-
-socket01-sctp-udp/tcp
-
- Verify that socket() returns the proper errno for various failure cases
-
-
-sockets
--------
-ltpSockets.sh
-
- Run basic socket related tests over UDP, TCP, and Multicast.
-
-
-tcp_cmds
---------
-arp01
- Test the basic functionality of `arp`.
-
-echo01
-
- Stresses the inetd/xinetd daemon using the `echo` service.
-
-finger01
-
- test the basic functionality of the `finger` command.
-
-ftp01
-
- test the basic functionality of the `ftp` command.
-
-host01
-
- test the basic functionality of the `host` command.
-
-netstat01
-
- test the basic functionality of the `netstat` command.
-
-perf_lan
-
- Generates LAN traffic using ICMP echo packets.
-
-ping01
-
- test the basic functionality of the `ping` command.
-
-rcp01
-
- test the basic functionality of the `rcp` command.
-
-rdist01
-
- test the basic functionality of the `rdist` command.
-
-rlogin01
-
- Tests the basic functionality of `rlogin`.
-
-rsh01
-
- test the basic functionality of the `rsh` command.
-
-rwho01
-
- test the basic functionality of the rwhod daemon using the
-
-sendfile
-
- Copy files from server to client using the sendfile()
- function.
-
-tcpdump
-
- test the basic functionality of `tcpdump`.
-
-telnet01
-
- Tests the basic functionality of `telnet`.
-
-
-
-traceroute
-----------
-traceroute_tests.sh
-
- Test basic functionality of `traceroute` command.
-
-
-
-xinetd
-------
-xinetd_tests.sh
-
- Test basic functionality of `xinetd` command.
+<testname=dhcpd_tests.sh>
+ <description>
+ Test basic functionality of dhcpd server.
+
+ <\description>
+ <test_location>
+ ltp/testcases/network/dhcpd/dhcpd_tests.sh
+ <\test_location>
+<\testname>
+<testname=ipchains_tests.sh>
+ <description>
+ Test basic functionality of ipchains.
+
+ <\description>
+ <test_location>
+ <\test_location>
+<\testname>
+<testname=ip_tests.sh>
+ <description>
+ Test basic functionality of ip command in route2 package
+
+ <\description>
+ <test_location>
+ ltp/testcases/network/iproute/ip_tests.sh
+ <\test_location>
+<\testname>
+<testname=echo601>
+ <description>
+ Stresses the inetd/xinetd daemon using the `echo` service.
+
+ <\description>
+ <test_location>
+ ltp/testcases/network/ipv6/echo6/echo601
+ <\test_location>
+<\testname>
+<testname=finger601>
+ <description>
+ test the basic functionality of the `finger` command.
+
+ <\description>
+ <test_location>
+ ltp/testcases/network/ipv6/finger6/finger601
+ <\test_location>
+<\testname>
+<testname=ftp601>
+ <description>
+ test the basic functionality of the `ftp` command.
+
+ <\description>
+ <test_location>
+ <\test_location>
+<\testname>
+<testname=perf_lan6>
+ <description>
+ Generates LAN traffic using ICMP echo packets.
+
+ <\description>
+ <test_location>
+ ltp/testcases/network/ipv6/perf_lan6
+ <\test_location>
+<\testname>
+<testname=ping601>
+ <description>
+ test the basic functionality of the `ping` command.
+
+ <\description>
+ <test_location>
+ ltp/testcases/network/ipv6/ping6/ping601
+ <\test_location>
+<\testname>
+<testname=rcp601>
+ <description>
+ test the basic functionality of the `rcp` command.
+
+ <\description>
+ <test_location>
+ <\test_location>
+<\testname>
+<testname=rlogin601>
+ <description>
+ Tests the basic functionality of `rlogin`.
+
+ <\description>
+ <test_location>
+ <\test_location>
+<\testname>
+<testname=rsh601>
+ <description>
+ test the basic functionality of the `rsh` command.
+
+ <\description>
+ <test_location>
+ <\test_location>
+<\testname>
+<testname=rwho601>
+ <description>
+ test the basic functionality of the rwhod daemon using the
+
+ <\description>
+ <test_location>
+ <\test_location>
+<\testname>
+<testname=sendfile601>
+ <description>
+ Copy files from server to client using the sendfile()
+ function.
+
+ <\description>
+ <test_location>
+ ltp/testcases/network/ipv6/sendfile6/sendfile601
+ <\test_location>
+<\testname>
+<testname=tcpdump6>
+ <description>
+ test the basic functionality of `tcpdump`.
+
+ <\description>
+ <test_location>
+ ltp/testcases/network/ipv6/tcpdump6
+ <\test_location>
+<\testname>
+<testname=telnet601>
+ <description>
+ Tests the basic functionality of `telnet`.
+
+ <\description>
+ <test_location>
+ <\test_location>
+<\testname>
+<testname=mc_cmds>
+ <description>
+ To determine the stability of the IP Multicast product
+ and to verify the accuracy and usablility of IP Multicast
+ related publications associated with changes and/or
+ additions to command level interfaces for this implementations
+ of IP Multicast.
+
+ <\description>
+ <test_location>
+ ltp/testcases/network/multicast/mc_cmds
+ <\test_location>
+<\testname>
+<testname=mc_commo>
+ <description>
+ To verify that IP Multicast can be used to send UDP datagrams
+ between two or more nodes on the same subnetwork using
+ a specific IP Multicast group and a specific port address.
+
+ <\description>
+ <test_location>
+ ltp/testcases/network/multicast/mc_commo
+ <\test_location>
+<\testname>
+<testname=mc_member>
+ <description>
+ To verify that two of the new options for level IPPROTO_IP
+ Service Interface allow the list of host group memberships
+ to be updated properly in response to the JoinHostGroup and
+ LeaveHostGroup requests. To test boundary conditions while
+ exercising IP Multicast JoinHostGroup and LeaveHostGroup
+ Service Interfaces.
+
+ <\description>
+ <test_location>
+ ltp/testcases/network/multicast/mc_member
+ <\test_location>
+<\testname>
+<testname=mc_opts>
+ <description>
+ To verify that three of the new options for level IPPROTO_IP
+ Service Interface are initially set to the default values as
+ defined in the documentation and that each of the new options
+ can be set and read properly by the setsockopt and getsockopt
+ routines, respectively. To test boundary conditions and to
+ generate errors while exercising the IP Multicast Service
+ Interface options.
+
+ <\description>
+ <test_location>
+ ltp/testcases/network/multicast/mc_opts
+ <\test_location>
+<\testname>
+<testname=fsx-linux>
+ <description>
+ Created by NeXT Software (Apple Computer, Inc.). This test will
+ thrash your NFS filesystem and has uncovered numerous bugs within
+ the Linux implementation.
+
+ <\description>
+ <test_location>
+ ltp/testcases/network/nfs/fsx-linux
+ <\test_location>
+<\testname>
+<testname=nfs01>
+ <description>
+ Stresses NFS by opening a large number of files on a nfs
+ mounted filesystem.
+
+ <\description>
+ <test_location>
+ ltp/testcases/network/nfs/nfs01
+ <\test_location>
+<\testname>
+<testname=nfs02>
+ <description>
+ Tests NFS copy of various filesizes, file consistency between copies
+ and preservation of write/nowrite permissions.
+
+ <\description>
+ <test_location>
+ ltp/testcases/network/nfs/nfs02
+ <\test_location>
+<\testname>
+<testname=nfs03>
+ <description>
+ Runs the LTP filesystem test: fs_inod, on an NFS mountpoint.
+
+ <\description>
+ <test_location>
+ ltp/testcases/network/nfs/nfs03
+ <\test_location>
+<\testname>
+<testname=nfslock01>
+ <description>
+ Two processes open FLOCK_IDATA file simultaneously
+ each one locks odd and even lines of the file simultaneously
+ and fill them with '0's and '1's. After they find eof, the
+ datafiles are compared.
+
+ <\description>
+ <test_location>
+ ltp/testcases/network/nfs/nfslock01
+ <\test_location>
+<\testname>
+<testname=nfsstat01>
+ <description>
+ Tests the 'nfsstat' command. This test runs locally, so no
+ actual network connection is needed.
+
+ <\description>
+ <test_location>
+ ltp/testcases/network/nfs/nfsstat01
+ <\test_location>
+<\testname>
+<testname=nfsstress>
+ <description>
+ This program is designed stress the NFS implimentation.
+ Many bugs were uncovered in the AIX operating system
+ implimentation of NFS when AIX kernel was built over NFS.
+ Source directory on a remote machine (one server many clients)
+ NFS-mounted on to a directory on a local machine from which
+ the kernel build was initiated. Apparently many defects/bugs
+ were uncovered when multiple users tried to build the kernel
+ by NFS mounting the kernel source from a remote machine and
+ tried to build the kernel on a local machine. AIX build envi-
+ ronment is set up to create the object files and executable
+ on the local machine.
+ This testcase will try to recreate such a senario.
+ Spawn N number of threads. Each thread does the following.
+ * Create a directory tree.
+ * Populate it with ".c" files and makefiles.
+ * initate a build. Executable will print hello world when executed
+ * clean up all the executables that were created.
+ * recurssively remove each subdir and its contents.
+ The test is aimed at stressing the NFS client and server.
+
+ <\description>
+ <test_location>
+ ltp/testcases/network/nfs/nfsstress
+ <\test_location>
+<\testname>
+<testname=rpc01>
+ <description>
+ Tests for SunRPC API
+
+ Test rpc using file transfers between a client & server
+
+ <\description>
+ <test_location>
+ ltp/testcases/network/rpc/basic_tests/rpc01
+ <\test_location>
+<\testname>
+<testname=rpcinfo01>
+ <description>
+ Basic test for the `rpcinfo` command.
+
+ <\description>
+ <test_location>
+ ltp/testcases/network/rpc/basic_tests/rpcinfo/rpcinfo01
+ <\test_location>
+<\testname>
+<testname=rup01>
+ <description>
+ Basic test for the `rup` command.
+
+ <\description>
+ <test_location>
+ ltp/testcases/network/rpc/basic_tests/rup/rup01
+ <\test_location>
+<\testname>
+<testname=rusers01>
+ <description>
+ Basic test for the `rusers` command.
+
+ <\description>
+ <test_location>
+ ltp/testcases/network/rpc/basic_tests/rusers/rusers01
+ <\test_location>
+<\testname>
+<testname=accept01-sctp>
+ <description>
+ Full test for SunRPC and TI-RPC API
+
+ Verify that accept() returns the proper errno for various failure cases
+
+ <\description>
+ <test_location>
+ <\test_location>
+<\testname>
+<testname=bind01-sctp-udp/tcp>
+ <description>
+ Verify that bind() returns the proper errno for various failure cases
+
+ <\description>
+ <test_location>
+ <\test_location>
+<\testname>
+<testname=listen01-sctp-udp/tcp>
+ <description>
+ Verify that listen() returns the proper errno for various failure cases
+
+ <\description>
+ <test_location>
+ <\test_location>
+<\testname>
+<testname=recv01-sctp-udp/tcp>
+ <description>
+ Verify that recv() returns the proper errno for various failure cases
+
+ <\description>
+ <test_location>
+ <\test_location>
+<\testname>
+<testname=recvfrom01-sctp-udp/tcp>
+ <description>
+ Verify that recvfrom() returns the proper errno for various failure cases
+
+ <\description>
+ <test_location>
+ <\test_location>
+<\testname>
+<testname=recvmsg01-sctp-udp/tcp>
+ <description>
+ Verify that recvmsg() returns the proper errno for various failure cases
+
+ <\description>
+ <test_location>
+ <\test_location>
+<\testname>
+<testname=send01-sctp-udp/tcp>
+ <description>
+ Verify that send() returns the proper errno for various failure cases
+
+ <\description>
+ <test_location>
+ <\test_location>
+<\testname>
+<testname=sendmsg01-sctp-udp/tcp>
+ <description>
+ Verify that sendmsg() returns the proper errno for various failure cases
+
+ <\description>
+ <test_location>
+ <\test_location>
+<\testname>
+<testname=sendto01-sctp-udp/tcp>
+ <description>
+ Verify that sendto() returns the proper errno for various failure cases
+
+ <\description>
+ <test_location>
+ <\test_location>
+<\testname>
+<testname=setsockopt01-sctp-udp/tcp>
+ <description>
+ Verify that setsockopt() returns the proper errno for various failure cases
+
+ <\description>
+ <test_location>
+ <\test_location>
+<\testname>
+<testname=socket01-sctp-udp/tcp>
+ <description>
+ Verify that socket() returns the proper errno for various failure cases
+
+ <\description>
+ <test_location>
+ <\test_location>
+<\testname>
+<testname=ltpSockets.sh>
+ <description>
+ Run basic socket related tests over UDP, TCP, and Multicast.
+
+ <\description>
+ <test_location>
+ ltp/testcases/network/sockets/ltpSockets.sh
+ <\test_location>
+<\testname>
+<testname=arp01>
+ <description>
+ Test the basic functionality of `arp`.
+
+ <\description>
+ <test_location>
+ ltp/testcases/network/tcp_cmds/arp/arp01
+ <\test_location>
+<\testname>
+<testname=echo01>
+ <description>
+ Stresses the inetd/xinetd daemon using the `echo` service.
+
+ <\description>
+ <test_location>
+ ltp/testcases/network/tcp_cmds/echo/echo01
+ <\test_location>
+<\testname>
+<testname=finger01>
+ <description>
+ test the basic functionality of the `finger` command.
+
+ <\description>
+ <test_location>
+ ltp/testcases/network/tcp_cmds/finger/finger01
+ <\test_location>
+<\testname>
+<testname=ftp01>
+ <description>
+ test the basic functionality of the `ftp` command.
+
+ <\description>
+ <test_location>
+ ltp/testcases/network/tcp_cmds/ftp/ftp01
+ <\test_location>
+<\testname>
+<testname=host01>
+ <description>
+ test the basic functionality of the `host` command.
+
+ <\description>
+ <test_location>
+ ltp/testcases/network/tcp_cmds/host/host01
+ <\test_location>
+<\testname>
+<testname=netstat01>
+ <description>
+ test the basic functionality of the `netstat` command.
+
+ <\description>
+ <test_location>
+ ltp/testcases/network/tcp_cmds/netstat/netstat01
+ <\test_location>
+<\testname>
+<testname=perf_lan>
+ <description>
+ Generates LAN traffic using ICMP echo packets.
+
+ <\description>
+ <test_location>
+ ltp/testcases/network/tcp_cmds/perf_lan
+ <\test_location>
+<\testname>
+<testname=ping01>
+ <description>
+ test the basic functionality of the `ping` command.
+
+ <\description>
+ <test_location>
+ ltp/testcases/network/tcp_cmds/ping/ping01
+ <\test_location>
+<\testname>
+<testname=rcp01>
+ <description>
+ test the basic functionality of the `rcp` command.
+
+ <\description>
+ <test_location>
+ ltp/testcases/network/tcp_cmds/rcp/rcp01
+ <\test_location>
+<\testname>
+<testname=rdist01>
+ <description>
+ test the basic functionality of the `rdist` command.
+
+ <\description>
+ <test_location>
+ ltp/testcases/network/tcp_cmds/rdist/rdist01
+ <\test_location>
+<\testname>
+<testname=rlogin01>
+ <description>
+ Tests the basic functionality of `rlogin`.
+
+ <\description>
+ <test_location>
+ ltp/testcases/network/tcp_cmds/rlogin/rlogin01
+ <\test_location>
+<\testname>
+<testname=rsh01>
+ <description>
+ test the basic functionality of the `rsh` command.
+
+ <\description>
+ <test_location>
+ ltp/testcases/network/tcp_cmds/rsh/rsh01
+ <\test_location>
+<\testname>
+<testname=rwho01>
+ <description>
+ test the basic functionality of the rwhod daemon using the
+
+ <\description>
+ <test_location>
+ ltp/testcases/network/tcp_cmds/rwho/rwho01
+ <\test_location>
+<\testname>
+<testname=sendfile>
+ <description>
+ Copy files from server to client using the sendfile()
+ function.
+
+ <\description>
+ <test_location>
+ ltp/testcases/network/tcp_cmds/sendfile
+ <\test_location>
+<\testname>
+<testname=tcpdump>
+ <description>
+ test the basic functionality of `tcpdump`.
+
+ <\description>
+ <test_location>
+ ltp/testcases/network/tcp_cmds/tcpdump
+ <\test_location>
+<\testname>
+<testname=telnet01>
+ <description>
+ Tests the basic functionality of `telnet`.
+
+ <\description>
+ <test_location>
+ ltp/testcases/network/tcp_cmds/telnet/telnet01
+ <\test_location>
+<\testname>
+<testname=traceroute_tests.sh>
+ <description>
+ Test basic functionality of `traceroute` command.
+
+ <\description>
+ <test_location>
+ ltp/testcases/network/traceroute/traceroute_tests.sh
+ <\test_location>
+<\testname>
+<testname=xinetd>
+ <description>
+ Test basic functionality of `xinetd` command.
+ <\description>
+ <test_location>
+ ltp/testcases/network/xinetd
+ <\test_location>
+<\testname>
[-- Attachment #3: Type: text/plain, Size: 332 bytes --]
------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing
server and web deployment.
http://p.sf.net/sfu/businessobjects
[-- Attachment #4: Type: text/plain, Size: 155 bytes --]
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
^ permalink raw reply [flat|nested] 10+ messages in thread