http://bugzilla.opensuse.org/show_bug.cgi?id=1012504
http://bugzilla.opensuse.org/show_bug.cgi?id=1012504#c14
--- Comment #14 from Tony Mechelynck
There are two possible fixes:
- Add a heuristic for detecting of safe conditions for read-only loops overlays, by extension of loopcxt_find_overlap() return codes. (Hopefully it is not part of public API.) I am now checking how complicated it would be.
- YaST level: Make simple changes in the code that prevent requesting of overlaying loop devices.
IIUC, doing both of these two possible fixes wouldn't be hurtful, just redundant. Since (IIUC) the second one is simpler (but wouldn't fix any possible similar error in other programs) why not do it immediately, then see how complicated the other heuristic would be? Then if the full fix seems feasible, and gets applied and successfully tested, the YaST fix may either be removed as unnecessary, or even left in as a "belt and suspenders" additional safety measure. -- You are receiving this mail because: You are on the CC list for the bug.