You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The reason will be displayed to describe this comment to others. Learn more.
I believe that the xino table is per filesystem (actually, per branch), and we should therefore use a generated path to avoid collisions.
Warning: simple testing will probably not exhibit the problem, because the xino file is created, then unlinked. But if multiple mounts are done at the same time, there is the possibility that the same xino file gets used twice (I don't know what would happen in that case, honestly).
f67ea78
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe that the xino table is per filesystem (actually, per branch), and we should therefore use a generated path to avoid collisions.
Warning: simple testing will probably not exhibit the problem, because the xino file is created, then unlinked. But if multiple mounts are done at the same time, there is the possibility that the same xino file gets used twice (I don't know what would happen in that case, honestly).
f67ea78
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually, I stand corrected: according to AUFS author, this should work fine[1]
[1] http://www.mail-archive.com/aufs-users@lists.sourceforge.net/msg03177.html