[pnfs] OPEN_CONFIRM being used

[William A. (Andy) Adamson]

hi rahul

On 5/31/07, Iyer, Rahul <Rahul.Iyer at netapp.com> wrote:
>
>  Hi Andy,
> I was running the 4.1-sessions tree. I saw an OPEN_CONFIRM being sent by
> the cient. This is a problem as the server shouldn't be setting the
> NFS4_OPEN_RESULT_CONFIRM flag in the result. I haven't changed the client to
> not send OPEN_CONFIRM in v4.1 just to be "nice". I can either:
> 1. Print a warning and send it anyway
> 2. Not send it and cause the open to fail
>
> Either way, the server needs to be changed so that it doesn't set this
> flag.
>


ok - i'll fix it. in general, i need to look at sessions processing of
OPEN/OPEN_CONFIRM/CLOSE/OPENDOWNGRADE/LOCK/UNLOCK seq# and clientid and make
sure we are up to spec.

thanks for the heads-up!

-->Andy

Thanks
> regards
> rahul
>
>
> _______________________________________________
> pNFS mailing list
> pNFS at linux-nfs.org
> http://linux-nfs.org/cgi-bin/mailman/listinfo/pnfs
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://linux-nfs.org/pipermail/pnfs/attachments/20070601/eb8529ed/attachment.htm