forked from sanyaade-mobiledev/chromium.src
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathdescriptions.tests
2990 lines (1843 loc) · 68.6 KB
/
descriptions.tests
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
personality01
Check that we can set the personality for a process.
personality02
Check that we get EINVAL for a bad personality.
exit01
Check that exit returns the correct values to the waiting parent
exit02
Check that exit flushes output file buffers and closes files upon
exiting
wait02
Basic test for wait(2) system call.
wait401
check that a call to wait4() correctly waits for a child
process to exit
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 until 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
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 notification
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
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.
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).
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.
sendfile02
Testcase to test the basic functionality of the sendfile(2) system call.
sendfile03
Testcase to test that sendfile(2) system call returns appropriate
errnos on error.
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 referring to the same file.
fork11
Test that parent gets a pid from each child when doing wait
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.
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
sockioctl01
Verify that ioctl() on sockets returns the proper errno for various
failure cases
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.
setitimer01
check that a reasonable setitimer() call succeeds.
setitimer02
check that a setitimer() call fails as expected
with incorrect values.
setitimer03
check that a setitimer() call fails as expected
with incorrect values.
float_trigo
increase CPUs workload - verify that results of some math functions are stable
trigonometric (acos, asin, atan, atan2, cos, sin, tan),
hyperbolic (cosh, sinh, tanh),
float_exp_log
increase CPUs workload - verify that results of some math functions are stable
exponential and logarithmic functions (exp, log, log10),
Functions that manipulate floating-point numbers (modf, ldexp, frexp),
Euclidean distance function (hypot),
float_bessel
increase CPUs workload - verify that results of some math functions are stable
Bessel (j0, j1, y0, y1),
Computes the natural logarithm of the gamma function (lgamma),
fload_power
increase CPUs workload - verify that results of some math functions are stable
Computes sqrt, power, fmod
float_iperb
increase CPUs workload - verify that results of some math functions are stable
pth_str01
Creates a tree of threads
pth_str02
Creates n threads
pth_str03
Creates a tree of threads does calculations, and
returns result to parent
asyncio02
Write/close flushes data to the file.
fpathconf
Basic test for fpathconf(2)
gethostid01
Basic test for gethostid(2)
pathconf01
Basic test for pathconf(2)
setpgrp01
Basic test for the setpgrp(2) system call.
setpgrp02
Testcase to check the basic functionality of the setpgrp(2) syscall.
ulimit01
Basic test for the ulimit(2) system call.
mmstress
Performs General Stress with Race conditions
mmap1
Test the LINUX memory manager. The program is aimed at
stressing the memory manager by simultaneous map/unmap/read
by light weight processes, the test is scheduled to run for
a minimum of 24 hours.
mmap2
Test the LINUX memory manager. The program is aimed at
stressing the memory manager by repeated 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 repeated map/write/unmap
of file/memory of random size (maximum 1GB) this is done by
multiple processes.
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.
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 requested 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.
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
brk01
Test the basic functionality of brk.
sbrk01
Basic test for the sbrk(2) system call.
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.
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
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.
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
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
link02
Basic test for link(2)
link03
Multi links tests
link04
Negative test cases for link(2)
link05
Multi links (EMLINK) negative test
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.
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 create a symbolic link of an existing
object name path.
symlink05
Verify that, symlink will succeed to create a symbolic link of an
non-existing object name path.
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.
linktest
Regression test for max links per file
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.
mkdir01
Basic errno test for mkdir(2)
mkdir02
This test will verify that new directory created
by mkdir(2) inherits 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.
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 existence of a file if
search access is permitted on the pathname of the specified file.
access06
EFAULT error testing for access(2).
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.
pipeio
This tool can be used to beat on system or named pipes.
See the help() function below for user information.
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.
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
The application creates several threads using pthread_create().
One thread performs a semop() with the SEM_UNDO flag set. The
change in semaphore value performed by that semop should be
"undone" only when the last pthread exits.
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