Hi,
Same issue is happening with statfs02_64. In normal system statfs call is there.
chown("/tmp/staQ9BKAG", 4294967295, 0) = 0
chmod("/tmp/staQ9BKAG", 0777) = 0
chdir("/tmp/staQ9BKAG") = 0
creat("testfile.21255", 0444) = 3
mmap(NULL, 1, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, 0, 0) = 0x7fc13e72c000
statfs("testfile.21255/testfile.21255", 0x609520) = -1 ENOTDIR (Not a directory)
fstat(1, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 4), ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7fc13e72b000
write(1, "statfs02 1 TPASS : expecte"..., 73statfs02 1 TPASS :
expected failure - errno = 20 : Not a directory
) = 73
statfs("testdir.statfs.21255", 0x609520) = -1 ENOENT (No such file or directory)
write(1, "statfs02 2 TPASS : expecte"..., 82statfs02 2 TPASS :
expected failure - errno = 2 : No such file or directo
) = 82
statfs("abcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstmnopqrstuvwxyzabcdefghijklmnopqrstmnopqrstuvwxyzaghijklmnopqrstmnopqrstuvwxyzabcdefghijklmnopqrstmnopqrstuvwxyz",
0x609520) = -1 ENAMETOOLONG (File name too long)
write(1, "statfs02 3 TPASS : expecte"..., 76statfs02 3 TPASS :
expected failure - errno = 36 : File name too long
) = 76
statfs("", 0x609520) = -1 EFAULT (Bad address)
write(1, "statfs02 4 TPASS : expecte"..., 69statfs02 4 TPASS :
expected failure - errno = 14 : Bad address
) = 69
Where as in test system the following is output.
chown("/tmp/stagqkjbD", -1, 501) = 0
chmod("/tmp/stagqkjbD", 0777) = 0
chdir("/tmp/stagqkjbD") = 0
open("testfile.15374", O_WRONLY|O_CREAT|O_TRUNC|O_LARGEFILE, 0444) = 3
mmap(NULL, 1, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, 0, 0) = 0x5557e73000
fstat(1, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 0), ...}) = 0
mmap(NULL, 65536, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x555801d000
write(1, "statfs02 1 TFAIL : call su"..., 53statfs02 1 TFAIL : call
succeeded unexpectedly
) = 53
write(1, "statfs02 2 TFAIL : call su"..., 53statfs02 2 TFAIL : call
succeeded unexpectedly
) = 53
write(1, "statfs02 3 TFAIL : call su"..., 53statfs02 3 TFAIL : call
succeeded unexpectedly
) = 53
statfs is not there in strace output. Can you please tell me what can be the
reason for strace not showing those functions?
I will try to check the system with D_FILE_OFFSET_BITS and as well as
disassembly code for further analysis.
Thanks and Regards
Ajoy
-----Original Message-----
From: chru...@suse.cz [mailto:chru...@suse.cz]
Sent: Monday, June 23, 2014 7:39 PM
To: Ajoymon Joseph
Cc: Jan Stancek; ltp-list@lists.sourceforge.net
Subject: Re: [LTP] fstatfs02 issue on mips64
Hi!
> I am not seeing fstatfs call itself when comparing the system call. I
> hope this is the reason?
That is strange but I would not call this to be the reason for the test
fail.
> Also fstatfs02 was working fine. Only fstatfs02_64 was having the
> issue. I saw in ../utils/newer_64.mk makefile. It will be good if you
> tell little more about the 64 here.
The difference is that the _64 testcases are compiled with
-D_FILE_OFFSET_BITS=64 so it's possible that there is something wrong
with large file support on your platform.
--
Cyril Hrubis
chru...@suse.cz
L&T Technology Services Ltd
www.LntTechservices.com<http://www.lnttechservices.com/>
This Email may contain confidential or privileged information for the intended
recipient (s). If you are not the intended recipient, please do not use or
disseminate the information, notify the sender and delete it from your system.
------------------------------------------------------------------------------
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing & Easy Data Exploration
http://p.sf.net/sfu/hpccsystems
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
