Re: nfs_refresh_inode: inode number mismatch with 2.4.0test1-ac15

From: Trond Myklebust (trond.myklebust@fys.uio.no)
Date: Mon Jun 12 2000 - 16:28:23 EST


>>>>> Russell King <rmk@arm.linux.org.uk> writes:

> I'm still running into NFS client problems on 2.4.0-test1-ac15
> running against a 2.2.14 knfsd server. The system is stable
> with
> 2.2.14 NFS client running against 2.2.14 knfsd server.

> In this particular setup, device 0x305 is only used by one
> client. (It contains the NFS export for the root-NFS client).

> It normally ends up with complaints about inode number
> mismatches from the 2.4.0 client, and the occasional EIO error.

What's your client setup? Is it ARM/i386, SMP,...?

For SMP machines I think we do have a problem with
nfs_refresh_inode(). There I suspect there is a race (again) due to
the removal of the lock_kernel() stuff in
nfs_file_{read,mmap,write}().

Cheers,
  Trond

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



This archive was generated by hypermail 2b29 : Thu Jun 15 2000 - 21:00:26 EST