All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Lord <lord@sgi.com>
To: Jan Harkes <jaharkes@cs.cmu.edu>
Cc: Alexander Viro <viro@math.psu.edu>, Chris Mason <mason@suse.com>,
	linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH/RFC] Replacing iget4/read_inode2 with icreate
Date: 30 Apr 2002 11:29:21 -0500	[thread overview]
Message-ID: <1020184161.7528.5.camel@jen.americas.sgi.com> (raw)
In-Reply-To: <20020430161415.GA23998@ravel.coda.cs.cmu.edu>

On Tue, 2002-04-30 at 11:14, Jan Harkes wrote:
> On Tue, Apr 30, 2002 at 10:54:06AM -0500, Steve Lord wrote:
> > May be a little soon to remove iget4 - you left one caller, nfs is still
> > there in __nfs_fhget. This is the code which will get removed once
> > filesystems have switched to the new method I think. I am booting an
> > XFS kernel with this code now.
> 
> Actually, it looks like NFS uses this itself because 'v3' has 64-bit
> inode numbers.

Should have realized that when I saw the code in the client not the
server.

> 
> Fix should be simple, something like the following. In fact NFS seems to
> use it's own test to track newly created inodes, which can be replaced
> with checking inode->i_state & I_NEW.
> 

NFS is up and running with the combo of the two patches now, I only
have V2 servers setup here though.

Thanks,

Steve



  reply	other threads:[~2002-04-30 16:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-29 23:24 [PATCH/RFC] Replacing iget4/read_inode2 with icreate Jan Harkes
2002-04-30  6:12 ` Christoph Hellwig
2002-04-30 14:52   ` Jan Harkes
2002-04-30 15:50     ` Jan Harkes
2002-04-30 15:54 ` Steve Lord
2002-04-30 16:05   ` Steve Lord
2002-04-30 16:14   ` Jan Harkes
2002-04-30 16:29     ` Steve Lord [this message]
2002-04-30 16:40     ` Chris Mason
2002-04-30 17:03       ` Jan Harkes
2002-05-01  2:42         ` Jan Harkes
2002-05-01  3:25           ` Alexander Viro
2002-05-01  3:47             ` Jan Harkes
2002-05-01 16:17           ` Kai Henningsen

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=1020184161.7528.5.camel@jen.americas.sgi.com \
    --to=lord@sgi.com \
    --cc=jaharkes@cs.cmu.edu \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=mason@suse.com \
    --cc=viro@math.psu.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.