From: Doug Hughes <doug-rDJHdQPhaF8@public.gmane.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-nfs@vger.kernel.org,
bugme-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r@public.gmane.org
Subject: Re: [Bugme-new] [Bug 11448] New: NFS client has inconsistent write flushing to non-linux serversa
Date: Fri, 29 Aug 2008 08:54:43 -0400 [thread overview]
Message-ID: <48B7F193.6040606@will.to> (raw)
In-Reply-To: <20080828132753.08bfe05f.akpm@linux-foundation.org>
confirmed that this bug is present in same way in 2.6.26 using default
ASYNC NFS, but so far does not exhibit when sync mount option is used.
next prev parent reply other threads:[~2008-08-29 12:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-11448-10286@http.bugzilla.kernel.org/>
[not found] ` <bug-11448-10286-V0hAGp6uBxO456/isadD/XN4h3HLQggn@public.gmane.org/>
2008-08-28 20:27 ` [Bugme-new] [Bug 11448] New: NFS client has inconsistent write flushing to non-linux serversa Andrew Morton
2008-08-28 20:33 ` Doug Hughes
2008-08-29 12:54 ` Doug Hughes [this message]
2008-08-29 17:08 ` J. Bruce Fields
2008-08-29 17:14 ` Peter Staubach
2008-08-29 17:23 ` Doug Hughes
[not found] ` <48B83091.7060800-rDJHdQPhaF8@public.gmane.org>
2008-08-29 17:53 ` Peter Staubach
2008-08-29 18:27 ` Doug Hughes
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=48B7F193.6040606@will.to \
--to=doug-rdjhdqphaf8@public.gmane.org \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r@public.gmane.org \
--cc=linux-nfs@vger.kernel.org \
/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