[pnfs] [PATCH 9/9] pnfs client prevent race in sequence slot

[Trond Myklebust]

On Thu, 2007-09-27 at 17:38 +0200, Benny Halevy wrote:

> I'm afraid there might be more into that. For example, if the 
> interrupted rpc was stateid changing
> you have to process the reply to stay in sync with the server so in 
> general I still think the client must process
> the reply regardless of whether whoever generated the rpc is waiting for 
> it or not.  This means that
> if an rpc is interrupted we need to return -EINTR upstream and postpone 
> the processing
> of the rpc reply as if it was an async rpc even if it started as 
> synchronous rather than try to second
> guess the server by probing it. (it could have been easier if there was 
> a way to officially try to cancel
> an outstanding rpc...)

That should not be a problem if you guys have followed the existing
prescription of always using asynchronous RPC calls for stateful
operations. Those are always guaranteed to complete.

Normally, the only case we have to worry about is the synchronous calls.

Trond