2012-12-08 (토), 14:55 +0900, Namjae Jeon: > From: Namjae Jeon <namjae.jeon@xxxxxxxxxxx> > > Test Case: > [NFS Client] > ls -lR . > > [NFS Server] > while [ 1 ] > do > echo 3 > /proc/sys/vm/drop_caches > done > > Error: "No such file or directory" > > When cache is dropped at the server, it results in lookup failure at the > NFS client. Even though the file exists. Looking at the code to rebuild > the inode in case of cache eviction. It tries to initiate a lookup operation > for ".." to get the parent information using the on-disk inode number. > Could you describe why this patch resolves that bug? Before applying this, we need to figure out why that bug is occurred. IMO, from the viewpoint of functionality, ".." resolution should work too. Thanks, -- Jaegeuk Kim Samsung
Attachment:
signature.asc
Description: This is a digitally signed message part
