linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Matt W. Benjamin" <matt@linuxbox.com>
To: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: Boaz Harrosh <bharrosh@panasas.com>,
	linux-nfs <linux-nfs@vger.kernel.org>,
	Ganesha NFS List <nfs-ganesha-devel@lists.sourceforge.net>
Subject: Re: unlink within an open directory stream
Date: Mon, 26 Mar 2012 15:29:15 -0400 (EDT)	[thread overview]
Message-ID: <923219433.84.1332790155474.JavaMail.root@thunderbeast.private.linuxbox.com> (raw)
In-Reply-To: <1598378492.82.1332790088063.JavaMail.root@thunderbeast.private.linuxbox.com>

Hi,

----- "Trond Myklebust" <Trond.Myklebust@netapp.com> wrote:

> On Mon, 2012-03-26 at 14:55 -0400, Matt W. Benjamin wrote:
> > Hi,
> > 
> > Boaz:  we do not any longer send a readdir index.  We do send a
> cookieverf.
> 
> Uhh... That would be so broken, that I can't imagine that is true...

I think you're misreading my statement.  My intended meaning had to do with Ganesha's generator
for the cookies themselves.  It's not relevant.

> 
> > Fist of all, I haven't established that the issue we're actually
> observing is caused
> > by the Linux client sending old cookies to readdir(something). 
> However, if it is,
> > it's in no way better to try to make cookies "more persistent."  Nor
> should the Linux
> > client be expecting it.  The assumption is simply flawed.  The
> protocol introduced
> > cookie verifier (a LONG time ago) for a reason.
> 
> Bullshit... The cookie verifier is unimplementable. Feel free to try
> or
> to show me an implementation that works. However I refuse to waste
> any
> more of my time trying to make that crap work, having already wasted
> several months of my life doing just that.

There must be something I'm missing here, but ok.

> 
> -- 
> Trond Myklebust
> Linux NFS client maintainer
> 
> NetApp
> Trond.Myklebust@netapp.com
> www.netapp.com

-- 
Matt Benjamin
The Linux Box
206 South Fifth Ave. Suite 150
Ann Arbor, MI  48104

http://linuxbox.com

tel. 734-761-4689
fax. 734-769-8938
cel. 734-216-5309

       reply	other threads:[~2012-03-26 19:29 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1598378492.82.1332790088063.JavaMail.root@thunderbeast.private.linuxbox.com>
2012-03-26 19:29 ` Matt W. Benjamin [this message]
     [not found] <209745840.4.1332606289405.JavaMail.root@thunderbeast.private.linuxbox.com>
2012-03-24 16:34 ` unlink within an open directory stream Matt W. Benjamin
2012-03-24 16:44   ` Myklebust, Trond
2012-03-24 16:53     ` Matt W. Benjamin
2012-03-24 17:12       ` Myklebust, Trond
2012-03-24 17:43         ` Matt W. Benjamin
2012-03-26 18:17         ` Boaz Harrosh
2012-03-26 18:25           ` Myklebust, Trond
2012-03-26 18:43             ` Boaz Harrosh
2012-03-26 18:55               ` Matt W. Benjamin
2012-03-26 19:01                 ` Myklebust, Trond
2012-03-26 19:07                 ` Boaz Harrosh
2012-03-30 15:24                 ` Peter Staubach
2012-03-30 15:46                   ` Myklebust, Trond
2012-03-30 16:46                     ` Peter Staubach
2012-03-30 17:10                     ` Matt W. Benjamin
2012-03-30 20:17           ` Jeff Layton
2012-04-04 15:35           ` Jeff Layton
2012-04-05  8:45             ` Benny Halevy

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=923219433.84.1332790155474.JavaMail.root@thunderbeast.private.linuxbox.com \
    --to=matt@linuxbox.com \
    --cc=Trond.Myklebust@netapp.com \
    --cc=bharrosh@panasas.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=nfs-ganesha-devel@lists.sourceforge.net \
    /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;
as well as URLs for NNTP newsgroup(s).