Jordi Pujol <jordipujolp@xxxxxxxxx> writes: > A Dimarts 17 Maig 2011 10:43:39, vÃreu escriure: >> Miklos Szeredi <miklos@xxxxxxxxxx> writes: >> Jordi, what's up with this? >> >> Could you please test the .v8 codebase with this single patch applied? > > Hello, > > I did so, but the system has never logged any dump from overlayfs, > this condition does not occur. Which is expected. > But I am so confused about the meaning of this test, I have seen that > other union filesystems will lock dentries for directory operations > and super_blocks for read/write operations, and overlayfs does not. I'm not sure what other filesystems do, but in overlayfs the upper/lower dentry references do not go away until the overlayfs dentry is freed. Jordi, what about the original bug you reported: >>>- a few days ago we talked about an error when repetitive sed instructions >>>were executed, also it happens in other processes, like mantaining list of >>>installed files for actual packages, >>>that is solved in ovl_rename issuing a dget for the old-dentry and parent >>>dentries. (This code is inspired on rename.c from unionfs) Is this still happening? Does the debug patch make any difference? Thanks, Miklos -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
