Hello, Eric. Eric W. Biederman wrote: > I will look a little more and see. But right now it looks like the > real problem with locking is that we use sysfs_mutex to lock the > sysfs_dirent s_children list. > > Instead it really looks like we should use i_mutex from the appropriate > inode. Or is there a real performance problem with forcing the directory > inodes in core when we modify the directories? I don't think there is any performance problem. Problems with using i_mutex were... * It was messy. I don't remember all the details now but IIRC symlink walk code was pretty complex. * And more importantly, inodes are reclaimable and might or might not be there. -- tejun _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/containers
