LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
	staubach@redhat.com, linux-kernel@vger.kernel.org,
	linux-nfs@vger.kernel.org, trond.myklebust@fys.uio.no,
	linux-fsdevel@vger.kernel.org, viro@zeniv.linux.org.uk,
	hch@lst.de
Subject: Re: [PATCH 1/3] enhanced lookup ESTALE error handling (v3)
Date: Mon, 10 Mar 2008 21:12:09 -0700	[thread overview]
Message-ID: <20080310211209.19a25c75.akpm@linux-foundation.org> (raw)
In-Reply-To: <1205187584.8385.6.camel@nimitz.home.sr71.net>

On Mon, 10 Mar 2008 15:19:44 -0700 Dave Hansen <haveblue@us.ibm.com> wrote:

> On Mon, 2008-03-10 at 23:03 +0100, Miklos Szeredi wrote:
> > > > This is a patch to enhance ESTALE error handling during the
> > > > lookup process.  The error, ESTALE, can occur when out of data
> > > > dentries, stored in the dcache, is used to translate a pathname
> > > > component to a dentry.  When this occurs, the dentry which
> > > > contains the pointer to the inode which refers to the non-existent
> > > > file is dropped from the dcache and then the lookup process
> > > > started again.  Care is taken to ensure that forward process is
> > > > always being made.  If forward process is not detected, then the
> > > > lookup process is terminated and the error, ENOENT, is returned
> > > > to the caller.
> > > 
> > > This collides in non-trivial ways with the always-coming-never-arrives
> > > r-o-bind-mounts patches.
> > > 
> > > I have an old version of those patches in -mm and I believe that Al
> > > is/was/has set up some git tree with these patches and perhaps other stuff.
> 
> Al's tree is here:
> 
> http://git.kernel.org/gitweb.cgi?p=linux/kernel/git/viro/vfs-2.6.git;a=summary
> 
> It's probably best to try and base your patches on top of there.  
> 

Al has a unique versioning scheme which I am not smart enough to
understand, so I'd be reluctant to pick this up without coordinating with
him.

afacit the "b1" branch there is the latest, but it doesn't appear to have
been touched for a couple of weeks.


      reply	other threads:[~2008-03-11  4:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-18 15:36 [PATCH 1/3] enhanced ESTALE error handling Peter Staubach
2008-01-18 16:14 ` Matthew Wilcox
2008-01-18 16:45   ` Peter Staubach
2008-01-18 17:18     ` J. Bruce Fields
2008-01-18 17:32       ` Peter Staubach
2008-02-01 20:57 ` [PATCH 1/3] enhanced lookup ESTALE error handling (v2) Peter Staubach
2008-03-10 20:23   ` [PATCH 1/3] enhanced lookup ESTALE error handling (v3) Peter Staubach
2008-03-10 21:38     ` Andrew Morton
2008-03-10 22:03       ` Miklos Szeredi
2008-03-10 22:19         ` Dave Hansen
2008-03-11  4:12           ` Andrew Morton [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=20080310211209.19a25c75.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=haveblue@us.ibm.com \
    --cc=hch@lst.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=staubach@redhat.com \
    --cc=trond.myklebust@fys.uio.no \
    --cc=viro@zeniv.linux.org.uk \
    --subject='Re: [PATCH 1/3] enhanced lookup ESTALE error handling (v3)' \
    /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

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).