<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Enable custom path to be ignored on shutdown umount cycle"
href="https://bugs.freedesktop.org/show_bug.cgi?id=56837#c6">Comment # 6</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Enable custom path to be ignored on shutdown umount cycle"
href="https://bugs.freedesktop.org/show_bug.cgi?id=56837">bug 56837</a>
from <span class="vcard"><a class="email" href="mailto:aleksei.lissitsin@gmail.com" title="aleksei.lissitsin@gmail.com">aleksei.lissitsin@gmail.com</a>
</span></b>
<pre>Yes. Without MNT_FORCE it now seems to behave correctly: only bind-mount gets
unmounted.
Just for the info: the problem only exists in the setting when only the
bind-mount is seen in mountinfo, and the real mountpoint is hidden. umount2
with MNT_FORCE then incorrectly assumes that the bind-mount is the last
mountpoint and proceeds to unmount the device (it succeeds because of MNT_FORCE
probably).
If both mountpoints are seen, it would correctly only detach the bind-mount and
leave the device mounted.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>