Hi Manas, Thanks for bringing this to attention. Indeed the tests in LTP failed. I updated with the reference you provided. The tests should pass now. But i retained some information files from the older release. This will not be a hindrance in your testing. Please verify these once again from May release. (http://ltp.cvs.sourceforge.net/ltp/ltp/testcases/network/nfsv4/locks/)
Regards-- Subrata On Thu, 2008-05-22 at 19:40 +0530, Manas K Nayak wrote: > > > > > > > Hi Subrata, > > I was trying to do lock tests from ltp-testsuite and noticed some > backtrace. > I followed the following way to run the local lock test on x86_64 bit m/c > (HS21) with RHEL5.2: > > 1) Build and Install latest ltp-testsuite. > 2) go to ltp-full-20080430/testcases/network/nfsv4/ > 3) Now issue make here > 4) cd locks > 5) create and mount any partition to a directory. (say /NEW here mounted on > ext3 filesystem type) > 6) create a testfile in mounted filesystem > 7) now run the test like below: > ./locktests -n 50 -f /NEW/testfile > 8) Now you will see the backtrace as below; > > Init > process initalization > .................................................................................................... > -------------------------------------- > > TEST : TRY TO WRITE ON A READ > LOCK:================================================== > TEST : TRY TO WRITE ON A WRITE > LOCK:================================================== > TEST : TRY TO READ ON A READ > LOCK:================================================== > TEST : TRY TO READ ON A WRITE > LOCK:================================================== > TEST : TRY TO SET A READ LOCK ON A READ > LOCK:================================================== > TEST : TRY TO SET A WRITE LOCK ON A WRITE > LOCK:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx > TEST : TRY TO SET A WRITE LOCK ON A READ > LOCK:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx > TEST : TRY TO SET A READ LOCK ON A WRITE > LOCK:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx > TEST : TRY TO READ LOCK THE WHOLE FILE BYTE BY BYTE:*** glibc detected *** > ./locktests: free(): invalid next size (fast): 0x000000000f741610 *** > ======= Backtrace: ========= > /lib64/libc.so.6[0x33c9671634] > /lib64/libc.so.6(cfree+0x8c)[0x33c9674c5c] > ./locktests[0x401e4d] > ./locktests[0x402914] > /lib64/libc.so.6(__libc_start_main+0xf4)[0x33c961d8b4] > ./locktests[0x400cc9] > ======= Memory map: ======== > 00400000-00404000 r-xp 00000000 08:02 886344 > /root/ltp-full-20080430/testcases/network/nfsv4/locks/locktests > 00604000-00605000 rw-p 00004000 08:02 886344 > /root/ltp-full-20080430/testcases/network/nfsv4/locks/locktests > 0f740000-0f761000 rw-p 0f740000 00:00 0 > 33c9200000-33c921a000 r-xp 00000000 08:02 3834154 > /lib64/ld-2.5.so > 33c941a000-33c941b000 r--p 0001a000 08:02 3834154 > /lib64/ld-2.5.so > 33c941b000-33c941c000 rw-p 0001b000 08:02 3834154 > /lib64/ld-2.5.so > 33c9600000-33c974a000 r-xp 00000000 08:02 3834156 > /lib64/libc-2.5.so > 33c974a000-33c9949000 ---p 0014a000 08:02 3834156 > /lib64/libc-2.5.so > 33c9949000-33c994d000 r--p 00149000 08:02 3834156 > /lib64/libc-2.5.so > 33c994d000-33c994e000 rw-p 0014d000 08:02 3834156 > /lib64/libc-2.5.so > 33c994e000-33c9953000 rw-p 33c994e000 00:00 0 > 33ca200000-33ca215000 r-xp 00000000 08:02 3834159 > /lib64/libpthread-2.5.so > 33ca215000-33ca414000 ---p 00015000 08:02 3834159 > /lib64/libpthread-2.5.so > 33ca414000-33ca415000 r--p 00014000 08:02 3834159 > /lib64/libpthread-2.5.so > 33ca415000-33ca416000 rw-p 00015000 08:02 3834159 > /lib64/libpthread-2.5.so > 33ca416000-33ca41a000 rw-p 33ca416000 00:00 0 > 33d7c00000-33d7c0d000 r-xp 00000000 08:02 3834024 > /lib64/libgcc_s-4.1.2-20080102.so.1 > 33d7c0d000-33d7e0d000 ---p 0000d000 08:02 3834024 > /lib64/libgcc_s-4.1.2-20080102.so.1 > 33d7e0d000-33d7e0e000 rw-p 0000d000 08:02 3834024 > /lib64/libgcc_s-4.1.2-20080102.so.1 > 2b9be5067000-2b9be5069000 rw-p 2b9be5067000 00:00 0 > 2b9be5082000-2b9be5085000 rw-p 2b9be5082000 00:00 0 > 2b9be8000000-2b9be8021000 rw-p 2b9be8000000 00:00 0 > 2b9be8021000-2b9bec000000 ---p 2b9be8021000 00:00 0 > 7fffc5a2e000-7fffc5a43000 rw-p 7fffc5a2e000 00:00 0 > [stack] > ffffffffff600000-ffffffffffe00000 ---p 00000000 00:00 0 > [vdso] > Aborted > > > While searching in google for more information on locktests ,got a > locktest testsuite from following opensource link, > http://nfsv4.bullopensource.org/tools/tests/locktest.php > I have attached the tar file of locktest testsuite here for your reference. > > (See attached file: locktests.tar.gz) > > I executed the above opensource locktests and it is running fine.Please see > the execution results as below; > > [EMAIL PROTECTED] locks]# ./locktests -n 50 -f /NEW/testfile > Init > process initalization > ................................................................................................... > -------------------------------------- > > TEST : TRY TO WRITE ON A READ > LOCK:.================================================== > TEST : TRY TO WRITE ON A WRITE > LOCK:================================================== > TEST : TRY TO READ ON A READ > LOCK:================================================== > TEST : TRY TO READ ON A WRITE > LOCK:================================================== > TEST : TRY TO SET A READ LOCK ON A READ > LOCK:================================================== > TEST : TRY TO SET A WRITE LOCK ON A WRITE > LOCK:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx > TEST : TRY TO SET A WRITE LOCK ON A READ > LOCK:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx > TEST : TRY TO SET A READ LOCK ON A WRITE > LOCK:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx > TEST : TRY TO READ LOCK THE WHOLE FILE BYTE BY > BYTE:================================================== > TEST : TRY TO WRITE LOCK THE WHOLE FILE BYTE BY > BYTE:================================================== > > process number : 50 > process number running test successfully : > 50 process of 50 successfully ran test : WRITE ON A READ LOCK > 50 process of 50 successfully ran test : WRITE ON A WRITE LOCK > 50 process of 50 successfully ran test : READ ON A READ LOCK > 50 process of 50 successfully ran test : READ ON A WRITE LOCK > 50 process of 50 successfully ran test : SET A READ LOCK ON A READ LOCK > 50 process of 50 successfully ran test : SET A WRITE LOCK ON A WRITE LOCK > 50 process of 50 successfully ran test : SET A WRITE LOCK ON A READ LOCK > 50 process of 50 successfully ran test : SET A READ LOCK ON A WRITE LOCK > 50 process of 50 successfully ran test : READ LOCK THE WHOLE FILE BYTE BY > BYTE > 50 process of 50 successfully ran test : WRITE LOCK THE WHOLE FILE BYTE BY > BYTE > > > We have "locktests-2.tar.gz" file in our ltp testsuite and it is giving > "back trace" and the opensource locktest (locktests.tar.gz ,which I have > attached in mail) is execuing fine. > So, I am not sure which one is newer and whether we can raise bug on > existing locktests in ltp ? > If the locktests in ltp is older ,then can we replace that with the > testsuite I found? > Or, > Can we make any patch for the existing ltp locktest by comparing both the > lock tests testsuite ? > > Thanks & Regards, > > Manas Kumar Nayak ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Ltp-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ltp-list
