From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: peter.staubach@emc.com
Cc: bfields@fieldses.org, bjschuma@netapp.com, linux-nfs@vger.kernel.org
Subject: RE: [PATCH 3/3] NFS: Detect loops in a readdir due to bad cookies
Date: Wed, 23 Mar 2011 14:48:35 -0400 [thread overview]
Message-ID: <1300906115.11677.58.camel@lade.trondhjem.org> (raw)
In-Reply-To: <5E6794FC7B8FCA41A704019BE3C70E8B0693F05F@MX31A.corp.emc.com>
On Wed, 2011-03-23 at 14:42 -0400, peter.staubach@emc.com wrote:
> Although I think that it is a good thing to protect the client against broken servers, it does seem like the right solution is to get the server fixed...
Don't get me wrong: I fully agree with that!
The reason for wanting this code is to cut down on the amount of
debugging we have to do in order to detect those broken servers.
Detecting duplicate cookies in a wireshark trace can be very
time-consuming if you are dealing with a 10^6-entry directory.
--
Trond Myklebust
Linux NFS client maintainer
NetApp
Trond.Myklebust@netapp.com
www.netapp.com
next prev parent reply other threads:[~2011-03-23 18:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-23 17:39 [PATCH 3/3] NFS: Detect loops in a readdir due to bad cookies Bryan Schumaker
2011-03-23 18:10 ` peter.staubach
2011-03-23 18:17 ` Trond Myklebust
2011-03-23 18:11 ` Trond Myklebust
2011-03-23 18:25 ` J. Bruce Fields
2011-03-23 18:34 ` Trond Myklebust
2011-03-23 18:42 ` peter.staubach
2011-03-23 18:48 ` Trond Myklebust [this message]
2011-03-23 21:27 ` NeilBrown
2011-03-23 21:36 ` Daniel.Muntz
2011-03-23 21:55 ` NeilBrown
2011-03-23 18:43 ` 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=1300906115.11677.58.camel@lade.trondhjem.org \
--to=trond.myklebust@netapp.com \
--cc=bfields@fieldses.org \
--cc=bjschuma@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=peter.staubach@emc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox