Wendy Cheng bb9bcf0616 [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>
2007-07-09 08:24:08 +01:00
..
2007-07-09 08:23:33 +01:00
2006-11-30 10:37:32 -05:00
2006-11-30 10:37:32 -05:00
2006-10-20 09:13:40 -04:00
2007-07-09 08:22:24 +01:00
2007-07-09 08:23:36 +01:00
2007-02-05 13:38:20 -05:00
2007-05-17 05:23:04 -07:00
2007-07-09 08:23:59 +01:00
2007-07-09 08:23:36 +01:00
2007-07-09 08:22:19 +01:00
2006-09-05 10:39:21 -04:00