[MESOS-5969] Linux 'MountInfoTable' entries not sorted as expected

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0.0
• Fix Version/s: 1.0.1
• Labels: filesystem linux
• Sprint: Mesosphere Sprint 40
• Story Points: 3
• Assignee: Kevin Klues
• Reporter: Kevin Klues
• Shepherd: Jie Yu
• Created: 02/Aug/16 18:51
• Updated: 02/Sep/16 00:13
• Resolved: 09/Aug/16 16:27

Description

Many places in the codebase assume that the mountinfo table is sorted according to the order: parent mount point < child mount point.

However, in some cases this may not be true if (for example), a parent mount point (say /) is remounted to add some extra flags to it. When this happens, the remounted file system will appear in the mount table at the point where it was remounted.

We actually encountered this problem in the wild for the case of / being remounted after /run was mounted – causing problems in the NvidiaVolume which assumes the parent < child ordering.

Issue Links

• relates to: MESOS-6118 Agent would crash with docker container tasks due to host mount table read.