Comment 6 for bug 1908638

Is "checkmounted" a standard / API function somewhere?

As mentioned earlier, my use case does work prior to the 14* patch since both path and mountpoint need to match an existing mount (rather than only the mountpoint) for pam_mount to decide something is already mounted.

I'm not seeing how the path gets to be unpredictable (at least for NFS on the linked bug). It looks more like vpt->volume might be failing to match the source path in pmt_utabent_matches as a result of certain xml configs because it's using the content of the path element verbatim instead of constructing it from multiple elements (e.g. 'path="nfs:/home/prisoners/p"' vs. 'server="nfs" path="/home/prisoners/p"') as happens in pmt_vol_to_dev.