Srinidhi Kaushik be63462f93 Handle invalid "losetup" options ... The non "util-linux" versions of "losetup" don't seem to have options like "-j" ("--associated") which lists the loop devices associated with the file, or "--show" which displays the name of the assigned loop device for a file. For instance, when "-j" is used, "GetLoopDevice()" fails with: $ losetup -j /path/to/file losetup: unrecognized option: j BusyBox v1.32.1 () multi-call binary. Add a fallback option to lookup the device from "sysfs" in cases where "losetup" fails for an invalid option. This can be done by reading the backing file from "/sys/block/loop*/loop/backing_file" for each of the devices listed there. Signed-off-by: Srinidhi Kaushik <shrinidhi.kaushik@gmail.com>		2021-05-02 20:02:51 +05:30
..
volume_path_handler.go	Remove unused/dead code	2021-03-09 09:34:37 +08:00
volume_path_handler_linux.go	Handle invalid "losetup" options	2021-05-02 20:02:51 +05:30
volume_path_handler_unsupported.go	Make descriptor lock per pod and release it per pod	2019-11-14 15:58:26 +00:00