Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
improve umount_root behavior #1242
The current pattern is to check if a mount exists and if not, then umount it. In rare occasions, it results in mount disappearing right after the check and before umount causing umount_root to fail. Better to just umount and interpret the error. Error code(32) is useless because it's the same for other errors like invalid mount point etc.. So rely on the substring in the error message "not mounted"