All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: xurui <xur@nanjing-fnst.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: Some uncomformity between the realization of the RHEL5Beta1 and the RFC1813
Date: Tue, 31 Oct 2006 21:50:52 -0500	[thread overview]
Message-ID: <20061101025052.GA32052@fieldses.org> (raw)
In-Reply-To: <008001c6fd5f$2c350330$8904a8c0@xurui>

On Wed, Nov 01, 2006 at 10:41:03AM +0800, xurui wrote:
>  struct COMMIT3args { nfs_fh3    file; offset3    offset; count3
>  count; };
...
>  
> 
> When we send the package with the sum of the augment count and offset
> larger than the file size ,which will lead to the overflow ,we assumed
> that nfs server will return fail message,

Why do you assume that?

That doesn't sound like the right behavior to me.  What if the file has
been truncated on the server without the client's knowledge?  Isn't it
better in that case to flush out whatever range remains instead of
failing the commit?

--b.

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2006-11-01  2:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-01  2:41 Some uncomformity between the realization of the RHEL5Beta1 and the RFC1813 xurui
2006-11-01  2:50 ` J. Bruce Fields [this message]
2006-11-01  3:40   ` Some uncomformity between the realization of the kernel " xurui
2006-11-01 14:21     ` Peter Staubach

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20061101025052.GA32052@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=nfs@lists.sourceforge.net \
    --cc=xur@nanjing-fnst.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.