2018-07-09 19:52 GMT+08:00 Jeff Layton <jlayton@xxxxxxxxxx>: > On Mon, 2018-07-09 at 14:22 +0300, Amir Goldstein wrote: >> Eddie, >> >> This is NFS v4. Right? > > I think he said v3, which means NLM (lockd). > >> Do you wait until Android build completes before closing the >> first reproducer fd? >> >> I suspect you can replace the effect of Android build with >> drop_caches on the server. >> >> Jeff, >> >> Does knfsd hold a reference on the file/dentry/inode when >> a lock is taken? >> > > Given that he's using v3, it would actually be lockd in this case, but > yes, it should hold a struct file reference by virtue of a nlm_file > reference. > >> Assuming this is indeed a bug reproduced only with NFS+overlayfs >> it sounds like overlay decode file handle fails to return the same >> inode that knfd holds with the lock. > > That's a possibility. > -- > Jeff Layton <jlayton@xxxxxxxxxx> Hi Jeff and Amir, Thanks your addressing on this case. Clairify couples of setup about my usage: 1. client is nfs v3 2. Without using overlay, the problem is not happening, Compiling android over nfs v3 with server fs is ext4 is very common use case in my working environment, so supposed overlay is the major difference to produce this issue. 3. the simple reproducer waits android build completes then close the fd. 4. drop-caches instead of android build does not reproduce I'll keep try it by your suggestions. Thanks, Eddie -- To unsubscribe from this list: send the line "unsubscribe linux-unionfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
