]> pilppa.com Git - linux-2.6-omap-h63xx.git/commit
[GFS2] Obtaining no_formal_ino from directory entry
authorWendy Cheng <wcheng@redhat.com>
Wed, 27 Jun 2007 21:07:08 +0000 (17:07 -0400)
committerSteven Whitehouse <swhiteho@redhat.com>
Mon, 9 Jul 2007 07:24:08 +0000 (08:24 +0100)
commitbb9bcf061660661c57ddcf31337529f82414b937
tree0876874e5252c4939b8e7bbd62a22a6eb4ad1abf
parentf4fadb23ca49abd2f1387a0b7e78b385ebc760ce
[GFS2] Obtaining no_formal_ino from directory entry

GFS2 lookup code doesn't ask for inode shared glock. This implies during
in-memory inode creation for existing file, GFS2 will not disk-read in
the inode contents. This leaves no_formal_ino un-initialized during
lookup time. The un-initialized no_formal_ino is subsequently encoded
into file handle. Clients will get ESTALE error whenever it tries to
access these files.

Signed-off-by: S. Wendy Cheng <wcheng@redhat.com>
Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
fs/gfs2/dir.c
fs/gfs2/inode.c
fs/gfs2/inode.h
fs/gfs2/ops_export.c
fs/gfs2/ops_fstype.c
fs/gfs2/rgrp.c