Re: [PATCH 0/3] enhanced ESTALE error handling

[Peter Staubach]

Chuck Lever wrote:
> Hi Peter-
>
> On Jan 18, 2008, at 10:35 AM, Peter Staubach wrote:
> > Hi.
> >
> > Here is a patch set which modifies the system to enhance the
> > ESTALE error handling for system calls which take pathnames
> > as arguments.
>
> The VFS already handles ESTALE.
>
> If a pathname resolution encounters an ESTALE at any point, the 
> resolution is restarted exactly once, and an additional flag is passed 
> to the file system during each lookup that forces each component in 
> the path to be revalidated on the server.  This has no possibility of 
> causing an infinite loop.
>
> Is there some part of this logic that is no longer working? 

The VFS does not fully handle ESTALE.  An ESTALE error can occur
during the second pathname resolution attempt.  There are lots of
reasons, some of which are the 1 second resolution from some file
systems on the server and the window in between the revalidation
and the actual use of the file handle associated with each
dentry/inode pair.

Also, there was no support for ESTALE errors which occur during
subsequent operations to the pathname resolution process.  For
example, during a mkdir(2) operation, the ESTALE can occur from
the over the wire MKDIR operation after the LOOKUP operations
have all succeeded.

   Thanx...

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