The problem is noticed only for these 2 tests lstat01A_64 and stat04_64. Analysis of the problem showed that these tests are called from runtest/syscall file. The problem is noticed because the symlink01.c file doesn't have implementation to take care lstat01A_64 and stat04_64 arguments that are passed in the file runtest/syscall. Solution: Simple solution is to remove lines.
lstat01A_64 symlink01 -T lstat01_64
stat04_64 symlink01 -T stat04_64
from runtest/syscall.
Other option is to provide feature in symlink01.c so that it can execute these tests successfully. I worked on one such patch. Please have a look. This runs same tests for lstat01A_64 and stat04_64 as is run for lstat01 and stat04 respectively. Signed-Off-By: Sharyathi Nagesh <sharyath@in.ibm.com>.
diff --git a/runtest/syscalls b/runtest/syscalls
index 10dba79..45b64e4 100644
--- a/runtest/syscalls
+++ b/runtest/syscalls
@@ -472,7 +472,7 @@
lseek10 lseek10
lstat01A symlink01 -T lstat01
-#lstat01A_64 symlink01 -T lstat01_64
+lstat01A_64 symlink01 -T lstat01_64
lstat01 lstat01
lstat01_64 lstat01_64
lstat02 lstat02
@@ -1020,7 +1020,7 @@
stat03 stat03
stat03_64 stat03_64
stat04 symlink01 -T stat04
-#stat04_64 symlink01 -T stat04_64
+stat04_64 symlink01 -T stat04_64
stat05 stat05
stat05_64 stat05_64
stat06 stat06