linux-kernel - Re: LTP ustat01 test fails on NFSROOT

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <2B2C1270-60FB-4830-A62C-D0357D2E1FB3@kernel.crashing.org>
Date:	Thu, 25 Oct 2007 10:59:53 -0500
From:	Kumar Gala <galak@...nel.crashing.org>
To:	Trond Myklebust <trond.myklebust@....uio.no>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	nfs@...ts.sourceforge.net, neilb@...e.de, bfields@...ldses.org,
	chuck.lever@...cle.com
Subject: Re: LTP ustat01 test fails on NFSROOT


On Oct 24, 2007, at 12:05 AM, Kumar Gala wrote:

>
> On Oct 23, 2007, at 8:21 PM, Trond Myklebust wrote:
>
>>
>> On Tue, 2007-10-23 at 17:52 -0500, Kumar Gala wrote:
>>> I'm looking into an issue with LTP's ustat01 & ustat02 tests in  
>>> which
>>> they report the following:
>>>
>>> ustat01     1  FAIL  :  ustat(2) failed and setthe errno to 116 :
>>> Stale NFS file handle
>>> ustat02     2  FAIL  :  ustat(2) failed to produce expected error;
>>> 14, errno: EFAULT and got 116
>>>
>>> It appears sometime between 2.6.21 and 2.6.22-rc1 some changes to  
>>> NFS
>>> got introduced that cause this.
>>>
>>> was wondering about any ideas while I try to debug what's going on.
>>>
>>> thanks
>>>
>>> - k
>>
>> I'm seeing zero problems with the latest checkouts from Linus' git  
>> tree.
>> Mind giving us some more details?
>
> I tried 2.6.24-rc1 w/the same result.
>
> The system is a 32-bit PPC embedded board that we mounting the  
> rootfs over nfs on.
>
> The defconfig is arch/powerpc/configs/mpc8641_hpcn_defconfig
>
>> 'strace' output would be useful, as would the standard NFS list of
>> client mount options, server export options, details on how your
>> exported partition is set up on the server, etc...
>
> strace:
>
> stat64("/", {st_dev=makedev(0, 14), st_ino=58821800,  
> st_mode=S_IFDIR|0775, st_nlink=18, st_uid=500, st_gid=500,  
> st_blksize=4096, st_blocks=8, st_size=4096,  
> st_atime=2007/10/23-22:43:30, st_mtime=2007/10/18-19:51:19,  
> st_ctime=2007/10/18-19:51:19}) = 0
> ustat(0xe, 0x1001a008)                  = -1 ESTALE (Stale NFS file  
> handle)
> fstat64(1, {st_dev=makedev(0, 14), st_ino=58821964, st_mode=S_IFCHR| 
> 0600, st_nlink=1, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=0,  
> st_rdev=makedev(4, 64), st_atime=2007/10/16-18:32:59,  
> st_mtime=2007/10/16-18:32:59, st_ctime=2007/10/24-05:03:34}) = 0
>
>
> Info on the server:
>
> [root@...ky ~]# exportfs -v
> /               <world> 
> (rw,async,wdelay,no_root_squash,no_subtree_check)
> [root@...ky ~]# uname -a
> Linux ducky.am.freescale.net 2.6.22.5-76.fc7 #1 SMP Thu Aug 30  
> 13:04:34 EDT 2007 ppc64 ppc64 ppc64 GNU/Linux
>
> On the host system:
>
> (not sure how to get client mount options, mount reports:
>
> %root% on / type unknown (rw)
>
> -sh-2.05b# cat /proc/cmdline
> root=/dev/nfs rw nfsroot=192.168.1.15:/home/galak/ltib-joust-8572/ 
> rootfs  
> ip=192.168.1.147:192.168.1.15:192.168.1.1:255.255.254.0:rocky:eth0:off 
>  console=ttyS0,115200
>
> If there is some other info that would be useful please let me know.

any ideas?  any other debug info needed?

- k
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/