Comment 0 for bug 1908638

Using a polyinstantiated directory (see /etc/security/pam_namespace.conf) as a mount point is not working in focal (20.04.1) with libpam-mount 2.16-10.

The problem is only when the polydir itself is used as a mountpoint; there is no problem using a subdirectory inside the polydir. (e.g. If "/data2" is defined as a polydir in /etc/security/pam_namespace.conf, pam_mount succeeds when using /data2/subdir as a mount point, but fails when using /data2 as the mount point.)

I think the problem is this patch: 0014-Don-t-compare-source-when-checking-if-it-s-already-m.patch

Expected behavior: A filesystem should be mounted at the polydir or at least debug logs should show an attempted mount command.

Observed behavior: Nothing is mounted and the following lines are logged by both systemd and login (debugging enabled in pam_mount.conf.xml)

(mount.c:250): Mount info: globalconf, user=elinde <volume fstype="cifs" server="stor1" path="data" mountpoint="/data2" cipher="(null)" fskeypath="(null)" fskeycipher="(null)" fskeyhash="(null)" options="multiuser,cruid=elinde,sec=krb5,cifsacl" /> fstab=0 ssh=0

(mount.c:622): data already seems to be mounted at /data2, skipping

The behavior I'm looking for does work in bionic (18.04.5) with libpam-mount 2.16-3ubuntu0.1.