cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GFS2 Patch] pass formal ino in do_filldir_main
Date: Wed, 07 Feb 2007 10:49:30 +0000	[thread overview]
Message-ID: <1170845370.11001.417.camel@quoit.chygwyn.com> (raw)
In-Reply-To: <1170823892.3414.3.camel@d-cthon07-w-63.Connectathon.ORG>

Hi,

I'm not sure that this is the right fix. no_formal_ino is used only as a
hash value in the lookup, the "real" lookup is always via no_addr. So we
can alter that hash if required to just use no_addr, but I'd rather not
have to return no_formal_ino here since we have no way to map that back
to the disk location of the inode in general. In fact given a maximum
sized GFS2 filesystem and enough nodes to fill it with inodes in a
reasonable time (yes, I know thats a lot and a long time!), its not even
certain to be unique,

Steve.

On Tue, 2007-02-06 at 23:51 -0500, Wendy Cheng wrote:
> Lookup failure found in '07 NFS connectathon. The nfsd is in the middle
> of readdirplus procedure call where it builds the file handles
> associated with the directory. GFS2 lookup code has been expected the
> first 64 bit of gfs2 inode number (formal inode number) but
> do_filldir_main() wrongly passes on-disk address inode number (no_addr).
> This patch fixes this.
> 
> Signed-off-by: S. Wendy Cheng <wcheng@redhat.com>
> 
> dir.c |    3 ++-
> 1 files changed, 2 insertions(+), 1 deletion(-)
> 
> --- linux-git/fs/gfs2/dir.c	2007-02-06 01:07:26.000000000 -0500
> +++ linux/fs/gfs2/dir.c	2007-02-06 20:50:16.000000000 -0500
> @@ -1241,8 +1241,9 @@ static int do_filldir_main(struct gfs2_i
>  
>  		error = filldir(opaque, (const char *)(dent + 1),
>  				be16_to_cpu(dent->de_name_len),
> -				off, be64_to_cpu(dent->de_inum.no_addr),
> +				off, be64_to_cpu(dent->de_inum.no_formal_ino),
>  				be16_to_cpu(dent->de_type));
> +		
>  		if (error)
>  			return 1;
>  
> 
> 



  reply	other threads:[~2007-02-07 10:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-07  4:51 [Cluster-devel] [GFS2 Patch] pass formal ino in do_filldir_main Wendy Cheng
2007-02-07 10:49 ` Steven Whitehouse [this message]
2007-02-07 22:35   ` Wendy Cheng
2007-02-07 23:37     ` Wendy Cheng
2007-02-08  9:42     ` Steven Whitehouse
2007-02-24  3:56       ` Wendy Cheng
2007-02-26 15:45         ` Steven Whitehouse
2007-02-26 16:11           ` Jonathan E Brassow
2007-02-26 17:16             ` Steven Whitehouse
2007-02-27 20:04               ` Wendy Cheng
2007-02-28  9:03                 ` Steven Whitehouse
2007-02-28 16:24                   ` Wendy Cheng
2007-02-28 16:26                     ` Wendy Cheng
2007-02-28 16:46                     ` Steven Whitehouse

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=1170845370.11001.417.camel@quoit.chygwyn.com \
    --to=swhiteho@redhat.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;
as well as URLs for NNTP newsgroup(s).