From: Steve Dickson <SteveD@redhat.com>
To: trond.myklebust@fys.uio.no
Cc: nfs@lists.sourceforge.net, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [NFS] [PATCH] mmap corruption
Date: Mon, 07 Apr 2003 13:39:31 -0400 [thread overview]
Message-ID: <3E91B7D3.30108@RedHat.com> (raw)
In-Reply-To: 16017.37263.648356.201846@charged.uio.no
Trond Myklebust wrote:
>However, I still stand by my statement that nfs_wb_all() is supposed
>to ensure that *all* pending writes have been cleared.
>The only explanation for npages != 0 is if
>
> a) an error occurred with nfs_wb_all() (we should perhaps test the
> return value of nfs_wb_all() there). Under normal circumstances,
> an error should only occur if you're using soft mounts, though.
>
I have checked the return value and its not failing... The would be too
easy... :-)
SteveD.
prev parent reply other threads:[~2003-04-07 17:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-04 19:20 [NFS] [PATCH] mmap corruption Steve Dickson
2003-04-04 22:01 ` Trond Myklebust
2003-04-05 16:47 ` Steve Dickson
2003-04-06 12:30 ` Trond Myklebust
2003-04-07 14:00 ` Steve Dickson
2003-04-07 14:56 ` Trond Myklebust
2003-04-07 17:39 ` Steve Dickson [this message]
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=3E91B7D3.30108@RedHat.com \
--to=steved@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nfs@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox